09 Jun

No ISSU on Nexus 7000 with vPC between VDCs on same chassis – follow up

A little while ago I wrote about unsupported scenario of upgrading NX-OS on Nexus 7000. It’s a scenario I found few months ago and forgot to write about it, but my other customer had same problem few weeks ago which refreshed my memory. Back then we got information from Cisco TAC that this scenario is not supported but no official information is available about this.

I got mail from Andras Toth from Cisco TAC lately pointing me that this limitation has been documented in NX-OS 5.1 release notes. Thanks Cisco for making it clear. And remember it applies to all NX-OS releases, not just 5.1.

14 May

No ISSU on Nexus 7000 with vPC between VDCs on same chassis

If you are using multiple VDCs on your Nexus 7000 switch and you create vPC between two of them you can forget about upgrading NX-OS via ISSU. This scenario is not supported, but there is no information about that in documentation. If you try to perform upgrade you will see following error message:

Notifying services about the switchover.            [#                   ]   0% -- FAIL. Return code 0x401E007B (request was aborted by service).
Please issue "show install all failure-reason" to find the cause of the failure.

Failure recovery action::
"Standby will be rebooted to force netboot and image download".
Install has failed. Return code 0x401E007B (request was aborted by service).

Please identify the cause of the failure, and try 'install all' again.

n7k-switch# show install all failure-reason
Service "vpc" in vdc: 2 returned error: configuration lock can not be acquired for peer switch (x41B7004B)
Service "vpc" in vdc: 3 returned error: configuration lock can not be acquired for peer switch (x41B7004B)

The only way to upgrade is to download new software, replace bootvar and reboot whole chassis.

15 Mar

Testing SSO on ASR1k

IOS XE on ASR1000 provides two forms of redundancy. First one is well-known hardware redundancy available in ASR1006 where two RP’s and ESP’s can be installed. On other platforms software redundancy and ISSU can be configured. Because IOS XE is in fact just one of a Linux processes running on the platform while system is booting up no one but two instances of iosd are executed in background, but only one is active. Both processes are running on same Route Processor. Standby IOS process can be switched to in the event of an IOS failure, and can also be used to upgrade sub-package software in some scenarios as the standby IOS process in an ISSU upgrade.
Read More