I opened a TAC Case on this: TAC Responded.... We have asked the BU to tell us how to do this. So no I am waiting for a Conference call with the BU.
So in the mean time I tried what James said.... I do have my reservations about golden disk. In my opinion golden disk is usefully for deploying a new router not upgrading a working router, due to the fact you have to generate a new ISO for each router. I was able to do this and have the package added to the repository. When I try to add one or more packages to the repo I get the file is corrupt, even though the file check sum matches... RP/0/RSP0/CPU0:CR1.LAB1#sh install log 58 Fri Apr 13 09:41:48.156 UTC Apr 12 12:21:52 Install operation 58 started by esundberg: install add source harddisk:/downloads/6.3.2 asr9k-ospf-x64-18.104.22.168-r632.x86_64.rpm Apr 12 12:21:53 Action 1: install add action started Apr 12 12:21:54 Install operation will continue in the background Apr 12 12:21:55 ERROR! Package "asr9k-ospf-x64-22.214.171.124-r632.x86_64.rpm" is invalid: asr9k-ospf-x64-126.96.36.199-r632.x86_64.rpm is corrupt Apr 12 12:21:55 ERROR!! failed while handling validate reply Apr 12 12:21:57 Install operation 58 aborted Apr 12 12:21:57 Ending operation 58 RP/0/RSP0/CPU0:CR1.LAB1# Erik Sundberg Sr. Network Engineering Network Engineering Department p: 773.661.5532 c: 708.710.7419 e: esundb...@nitelusa.com Main: 888.450.2100 NOC 24/7: 866.892.0915 350 North Orleans Street, Suite 1300N Chicago, IL 60654 www.nitelusa.com Managed Telecom Services MPLS | Ethernet | Private Line | Internet | Voice | Security -----Original Message----- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of adamv0...@netconsultings.com Sent: Friday, April 13, 2018 9:36 AM To: 'Tom Hill' <t...@ninjabadger.net>; email@example.com Subject: Re: [c-nsp] Cisco ASR99xx 64-bit upgrade 6.3.1 to 6.3.2 > Tom Hill > Sent: Friday, April 13, 2018 1:46 PM > > On 12/04/18 18:06, Gert Doering wrote: > > yum update > > > > ... now *that* would be nice... > > I thought you could do that... > > https://www.cisco.com/c/dam/assets/global/DK/seminarer/pdfs/XR60.pdf > (pgs. 30 & 31) > Page 26 of the same doc: IOS XR packages are installed with "install update/upgrade". Install commands are a wrapper around YUM to provide multiarch support. -so there's your yum update But from the initial discussions on this from a few years back I thought I'd be able to spin up container on new version and then just switch to new one in an instance, or failback quickly if needed, preferably 0 packet loss in the process (maybe I'm mistaken ncs6k with asr9k). Makes me wonder what's going on under the hood on asr9ks ncs5ks actually -i.e. how does the picture look like at each LC (I guess we'll need to wait till this "modular" architecture arrives to LCs as well?) In this sense, to me the router chassis is like a small DC with compute nodes (in form of RPs and LCs) all connected via Ethernet network -it would be nice to have control over which containers and what versions run on each compute node. And regarding the 0 packet loss, I'm wondering whether the NPU microcode version is independent of the (I guess Admin Plane) version (or whether it's still monolithic) Also wondering when we'll be able to take RPs out of the chassis that is spin up the Control container(s) (and third party containers) on COTS HW and let these talk to LCs. As unfortunately these chassis-based systems can become full with just couple of LCs in them just because the RP can't cope with the high number of VRFs, prefixes and BGP sessions. adam netconsultings.com ::carrier-class solutions for the telecommunications industry:: _______________________________________________ cisco-nsp mailing list firstname.lastname@example.org https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ________________________________ CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error please notify the sender immediately by replying to this e-mail. You must destroy the original transmission and its attachments without reading or saving in any manner. Thank you. _______________________________________________ cisco-nsp mailing list email@example.com https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/