Re: [c-nsp] new ASR9901 ios update problem
On 6/Nov/19 10:34, Gert Doering wrote: > Even if IOS XR were absolutely perfect and Cisco pricing and trade > negotiations would have less of a turkish bazaar, there'd still be the > zillion other sources of amusement in-house, like Nexus, Meraki, annual > license fees, etc. :-) Oh hell yeah :-)... Mark. signature.asc Description: OpenPGP digital signature ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
Hi, On Wed, Nov 06, 2019 at 10:29:00AM +0200, Mark Tinka wrote: > On 6/Nov/19 10:16, Erik Sundberg wrote: > > I have hope that one day the Cisco gods will discover "apt update; apt > > upgrade" and all this sorcery that we need for an upgrade will become a > > thing of the past. > > And having nothing to moan about? c-nsp would whither into oblivion :-). Even if IOS XR were absolutely perfect and Cisco pricing and trade negotiations would have less of a turkish bazaar, there'd still be the zillion other sources of amusement in-house, like Nexus, Meraki, annual license fees, etc. :-) gert -- "If was one thing all people took for granted, was conviction that if you feed honest figures into a computer, honest figures come out. Never doubted it myself till I met a computer with a sense of humor." Robert A. Heinlein, The Moon is a Harsh Mistress Gert Doering - Munich, Germany g...@greenie.muc.de signature.asc Description: PGP signature ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
On 6/Nov/19 10:16, Erik Sundberg wrote: > I have hope that one day the Cisco gods will discover "apt update; apt > upgrade" and all this sorcery that we need for an upgrade will become a thing > of the past. And having nothing to moan about? c-nsp would whither into oblivion :-). Mark. ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
Hi, On Wed, Nov 06, 2019 at 08:16:23AM +, Erik Sundberg wrote: > I have hope that one day the Cisco gods will discover "apt update; apt > upgrade" and all this sorcery that we need for an upgrade will become a thing > of the past. Even that is way too complicated and error-prone if you want to do large upgrades. Give me a "copy http://$image flash:" any day... It's not even overly hard to do that with a proper filesystem underneath *and* per-component upgrades - mount the image read-only, mount a read-write section of the flash on top of it (overlay), install all the hotfixes to the overlay, and if the underlay is upgraded, wipe the overlay at the next reboot. Done. Yes, there are scenarios where this is not as flexible as what XR offers today... but hey, I trade a bit of flexibility against extensive nightmares every day. gert -- "If was one thing all people took for granted, was conviction that if you feed honest figures into a computer, honest figures come out. Never doubted it myself till I met a computer with a sense of humor." Robert A. Heinlein, The Moon is a Harsh Mistress Gert Doering - Munich, Germany g...@greenie.muc.de signature.asc Description: PGP signature ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
I have hope that one day the Cisco gods will discover "apt update; apt upgrade" and all this sorcery that we need for an upgrade will become a thing of the past. From: cisco-nsp on behalf of c...@marenda.net Sent: Saturday, November 2, 2019 10:58 AM To: 'Aaron Gould' ; c...@marenda.net ; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] new ASR9901 ios update problem Thanks fort he flowers, Aaron! Now i got stuck in those patches called SMU. Not only the mentioned time-consuming (each reload takes 15..20 minutes) is boring, But after installing most of the SMUs and ony 5..7 remaining from the bunch of 80+-5 SMUs, the X device tells me on its console port, that the root filesystem is over 80% or more full. LC/0/0/CPU0:Nov 2 12:47:56.505 CET: resmon[290]: %HA-HA_WD-3-DISK_ALARM_ALERT : A monitored device / ( rootfs:/ ) is above 80% utilization. Current utilization = 80. Please remove unwanted user files and configuration rollback points. Googling for this i found https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-xr-software/116332-maintain-ios-xr-smu-00.html [...] Bootflash is above 80% utilization The following message may appear after SMU installation. RP/0/RSP0/CPU0:Jul 9 17:40:37.959 : wdsysmon[447]: %HA-HA_WD-4-DISK_WARN : A monitored device /bootflash: is above 80% utilization. Current utilization = 89. Please remove unwanted user files and configuration rollback points. This message can be safely ignored. As per design it is expected that IOS-XR will keep up to two MBIs on the bootflash following SMU install(s). At subsequent SMU install(s), if the bootflash space required by the new package(s) is not available, IOS-XR will clean up automatically old MBIs to make space for the new MBI package. [...] So i did continue and no it is 99-100% full, "install add source ..." works but "install activate ..." aborts. I do not have "userfiles" on it, i did but the ios,tar,smu's onto "harddisk:" . I did not find any hint how to make space there, i tried "clear configuration commits oldest 100" "install remove inactive all synchronous" But this did not help. #show install log 250 detail Sat Nov 2 12:56:50.744 CET Nov 02 09:56:57 Install operation 250 started by jm: install activate id 249 Nov 02 09:56:57 Package list: Nov 02 09:56:57 asr9k-mgbl-x64-2.0.0.4-r653.CSCvr46090.x86_64 Nov 02 09:57:01 Action 1: install prepare action started Nov 02 09:57:03 Install operation will continue in the background Nov 02 09:57:03 The prepared software is set to be activated with process restart Nov 02 09:57:47 Start preparing software for local installation Nov 02 09:57:59 Action 1: install prepare action completed successfully Nov 02 09:58:00 Action 2: install activate action started Nov 02 09:58:00 The software will be activated with process restart Nov 02 09:58:01 Activating XR packages Nov 02 09:59:12 Node 0/RSP0/CPU0 encountered error(s) during operation. Please check 'show install log 250 detail' for error details Nov 02 09:59:12 Error stack for location 0/RSP0/CPU0 1# Available disk space(including additional buffer 104857600) 215699456 is not sufficient for rpm installation of archive size 110199132 2# failed to load files from ldpath (new) Please collect 'show tech-support install one-showtech' from XR and 'show tech-support ctrace' from Admin and pass this information to your TAC representative for support. Nov 02 09:59:12 Agent on the lead has err'ed during SWC_BEGIN Aborting the operation Nov 02 09:59:12 Action 2: install activate action aborted Nov 02 10:00:21 Install operation 250 aborted Nov 02 10:00:21 Ending operation 250 I submitted the output from 'show tech-support install one-showtech' to my TAC case But i have not found out how to move the "admin'show tech-support ctrace'" output out of the box. Looks like admin-harddisk: is not the same as harddisk: and also admin copy does not know ftp as destination (and i believe it will not work with my mgmt-vrf, ip information is a stange 192.168.0.4 not my mgmt-ip, ) Very very strange ☹ BTW, When i was at the approx. 80% SMU installation point, i got the hint from tac that i can untar the SMUs, and bundle them (without the .txt files) in one tape-archive to get it installed faster. Way too late after 3 days of work Looks that the documentation on how to upgrade the box has never been tested (and in/output captured) and also, no-one had ever tried to add all recommended patches. Any idea on what is blocking space on / and can be removed ? Repartiion and install from scratch ? RMA it and get a refurbished device with scratches instead of this expensive brand new garbage ? I am also a li
Re: [c-nsp] new ASR9901 ios update problem
Thanks fort he flowers, Aaron! Now i got stuck in those patches called SMU. Not only the mentioned time-consuming (each reload takes 15..20 minutes) is boring, But after installing most of the SMUs and ony 5..7 remaining from the bunch of 80+-5 SMUs, the X device tells me on its console port, that the root filesystem is over 80% or more full. LC/0/0/CPU0:Nov 2 12:47:56.505 CET: resmon[290]: %HA-HA_WD-3-DISK_ALARM_ALERT : A monitored device / ( rootfs:/ ) is above 80% utilization. Current utilization = 80. Please remove unwanted user files and configuration rollback points. Googling for this i found https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-xr-software/116332-maintain-ios-xr-smu-00.html [...] Bootflash is above 80% utilization The following message may appear after SMU installation. RP/0/RSP0/CPU0:Jul 9 17:40:37.959 : wdsysmon[447]: %HA-HA_WD-4-DISK_WARN : A monitored device /bootflash: is above 80% utilization. Current utilization = 89. Please remove unwanted user files and configuration rollback points. This message can be safely ignored. As per design it is expected that IOS-XR will keep up to two MBIs on the bootflash following SMU install(s). At subsequent SMU install(s), if the bootflash space required by the new package(s) is not available, IOS-XR will clean up automatically old MBIs to make space for the new MBI package. [...] So i did continue and no it is 99-100% full, "install add source ..." works but "install activate ..." aborts. I do not have "userfiles" on it, i did but the ios,tar,smu's onto "harddisk:" . I did not find any hint how to make space there, i tried "clear configuration commits oldest 100" "install remove inactive all synchronous" But this did not help. #show install log 250 detail Sat Nov 2 12:56:50.744 CET Nov 02 09:56:57 Install operation 250 started by jm: install activate id 249 Nov 02 09:56:57 Package list: Nov 02 09:56:57 asr9k-mgbl-x64-2.0.0.4-r653.CSCvr46090.x86_64 Nov 02 09:57:01 Action 1: install prepare action started Nov 02 09:57:03 Install operation will continue in the background Nov 02 09:57:03 The prepared software is set to be activated with process restart Nov 02 09:57:47 Start preparing software for local installation Nov 02 09:57:59 Action 1: install prepare action completed successfully Nov 02 09:58:00 Action 2: install activate action started Nov 02 09:58:00 The software will be activated with process restart Nov 02 09:58:01 Activating XR packages Nov 02 09:59:12 Node 0/RSP0/CPU0 encountered error(s) during operation. Please check 'show install log 250 detail' for error details Nov 02 09:59:12 Error stack for location 0/RSP0/CPU0 1# Available disk space(including additional buffer 104857600) 215699456 is not sufficient for rpm installation of archive size 110199132 2# failed to load files from ldpath (new) Please collect 'show tech-support install one-showtech' from XR and 'show tech-support ctrace' from Admin and pass this information to your TAC representative for support. Nov 02 09:59:12 Agent on the lead has err'ed during SWC_BEGIN Aborting the operation Nov 02 09:59:12 Action 2: install activate action aborted Nov 02 10:00:21 Install operation 250 aborted Nov 02 10:00:21 Ending operation 250 I submitted the output from 'show tech-support install one-showtech' to my TAC case But i have not found out how to move the "admin'show tech-support ctrace'" output out of the box. Looks like admin-harddisk: is not the same as harddisk: and also admin copy does not know ftp as destination (and i believe it will not work with my mgmt-vrf, ip information is a stange 192.168.0.4 not my mgmt-ip, ) Very very strange ☹ BTW, When i was at the approx. 80% SMU installation point, i got the hint from tac that i can untar the SMUs, and bundle them (without the .txt files) in one tape-archive to get it installed faster. Way too late after 3 days of work Looks that the documentation on how to upgrade the box has never been tested (and in/output captured) and also, no-one had ever tried to add all recommended patches. Any idea on what is blocking space on / and can be removed ? Repartiion and install from scratch ? RMA it and get a refurbished device with scratches instead of this expensive brand new garbage ? I am also a little bit afraid on using such a thing for production., Thought version 6.5 would be matured and procedures well documented And the TAC people can give me concrete answers not generic blarney. ->sigh<- Jürgen Marenda. > -Ursprüngliche Nachricht- > Von: Aaron Gould > Btw, good job, and thanks Jürgen for the informative and detailed instruction > on XR upgrade. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net
Re: [c-nsp] new ASR9901 ios update problem
It's pretty simple upgrade for asr9900's running 64 bit. Below is what we use for our ASR9906's when upgrading 64 bit to 64 bit. !Do your upgrade prechecks (sh run, show redundancy, show platform, show install active, and etc.) ! If installing from an interface that's in a VRF. http client vrf MANAGEMENT http client source-interface ipv4 MgmtEth0/RSP0/CPU0/0 ! add the software, let the router download it install add source http://x.x.x.x/Cisco/ASR9906/6.5.3/ asr9k-mini-x64-6.5.3.iso ASR9K-x64-iosxr-px-k9-6.5.3.tar ! install it. install activate asr9k-mini-x64-6.5.3 asr9k-k9sec-x64-2.1.0.0-r653.x86_64 asr9k-ospf-x64-1.0.0.0-r653.x86_64 asr9k-mpls-x64-2.0.0.0-r653.x86_64 asr9k-mgbl-x64-2.0.0.0-r653.x86_64 asr9k-li-x64-1.1.0.0-r653.x86_64 asr9k-mcast-x64-2.0.0.0-r653.x86_64 asr9k-mpls-te-rsvp-x64-2.1.0.0-r653.x86_64 asr9k-isis-x64-1.1.0.0-r653.x86_64 Router reboots automatically ! Make sure the Linecards are up show platform ! Make sure the linecards were upgraded show install active ! Commit the install, or you will need to do it all over again if you reboot the router with the software not commited. install commit ! Check to see if the linecards need a firmware upgrade. show hw-module fpd ! Upgrade the firmware if needed upgrade hw-module location all fpd all Reload the line cards that say RLOAD REQ. We just reload the whole chassis. admin reload rack 0 And Done -Original Message- From: cisco-nsp On Behalf Of Tim Warnock Sent: Wednesday, October 30, 2019 6:40 AM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] new ASR9901 ios update problem eXR makes this so much easier. Other than the pain of 6.3.2 -> 6.3.3 (where RPM moved to code signing) pretty much none of that is necessary. But yeah, 3* lines should get you from any version > 6.3.3 to any other version. ([conf t, fpd auto-upgrade enable, commit, end,] copy url:///file harddisk:/ [vrf ], install add source harddisk:/ , install activate id ) You can even stage the install during normal hours so the final activation happens much faster (copy, install add source, install prepare then later on install activate). But - if you really don't want to spend a few minutes setting up a tarball with all of the packages you want installed in one go then I hear CSM might be the solution. Also should handle RPM hell if you have lots of SMUs... > -Original Message- > From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf > Of Aaron Gould > Sent: Wednesday, 30 October 2019 1:33 AM > To: c...@marenda.net; cisco-nsp@puck.nether.net > Subject: Re: [c-nsp] new ASR9901 ios update problem > > Btw, good job, and thanks Jürgen for the informative and detailed > instruction on XR upgrade. > > -Aaron > > -Original Message- > From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf > Of Aaron Gould > Sent: Tuesday, October 29, 2019 10:23 AM > To: c...@marenda.net; cisco-nsp@puck.nether.net > Subject: Re: [c-nsp] new ASR9901 ios update problem > > You just gave me another reason to like Juniper :| > > -Aaron > > > ___ > 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/ > > ___ > 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/ ___ 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/ 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/
Re: [c-nsp] new ASR9901 ios update problem
eXR makes this so much easier. Other than the pain of 6.3.2 -> 6.3.3 (where RPM moved to code signing) pretty much none of that is necessary. But yeah, 3* lines should get you from any version > 6.3.3 to any other version. ([conf t, fpd auto-upgrade enable, commit, end,] copy url:///file harddisk:/ [vrf ], install add source harddisk:/ , install activate id ) You can even stage the install during normal hours so the final activation happens much faster (copy, install add source, install prepare then later on install activate). But - if you really don't want to spend a few minutes setting up a tarball with all of the packages you want installed in one go then I hear CSM might be the solution. Also should handle RPM hell if you have lots of SMUs... > -Original Message- > From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of > Aaron Gould > Sent: Wednesday, 30 October 2019 1:33 AM > To: c...@marenda.net; cisco-nsp@puck.nether.net > Subject: Re: [c-nsp] new ASR9901 ios update problem > > Btw, good job, and thanks Jürgen for the informative and detailed > instruction on XR upgrade. > > -Aaron > > -Original Message- > From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of > Aaron Gould > Sent: Tuesday, October 29, 2019 10:23 AM > To: c...@marenda.net; cisco-nsp@puck.nether.net > Subject: Re: [c-nsp] new ASR9901 ios update problem > > You just gave me another reason to like Juniper :| > > -Aaron > > > ___ > 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/ > > ___ > 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/ ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
On 29/Oct/19 17:23, Aaron Gould wrote: > You just gave me another reason to like Juniper :| One of the biggest reason keeping me from leaving IOS XE for our Metro-E deployments. Mark. ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
Btw, good job, and thanks Jürgen for the informative and detailed instruction on XR upgrade. -Aaron -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Aaron Gould Sent: Tuesday, October 29, 2019 10:23 AM To: c...@marenda.net; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] new ASR9901 ios update problem You just gave me another reason to like Juniper :| -Aaron ___ 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/ ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
You just gave me another reason to like Juniper :| -Aaron ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
Hi, i got some help from TAC on this, So i manged the upgrade (but the patches "SMU"s are still waiting) Here is a (not really) short summary of the steps i did (may be thats not the optimal/fastes procedure): 1. i have working serial console access (115200-8N1) 2. i have an account "jm" with the same rights as "admin" so i must not type "admin" in front of each command i believe 3. the first Management-Ethernet "MgmtEth0/RSP0/CPU0/0" is in vrf mgmt with ip 10.10.50.22 /24 4. my ftp/tftp/... server is on the same (v)lan and has the ip 10.10.50.84 so direct connection and no router/NAT/... in the way 5. username:password for ftp in this text used is cisco:ciscopass 6. i did the steps 1,3 and skipped step 2 from the PDF ASR9K_IOS-XR-64-bit_Upgrade_MOP_6.5.3.pdf found in ASR9K-x64-docs-6.5.3.tar since i upgrade only from 6.5.2 to 6.5.3 where no "bridge" package installation is nessassary (in that tar-ball are not the linux-manpages for the box) 7. i put the files asr9k-mini-x64-6.5.3.iso ASR9K-x64-iosxr-px-k9-6.5.3.tar onto the ftp-server in directory ASR9901/6.5.3/ i (relative to user cisco's basedirectory) 8. i put the "x64" and "sysadmin" smus onto the ftp-server in directory ASR9901/6.5.3/smu/ 9. Trying method "4.2" from the pdf above, "install" does not know the command "upgrade" or "update" When entering "run" or "admin" "run" the install command has "update" "upgrade" options but does not know how to ftp out, due to unknow syntax i could not find out how to use a vrf. Also setting ftp source-interface etc in the config did not help. doing ifconfig does not show my Management-ethernet but some strange internal vlans... 10. Trying method "4.1" . 10.1. makeing directories on the "harddisk:" mkdir harddisk:/sw mkdir harddisk:/sw/6.5.3 mkdir harddisk:/sw/6.5.3/smu cd harddisk:/sw/6.5.3 10.2. copying files from ftp-server copy ftp://cisco:ciscopass@10.10.50.84;mgmt/ASR9901/6.5.3/asr9k-mini-x64-6.5.3.is o harddisk:/sw/6.5.3/ copy ftp://cisco:ciscopass@10.10.50.84;mgmt/ASR9901/6.5.3/ASR9K-x64-iosxr-px-k9-6 .5.3.tar harddisk:/sw/6.5.3/ 10.3. install add source harddisk:/sw/6.5.3/ asr9k-mini-x64-6.5.3.iso --^ here is a needed space between ...6.5.3/ and asr9... ...Install operation 13 finished successfully 10.4. install add source harddisk:/sw/6.5.3/ ASR9K-x64-iosxr-px-k9-6.5.3.tar --^ here is a needed space between ...6.5.3/ and ASR9... ...Install operation 14 finished successfully 10.5. install prepare id 13 14 Both Install opertion numbers from above together shwo install request show install log 15 detail fast going to 40%, then long waiting (15 minutes) ... Install operation 15 finished successfully 10.6 install activate ... Action 1: install activate action completed successfully Action 1: install activate action completed successfully Install operation 16 finished successfully Ending operation 16 10.7. maschine boots automatically and after around 15 minutes, all the interfaces are again there. 10.8. login (iff not done) 10.9. install commit ... Install operation 18 finished successfully 10.10. again doing Part 2 of the upgrade PDF 10.11. install remove inactive all 10.12. and a final reload That was it. == Now i need a nice way to get the SMUs installed without headache. BTW, the "px" are for the 32Bit (for example) ASR9001 devices "classic XR" "cXR" the "x64" and the "sysadm" are for the 64Bit (for example) ASR9901 devices "enhanced XR" "eXR" so i was told in my TAC case. I wonder why i find them all mixed up when i first select the one or other in cisco-support-download section. == missing output of my mgmt-vrf in IOS-XR 6.5.2 when i was typeing "show vrf all" was a bug disappearing afer the upgrade to 6.5.3. == Jürgen Marenda. ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
On 24/10/2019 09:27, Werner le Grange wrote: > You can't upgrade directly from release 4 to 6. First upgrade to 5.3.4 > before upgrading to release 6. Neither one of you have paid any attention to the fact that the OP specified a 9901, not a 9001 or 9006. These came with 64-bit XR, so any 32-bit knowledge is defunct at this point -- you're just adding noise to the list. -- Tom ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
Hi Aaron You can't upgrade directly from release 4 to 6. First upgrade to 5.3.4 before upgrading to release 6. It's recommended to remove fpd auto-upgrade in the admin config (if configure) when upgrading between major releases. RP/0/RSP0/CPU0:hostname(admin)#sh run | i auto Thu Oct 24 10:12:41.175 SAST Building configuration... *fpd auto-upgrade* Install the post-expiry SMU and root cert, else you won't be able to add install add any new software. This document is for 5.1.3 - you'll need the 4.3.4 SMU https://www.cisco.com/c/en/us/td/docs/routers/technotes/MOP-CSS-to-Abraxas.html Once complete, you would be able to add the 5.3.4 PIE files. install add ... install active disk0:*5.3.4* asynchronous install commit - after the reload. Run a FPD upgrade. RP/0/RSP0/CPU0:hostname(admin)#upgrade hw-module fpd all location all Once the FPD upgrade is complete - remove the 4.3.4 inactive files to ensure you have enough space on the router. RP/0/RSP0/CPU0:hostname(admin)#install remove inactive asynchronous Now you are ready to add the 6.5.2 PIE files and relevant SMU's. install add install active install commit -Werner On Thu, Oct 24, 2019 at 4:32 AM Aaron Gould wrote: > It got jumbled ... I'll try again... > > > admin install add disk1:asr9k-mgbl-px.pie-4.3.4 > disk1:asr9k-mpls-px.pie-4.3.4 disk1:asr9k-mini-px.pie-4.3.4 > disk1:asr9k-fpd-px.pie-4.3.4 synchronous > > admin install activate disk0:asr9k-mgbl-px-4.3.4 disk0:asr9k-mpls-px-4.3.4 > disk0:asr9k-mini-px-4.3.4 disk0:asr9k-fpd-px-4.3.4 synchronous > > (after reboot occurs) > > admin install commit > > > > ___ > 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/ > ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
It got jumbled ... I'll try again... admin install add disk1:asr9k-mgbl-px.pie-4.3.4 disk1:asr9k-mpls-px.pie-4.3.4 disk1:asr9k-mini-px.pie-4.3.4 disk1:asr9k-fpd-px.pie-4.3.4 synchronous admin install activate disk0:asr9k-mgbl-px-4.3.4 disk0:asr9k-mpls-px-4.3.4 disk0:asr9k-mini-px-4.3.4 disk0:asr9k-fpd-px-4.3.4 synchronous (after reboot occurs) admin install commit ___ 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/
Re: [c-nsp] new ASR9901 ios update problem
Unsure about ASR9901 running 6.5.2... but I just now upgraded ASR9006 from 4.1.2 to 4.3.4 The process is pretty much... admin install add ... admin install activate ... admin install commit ...that's pretty much it in simplest terms... (I'll say I don't fully understand all the caveats and nuances with bridge smu's, time expiry issue, bug fix smu packages, bundle all pie's into a tar ball, etc,etc)... But in its simplest form, that's it. admin install add disk1:asr9k-mgbl-px.pie-4.3.4 disk1:asr9k-mpls-px.pie-4.3.4 disk1:asr9k-mini-px.pie-4.3.4 disk1:asr9k-fpd-px.pie-4.3.4 synchronous admin install activate disk0:asr9k-mgbl-px-4.3.4 disk0:asr9k-mpls-px-4.3.4 disk0:asr9k-mini-px-4.3.4 disk0:asr9k-fpd-px-4.3.4 synchronous (after reboot occurs) admin install commit You have may other pies you require, just add this into the list above. I had issues with tftp, so I simply ftp the files into disk1 and executed install from that location I had issues with a clock and also fpd, simply set the clock to something like 2009 and add that fpd pie. That's what I did, worked. - Aaron ___ 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/