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/
