Here is a follow up to my email thread Cisco release the following 6.3.2 bridge smu containing the following packages. These package allow the router to handle signed RPM’s. I will assume they will eventually be up on Cisco CCO website. asr9k-sysadmin-system-6.3.1.1-r631.CSCvf01652.x86_64 asr9k-iosxr-infra-64-1.0.0.1-r631.CSCvf01652.x86_64
We are running Cisco ASR9906, but this should also apply for 9912, and 9922. Also the IOS XR image file is now a ISO file and packages are now RPM’s. Install the files like you would for any other package on previous versions. I believe this started in IOS XR 6.x, not 100% sure. ftpServer: 1.2.3.4 VRF MANAGEMENT #Set up your FTP source Interface. Same goes for HTTP too. clear configuration inconsistency conf t ftp client vrf MANAGEMENT source-interface MgmtEth 0/RSP0/CPU0/0 commit exit ### Commands to monitor install requests #show install repository all #show install log <id> #show install request # # if needed to remove a package # install remove <package> # #Patch 6.3.1 ----------------- install add source ftp://tftp@1.2.3.4;MANAGEMENT/Cisco/ASR9906/6.3.2/632-bridge-smu/ asr9k-iosxr-infra-64-1.0.0.1-r631.CSCvf01652.x86_64.rpm install add source ftp://tftp@1.2.3.4;MANAGEMENT/Cisco/ASR9906/6.3.2/632-bridge-smu/ asr9k-sysadmin-system-6.3.1.1-r631.CSCvf01652.x86_64.rpm install activate asr9k-sysadmin-system-6.3.1.1-r631.CSCvf01652.x86_64 asr9k-iosxr-infra-64-1.0.0.1-r631.CSCvf01652.x86_64 install commit #Upgrade 6.3.1 to 6.3.2 -------------------------------- #Add or remove any packages that fits your needs. install add source ftp://tftp@1.2.3.4;MANAGEMENT/Cisco/ASR9906/6.3.2/ asr9k-mini-x64-6.3.2.iso asr9k-isis-x64-1.2.0.0-r632.x86_64.rpm asr9k-k9sec-x64-3.1.0.0-r632.x86_64.rpm asr9k-li-x64-1.1.0.0-r632.x86_64.rpm asr9k-mcast-x64-2.0.0.0-r632.x86_64.rpm asr9k-mgbl-x64-3.0.0.0-r632.x86_64.rpm asr9k-mpls-te-rsvp-x64-1.2.0.0-r632.x86_64.rpm asr9k-mpls-x64-2.0.0.0-r632.x86_64.rpm asr9k-ospf-x64-1.0.0.0-r632.x86_64.rpm show install repository all install activate asr9k-mini-x64-6.3.2 asr9k-isis-x64-1.2.0.0-r632.x86_64 asr9k-k9sec-x64-3.1.0.0-r632.x86_64 asr9k-li-x64-1.1.0.0-r632.x86_64 asr9k-mcast-x64-2.0.0.0-r632.x86_64 asr9k-mgbl-x64-3.0.0.0-r632.x86_64 asr9k-mpls-te-rsvp-x64-1.2.0.0-r632.x86_64 asr9k-mpls-x64-2.0.0.0-r632.x86_64 asr9k-ospf-x64-1.0.0.0-r632.x86_64 #System says install request completed successfully, then the router automatically reboots. #After it comes back up on 6.3.2 verify the software version after all the linecards are up show install active show ver #Then install commit I hope this helps someone else…. From: arulgobinath emmanuel [mailto:arulg...@gmail.com] Sent: Friday, April 13, 2018 7:48 PM To: Erik Sundberg <esundb...@nitelusa.com> Subject: Re: [c-nsp] Cisco ASR99xx 64-bit upgrade 6.3.1 to 6.3.2 Hi Erik, The error you are getting due to bridge smu. Have done few ncs upgrades faced the same issue. Smu they can publish its available internally. BR, Gobinath On Sat, 14 Apr 2018, 00:50 Erik Sundberg, <esundb...@nitelusa.com<mailto:esundb...@nitelusa.com>> wrote: 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-1.0.0.0-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-1.0.0.0-r632.x86_64.rpm" is invalid: asr9k-ospf-x64-1.0.0.0-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<mailto: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<http://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<mailto:cisco-nsp-boun...@puck.nether.net>] On Behalf Of adamv0...@netconsultings.com<mailto:adamv0...@netconsultings.com> Sent: Friday, April 13, 2018 9:36 AM To: 'Tom Hill' <t...@ninjabadger.net<mailto:t...@ninjabadger.net>>; cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> 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<http://netconsultings.com> ::carrier-class solutions for the telecommunications industry:: _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> 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 cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> 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 cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/