Upgrading Nexus 5548

Hi,
We want to upgrade our pair of Nexus 5548 to the new NX-OS 5.1(3)N2(1a) from the 5.0(3)N1(1c) version. We would like to use the ISSU procedure. But when we execute the command "show spannig-tree issu-impact" we get the following output:
No Active Topology change Found!
Criteria 1 PASSED !!
No Ports with BA Enabled Found!
Criteria 2 PASSED!!
List of all the Non-Edge Ports
Port VLAN Role Sts Tree Type Instance
Ethernet2/8 1803 Desg FWD PVRST 1803
The 1803 vlan is only used for the peer-keepalive link and it only exists on these two Nexus. So one of the two Nexus needs to be the STP root. That makes the ports on that vlan to be in designated-forwarding state, which is not supported for the ISSU:
sh run int e2/8
!Command: show running-config interface Ethernet2/8
!Time: Fri Jun 8 17:04:33 2012
version 5.0(3)N1(1c)
interface Ethernet2/8
switchport access vlan 1803
speed 1000
That is the only port that belongs to that VLAN and it is directly connected to the other Nexus 5548. So the only way we see to avoid this port of being in designated-forwarding state is to apply the "no spanning-tree vlan 1803" command. Would it be a problem?
We can imagine that introducing the "spanning-tree port type edge" should not be a good idea, shouldn´t it?
Thank you very much for your help!
Josu

Hi,
Reviewing all the prerequisites for the ISSU, we have seen the following:
SSU and Layer 3
Cisco Nexus 5500 Platform switches support Layer 3 functionality. However, the system cannot be upgraded with the ISSU process (non disruptive upgrade) when Layer 3 is enabled. It is required to unconfigure all Layer 3 features to be able to upgrade in a non disruptive way with an ISSU.
We have the interface-vlan feature enabled. But it is only used for two interfaces:
- interface-vlan 510 --> It is only used in order connect to the switch
- interface-vlan 1803 --> The one used for the keepalive
We could administratevely shutdown the interface-vlan 510. But we could not do so with the interface-vlan 1803, since it is used for the keepalive. If we execute "no feature interface-vlan", would the keepalive stop working?
When we execute "sh install all impact ..." command the Nexus does not tell anything about this feature. Is really recommended to disable it? Is it needed for the ISSU procedure?
Thank you very much in advance!!
JOSU

Similar Messages

Upgrading Nexus 5548 UP, Release 5.1(3)N2(1b)

Hi,
I try upgrading my Nexus 5548 with the release 5.1(3)N2(1b)
But I see that the image is'y not compatibible with the module 1 !!!
I followed the Upgrade and Downgrade Guide.
Help me.
********************************************** CLI output *************
sw-tdb-nx5548-1# show install all status
This is the log of last installation.
Verifying image bootflash:/n5000-uk9-kickstart.5.1.3.N2.1.bin for boot variable "kickstart".
SUCCESS
Verifying image bootflash:/n5000-uk9.5.1.3.N2.1b.bin for boot variable "system".
SUCCESS
Verifying image type.
SUCCESS
Extracting "system" version from image bootflash:/n5000-uk9.5.1.3.N2.1b.bin.
SUCCESS
Extracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.5.1.3.N2.1.bin.
SUCCESS
Extracting "bios" version from image bootflash:/n5000-uk9.5.1.3.N2.1b.bin.
SUCCESS
Extracting "fexth" version from image bootflash:/n5000-uk9.5.1.3.N2.1b.bin.
SUCCESS
Recommended action::
"Module 1 might not be supported in the new image,
it should be powered off before proceeding with install".
Performing module support checks.
SUCCESS
Notifying services about system upgrade.
SUCCESS
Compatibility check is done:
Module bootable          Impact Install-type Reason
     1        no             n/a           n/a Incompatible image
   101       yes non-disruptive       rolling
Images will be upgraded according to following table:
Module       Image         Running-Version             New-Version Upg-Required
     1      system             5.1(3)N2(1)            5.1(3)N2(1b)            no
     1   kickstart             5.1(3)N2(1)             5.1(3)N2(1)            no
     1        bios      v3.5.0(02/03/2011)      v3.5.0(02/03/2011)            no
     1      SFP-uC                v1.0.0.0                v1.0.0.0            no
   101       fexth             5.1(3)N2(1)            5.1(3)N2(1b)           yes
     1   power-seq                    v1.0                    v1.0            no
     3   power-seq                    v2.0                    v2.0            no
     1          uC                v1.2.0.1                v1.2.0.1            no
sw-tdb-nx5548-1#
sw-tdb-nx5548-1#
sw-tdb-nx5548-1#

I was using an bad command, the right one is:
install all kickstart bootflash:n5000-uk9-kickstart.5.1.3.N2.1b.bin system bootflash:n5000-uk9.5.1.3.N2.1b.bin
Now the Nexus is upgraded.
Regards

NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX

Hi All,
Please tell me how to do "NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX" without downtime for FEX.
The Server are connected to FEX.
Attached the diagram.

Hi,
If the 5500s are layer-2 with vPC running between them than you can use ISSU to upgade.
here is doc to follow:
ISSU Support for vPC Topologies
An ISSU is completely supported when two switches are paired in a vPC configuration. In a vPC configuration, one switch functions as a primary switch and the other functions as a secondary switch .They both run the complete switching control plane, but coordinate forwarding decisions to have optimal forwarding to devices at the other end of the vPC. Additionally, the two devices appear as a single device that supports EtherChannel (static and 802.3ad) and provide simultaneously data forwarding services to that device.
While upgrading devices in a vPC topology,you should start with the switch that is the primary switch. The vPC secondary device should be upgraded after the ISSU process completes successfully on the primary device. The two vPC devices continue their control plane communication during the entire ISSU process (except when the ISSU process resets the CPU of the switch being upgraded).
This example shows how to determine the vPC operational role of the switch:
link:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/upgrade/513_N1_1/n5k_upgrade_downgrade_513.html
HTH

Nexus 5548 Upgrading NX-OS ?

If I want to upgrade our 5548's to the latest OS, do I also have to upgrade to the latest kickstart version as well ?
Any help would be appreciated.
Cheers
Dave

Thanks for the reply. Got both switches upgraded last night, once I figured out to create a management VRF and FTP
from that vlan to the switch.
Cheers
Dave

Urgent help: L3 daughter card for Nexus 5548

Hi
We have 2 Nexus 5548 which is in one vPC doamin. All the servers are teamed to these switches
Requirement
We have to install New L3 daughter card.(N55-D160L3-V2(=))
I have gone through the Cisco websites and found that we have to do the following things
1. software version:
i Nexus 5548P Daughter Card (N55-D160L3)
Before installing a Layer 3 daughter card (N55-D160L3) into a Cisco Nexus 5548P switch, you must upgrade to Cisco NX-OS Release 5.0(3)N1(1b) or NX-OS Release 5.0(3)N1(1c) and then install the card into the chassis.
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/release/notes/Rel_5_0_3_N2_1/Nexus5000_Release_Notes_5_0_3_N2.html
2. license:
Also in order to enable this module following license should present on N5k device:
LAN_BASE_SERVICES_PKG - it's free and lifetime.
https://supportforums.cisco.com/thread/2121574
I have 2 questions
1- In cisco documentation its says that these cards will be installed in the front where I/O module is and after NX OS 5.X they are hot swappable
Does that mean that no reboot will be required after installing this module (keeping in mind its the first time) so i am confused about the wording ???
Does license installation requires reboot??? in short if you are installing for the first time do we require a reboot ???? that is my main question
2- I have heard there is a known bug which keep rebooting the switch after installation of L3 card
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl45495
has that been address in any version of license or NS-OS yet???
Thanks heaps guys
If the module is still offline when the requirements are met above, it could be a bug.(CSCtl45495) Try reloading the switch.

1- In cisco documentation its says that these cards will be installed in the front where I/O module is and after NX OS 5.X they are hot swappable
Does that mean that no reboot will be required after installing this module (keeping in mind its the first time) so i am confused about the wording ???
Answer: -- Yes no reboot is required.
Does license installation requires reboot??? in short if you are installing for the first time do we require a reboot ???? that is my main question
Answer: As you are installing the license for the first time reboot of the box is not required.
2- I have heard there is a known bug which keep rebooting the switch after installation of L3 card
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl45495
has that been address in any version of license or NS-OS yet???
Answer;--No this is not fixed yet.
HTH
Regards
Inayath
********Please do not forget to rate the post if this info is helpfull.

Nexus 5548 Layer 3 daughter card insertion

Hello there,
I am planning to install Nexus 5548 Layer 3 daughter card. I found the hardware removal procedure on Cisco website but it doesn't say whether it's hot plugged or not. (Since I've to remove existing L2 module so I guess the box needs to be powered off but not sure). Has anybody had the experience in doing the upgrade to share?
Thanks in advance
Regards,
Chinnawoot
PS. Detail of the running system
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
AUUT05TRUSDS03# show ver
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS:      version 3.6.0
loader:    version N/A
kickstart: version 7.0(1)N1(1)
system:    version 7.0(1)N1(1)
Power Sequencer Firmware:
             Module 1: version v2.0
             Module 3: version v2.0
Microcontroller Firmware:        version v1.2.0.1
SFP uC:    Module 1: v1.0.0.0
QSFP uC:   Module not detected
BIOS compile time:       05/09/2012
kickstart image file is: bootflash:///n5000-uk9-kickstart.7.0.1.N1.1.bin
kickstart compile time: 3/19/2014 14:00:00 [03/20/2014 10:09:46]
system image file is:    bootflash:///n5000-uk9.7.0.1.N1.1.bin
system compile time:     3/19/2014 14:00:00 [03/20/2014 13:54:43]
Hardware
cisco Nexus5548 Chassis ("O2 32X10GE/Modular Universal Platform Supervisor")
Intel(R) Xeon(R) CPU         with 8253860 kB of memory.
Processor Board ID FOC172441CQ
Device name: AUUT05TRUSDS03
bootflash:    1966080 kB
Kernel uptime is 172 day(s), 21 hour(s), 56 minute(s), 9 second(s)
Last reset at 126063 usecs after Wed May 21 12:35:50 2014
Reason: Reset Requested by CLI command reload
System version: 7.0(1)N1(1)
Service: power-sequence cycled
plugin
Core Plugin, Ethernet Plugin
AUUT05TRUSDS03# show lic usage
Feature                      Ins Lic   Status Expiry Date Comments
                                 Count
FCOE_NPV_PKG                  No    -   Unused             -
FM_SERVER_PKG                 No    -   Unused             -
ENTERPRISE_PKG                No    -   Unused             -
FC_FEATURES_PKG               No    -   Unused             -
VMFEX_FEATURE_PKG             No    -   Unused             -
ENHANCED_LAYER2_PKG           Yes   -   Unused Never       -
LAN_BASE_SERVICES_PKG         No    -   Unused             -
LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -

I ended up getting the answer from TAC. First put in these two commands:
test ethpm l3 enable-show-iport
test port-channel l3 enable-show-ipc
Then you will get some new port channels showing up (127 and 128).
I'm not sure what 128 is for, but 127 is the internal port channel for the L3 card. Then you can view stats and poll with SNMP against the interface...
show interface port-channel 127

FCoE with Cisco Nexus 5548 switches and VMware ESXi 4.1

Can someone share with me what needs to be setup on the Cisco Nexus side to work with VMware in the following scenario?
Two servers with two cards dual port FCoE cards with two ports connected to two Nexus 5548 switches that are clusterd together. We want to team the ports together on the VMware side using IP Hash so what should be done on the cisco side for this to work?
Thanks...

Andres,
The Cisco Road Map for the 5010 and 5020 doesn't include extending the current total (12) FEX capabities. The 5548 and 5596 will support more (16) per 55xxk, and with the 7K will support upto 32 FEX's.
Documentation has been spotty on this subject, because the term 5k indicates that all 5000 series switches will support extended FEX's which is not the case only the 55xx will support more than 12 FEX. Maybe in the future the terminology for the 5k series should be term 5000 series and 5500 series Nexus, there are several differences and advancements between the two series.

Prime Infrastructure 2.0 and Nexus 5548, SSH credentials fail

Hi,
I'm having problem getting the Prime Infrastructure 2.0 to login with SSH to a Nexus 5548 to do an inventory. I get "Wrong Telnet/SSH credentials". But when I use the same credentials from another SSH-client it works fine. I also tested to SSH from the console of the Prime-server and that also works fine.
Any ideas???
Regards,
Stefan Lindkvist

I have PI 2.0 working against Nexus 5k's in two different installations. See below for an example (click to enlarge).
Have you put in an entry in both the login and enable fields (even though they are not separately required when logging in directly)?

Telephony Issues on Nexus 5548

Dear Viewers,
I have Nexus 5548 devices in one of my client data centers and i have one 3750 switch to which all of these Avaya voice servers connect.
The 3750 switch was initially connected through a L2 Link to a 6509 catalyst switch and the telephony applications were working correctly.
The problem arises when i move this 3750 layer 2 link to a Nexus 5548 (OS version 5.1(3)N1 switch. All telephony calls coming from the outside (External calls) are not working as required but the internal calls work as usual.
What is odd is that when i migrate this L2 link back to the 6509 switch, all works as usual. This is just a layer 2 connection and i am wondering why this is not possible.
The vlan is accepted on all relevant trunks. I also deactivated igmp snooping on this voice vlan on the Nexus 5548 thinking it would help but in vain.
Any ideas and suggestions are welcome.
regards.
Alain

This is my radius config...... on a 5K
radius-server timeout 7
radius-server host 10.28.42.20 key 7 "Password" auth-port 1645 acct-port 1646 authentication accounting
radius-server host 10.28.42.21 key 7 "Password" auth-port 1645 acct-port 1646 authentication accounting
aaa group server radius Radius-Servers
server 10.28.42.20
server 10.28.42.21
aaa authentication login default group Radius-Servers
ip radius source-interface Vlan1
aaa authentication login default fallback error local
And it is currently working. On the radius server i also had to do this to make the users admins once logged in:
https://supportforums.cisco.com/document/137181/nexus-integration-admin-access-free-radius

Fabric with two Nexus-5548 and a brocade switch does not get fabric updates

We have a fabric containing two Nexus 5548 and a Brocade 5000 switch in interop mode 2. When i make changes to the zoning, the first nexus (the fabric principal) and the brocade switch see the zone changes. The second Nexus switch does not see it. There are no error messages but the change just can't be seen. What can i do to find out, what goes wrong ?

Ouch, deprecated is not the word i wanted to read
We are using 5.1(3)N1(1a) on nexus-rz1-a
and 6.0(2)N1(2) on nexus-rz2-a.
The fabric can be seen :
nexus-rz2-a# show fcs ie vsan 10
IE List for VSAN: 10
IE-WWN                   IE     Mgmt-Id Mgmt-Addr (Switch-name)
10:00:00:05:1e:90:57:27 S(Rem) 0xfffc01 10.88.133.110 (bc-san1)
20:0a:00:2a:6a:72:ba:01 S(Loc) 0xfffc1c 10.88.133.105 (nexus-rz2-a)
20:0a:54:7f:ee:7f:dc:01 S(Adj) 0xfffc0b 10.88.133.100 (nexus-rz1-a)
[Total 3 IEs in Fabric]
nexus-rz1-a# show fcs ie vsan 10
IE List for VSAN: 10
IE-WWN                   IE     Mgmt-Id Mgmt-Addr (Switch-name)
10:00:00:05:1e:90:57:27 S(Adj) 0xfffc01 10.88.133.110 (bc-san1)
20:0a:00:2a:6a:72:ba:01 S(Adj) 0xfffc1c 10.88.133.105 (nexus-rz2-a)
20:0a:54:7f:ee:7f:dc:01 S(Loc) 0xfffc0b 10.88.133.100 (nexus-rz1-a)
[Total 3 IEs in Fabric]
I try to distribute the zoneset this way:
zoneset distribute vsan 10
Zoneset distribution initiated. check zone status
nexus-rz1-a# show zone status
VSAN: 10 default-zone: deny distribute: full Interop: 2
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: unsupported
Full Zoning Database :
    DB size: 6291 bytes
    Zonesets:1 Zones:62 Aliases: 44
Active Zoning Database :
    DB size: 10243 bytes
    Name: FABRIC1 Zonesets:1 Zones:60
Status: Zoneset distribution completed at 08:06:00 UTC Dec 3 2013
nexus-rz2-a# show zone status
VSAN: 1 default-zone: deny distribute: active only Interop: default
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: unsupported
Full Zoning Database :
    DB size: 4 bytes
    Zonesets:0 Zones:0 Aliases: 0
Active Zoning Database :
    Database Not Available
Status:
VSAN: 10 default-zone: deny distribute: full Interop: 2
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: unsupported
Full Zoning Database :
    DB size: 6291 bytes
    Zonesets:1 Zones:62 Aliases: 44
Active Zoning Database :
    DB size: 10243 bytes
    Name: FABRIC1 Zonesets:1 Zones:60
Status: Activation completed at 13:03:42 UTC Dec 2 2013

Install pbr feature nexus 5548

I am in need of Policy Based Routing for a new project. At my core I have a couple of Nexus 5548s clustered together. I go into configure terminal and run the command "feature pbr" and the return is invalid. So I check the license with the command "show license usage" and I get the following output:
Feature Ins Lic Status Expiry Date Comments
Count
FCOE_NPV_PKG No - Unused -
FM_SERVER_PKG No - Unused -
ENTERPRISE_PKG Yes - Unused Never -
FC_FEATURES_PKG Yes - Unused Never -
VMFEX_FEATURE_PKG No - Unused -
ENHANCED_LAYER2_PKG No - Unused -
LAN_BASE_SERVICES_PKG Yes - In use Never -
LAN_ENTERPRISE_SERVICES_PKG Yes - Unused Never -
From here I see that the enterprise package is installed and is unused. How can I gain access to the enterprise features? I found a document here that says "Ensure that you are in the correct VDC (or use the switchto vdc command). " The switchto vdc command is also invalid. What am I missing?
Eric

I realise this is a very old post however I wanted to post here in case others are still looking for this feature. PBR is now supported in version 6.0(2)N2(1) on Nexus 5k.
RELEASE NOTES: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/release/notes/6_02/Nexus5500_Release_Notes_6_02.html#pgfId-472355

Command to see transmit qeueing drops in Nexus 5548

Hello, 10g links in our core are getting rather congested as seen by MRTG graphs. Any command on Nexus 5548 to show transmit queuing drops on a given interface?

You could use #show queing interface eth 1/1
it shows you output similar as below:
NEXUS-1# show queuing interface ethernet 1/1
Ethernet1/1 queuing information:
TX Queuing
    qos-group sched-type oper-bandwidth
        0       WRR            100
RX Queuing
    qos-group 0
    q-size: 470080, HW MTU: 9216 (9216 configured)
    drop-type: drop, xon: 0, xoff: 470080
    Statistics:
        Pkts received over the port             : 222434
        Ucast pkts sent to the cross-bar        : 199674
        Mcast pkts sent to the cross-bar        : 22760
        Ucast pkts received from the cross-bar : 101087
        Pkts sent to the port                   : 145083
        Pkts discarded on ingress               : 0
        Per-priority-pause status               : Rx (Active), Tx (Inactive)
Total Multicast crossbar statistics:
    Mcast pkts received from the cross-bar      : 43996

TACACS Nexus 5548 Authorization

I am having an issue with authorization on the Nexus 5548. Note: The tacacs configuration has and still works correctly with all non-Nexus gear.
Authentication succeeds, and initiatial authorization passes. However, all sh and config commands fail, though AAA Autho Config-Commands .... and Commands Default Group <Grp Name), are configured.
ACS generates the following error: 13025 Command failed to match a Permit rule. The Selected Command Set is DenyAllCommands. I created an AllowAll, but am unclear how to associate this with Access Policy.
Any help would be greatly appreciated.

Hello,
Hope the attached document points you into the right direction.
Regards.

Nexus 5548 L3 daughter card flapping

Hi guys,
Anyone of you here that experienced the logs below on their Nexus box:
2011 Dec 12 06:24:45 GDCNXS5K01 %BTCM-2-BTCM_LOG_ROUTER_ERR: router card in slot 3 has internal link(s) flapped: router ports down: 0x1a108000 0x1a109000 0x1a10a000 0x1a10b000 0x1a10c000 0x1a10d000 0x1a10e000 0x1a10f000
I am getting this log at least once a day. Seems like it is shutting down the SVI of the box after the said log occured. Good thing I have enable vPC and I am able to access the NXS5K through the vCP keepalive link (mgmt).
I have two Nexus 5548, but only one is experiencing the said error.
Any inputs, suggestions would be greatly appreciated.
Thanks,
Edzel

We had this same problem this past weekend, only in module 2 on a 5596.
In our case, we had rebooted our primary Nexus and found the following message immediately preceeded the BTCM error you noted:
%$ VDC-1 %$ %NOHMS-2-NOHMS_DIAG_ERROR: Module 2: Bootup diag detected major event: Forwarding ASIC failure: Ethernet2/9 Ethernet2/10 Ethernet2/11 Ethernet2/12 Ethernet2/13 Ethernet2/14 Ethernet2/15 Ethernet2/16
We replaced the module. A "show diag results module 3" would probably show you the same thing. However, I don't think the error message will show up until you reboot.
If your flapping Nexus is secondary, you probably won't notice anything major, but if it is your primary, it would probably affect your routing.

Servers connected to Nexus 5548 only getting 200 Mbps of throughput

Servers connected to NExus 5k were only getting 100 Mbps of throughput. So I disabled Flow control recieve on all the ports. After this we are getting 200 Mbps of speed. The servers are connected throuh 10 gig port. Could you guys please suggest why the throguhput is still low? Atleast we should get 1Gbps of thrpoughput.

Hi Adam,
I think we probably need a little more information to go on. Can you answer the following?
What type of servers and NICs?
What OS are you running on the servers?
What cables do you have from the servers to the switch?
Are the two servers in the same subnet or is the traffic between them routed?
If routed, is that in the Nexus 5548 or some other router?
How are you testing throughput?
Presumably you're not seeing any errors on the switch ports that the servers are connected to?
Regards

Upgrading Nexus 5548

Similar Messages

Maybe you are looking for