Nexus 5548 - VM Traffic through Nexus failed

Hi guys,
I am having a Nexus switching problem in a data center.
VM traffic failed through the nexus switches, i run a ping test and the test is fail and back to success after few minutes, after a minute of success ping it is fail again.
Also when the nexus don't reach the tacacs this indicate us that we lose the VMs.
The issue affect the virtual servers and does not affect other servers. The virtual machine is VMWare with ESX and Vcenter.
Please look at the attach topology:
The issue happen in MST Region X.
We tried to disconnect MST Region Y and the issue is remain the same.
The 2 6500 switches in the bottom of the diagram runs GLBP for servers' default gateway.
Also, there is some downstream switches that connected to the 6500 switches and not apear in the diagram.
I found a workaround - If i configure on one of the 6500 in MST Region X on Port-channel 1 spanning-tree mst 0-1 cost 20 the issue is solved.
ESX server connectivity architecture:
6 nics. 2 for management and vmotion, 2 for NFS traffic, 2 for VM traffic.
Management and vmotion couple are configured as a team where one of the nics is primary for management and the second is primary for vmotion.
The NFS couple are configured the same.
The 2 nics configured for VM traffic are configured as active active.
Mode of connection: all connections are trunk.
Someone?

Hi,
Finally, we found the problem.
We configure on the 6500's links - mtu 9216.
The VMs was disconnect cause the NFS generates jumbo frames.
Thanks a lot.

Similar Messages

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)?

Nexus 5548 and Define static route to forward traffic to Catalyst 4500

Dear Experts,
Need your technical assistance for the Static routing in between Nexus 5548 and Catalyst 4500.
Further I connected both Nexus 5548 with Catalyst 4500 as individual trunk ports because there is HSRP on Catalyst 4500. So I just took 1 port from each nexus 5548, make it trunk with the Core Switch (Also make trunk from each Switch each port). Change the speed on Nexus to 1000 because other side on Catalyst 4500 line card is 1G RJ45.
*Here is the Config on Nexus 5548 to make port a Trunk:*
N5548-A/ N5548-B
Interface Ethernet1/3
Switchport mode trunk
Speed 1000
Added the static route on both nexus for Core HSRP IP: *ip route 0.0.0.0/0 10.10.150.39 (Virtual HSRP IP )*
But I could not able to ping from N5548 Console to core Switch IP of HSRP? Is there any further configuration to enable routing or ping?
Pleas suggest

Hello,
Please see attached config for both Nexus 5548. I dont have Catalyst 4500 but below is simple config what I applied:
Both Catalyst 4500
interface gig 3/48
switchport mode trunk
switchport trunk encap dot1q
On Nexus 5548 Port 1/3 is trunk
Thanks,
Jehan

FCoE using Brocade cards CNA1020 and Cisco Nexus 5548 switches

All,
I have the following configuration and problem that I am not sure how to fix:
I have three Dell R910 servers with 1TB of memory and each has two brocade 1020 CNA cards dual port. I am using distributed switches for the VM network and a second distributed switch for VMotion. I have two of the 10G ports configured in each distributed switch using IP Hash. The management network is configured using a standard switch with two 1G ports.
The Nexus configuration is we have two nexus 5548 switch connected together with a trunk. We have two VPC's configured to each ESX hosts consisting of two 10gig ports in each VPC with one port going to each switch. The VPC is configured for static LAG.
What I am seeing is that after a few hours the virtual machines will not be accessible via network anymore. So if you ping the VM it will not work and if you get on the console of the VM then ping the gateway then nothing as well but if you try to ping another virtual machine on the same host on the same VLAN then it will work so traffic is going through the ESX backplane. If I reboot the ESX host then things will work again for another few hours or so then the problem repeats.
The version of vSphere I am using is ESXi4.1
Please assist I am stuck.
Thanks...

Here is the link for Nexus and Brocade interoperability Matrix
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix7.html#wp313498
usually this table would show those models those have been tested and verified
However I do not see Brocade 5300 listed in the table . It could be, interoperability may have not been tested by both vendors perticularly to 5300 type Model.

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

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

Help please with TACACS authentication from a Nexus 5548

I cannot get login working via TACACS from my Nexus 5548. I've tried creating a group and a single server with key etc.
Config is simple:
tacacs-server key 7 ************
ip tacacs source-interface Vlanx
aaa group server tacacs+ tacacs
server 10.x.y.z
The test aaa command shows it's authenticating:
NEX01# test aaa server tacacs+ 10.x.y.z <username> <password)
user has been authenticated
Debug shows this:
NEX01# 2011 Jun 8 12:31:03 NEX01 %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication failed for user <username> from 10.x.y.z- login[1691]
Am I doing something glaringly wrong here?
Any advice is greatly appreciated.
Thank you.

Hi Paul,
Looks like may be the packet dont have the route ACS when you try to login .
Can you share sh run of the switch ?
Also do you see failed attempt on tacacs server side. ?
Can you ping tacacs server with source interface Vlanx?
Thanks
Waris Hussain

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.

Very low transfer speed issue on SUN4270 M2 server connected with nexus 5548 switch on 10GB fiber.

                   Hi,
I have 2 SUN 4270 M2 servers connected with Nexus 5548 switch over 10Gb fiber card. I am getting performance of just 60 MB per second while transfer of 5Gb file across 2 servers. The similar speed i use to get on 1Gb network also. Please suggest how to improve the tranfer speed. On servers, ports ET4 and ETH5 are bonded in bond0 with mode=1. The server envrionment will be used for OVS 2.2.2.
Below are the details of network configuration on server. I quick help will be highly appriciated--
[root@host1 network-scripts]# ifconfig eth4
eth4      Link encap:Ethernet HWaddr 90:E2:BA:0E:22:4C
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
          RX packets:5648589 errors:215 dropped:0 overruns:0 frame:215
          TX packets:3741680 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2492781394 (2.3 GiB) TX bytes:3911207623 (3.6 GiB)
[root@host1 network-scripts]# ifconfig eth5
eth5      Link encap:Ethernet HWaddr 90:E2:BA:0E:22:4C
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
          RX packets:52961 errors:215 dropped:0 overruns:0 frame:215
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3916644 (3.7 MiB) TX bytes:0 (0.0 b)
[root@host1 network-scripts]# ethtool eth4
Settings for eth4:
        Supported ports: [ FIBRE ]
        Supported link modes:   1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 1000baseT/Full
                                10000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 10000Mb/s
        Duplex: Full
        Port: FIBRE
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes
[root@host1 network-scripts]# ethtool eth5
Settings for eth5:
        Supported ports: [ FIBRE ]
        Supported link modes:   1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 1000baseT/Full
                                10000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 10000Mb/s
        Duplex: Full
        Port: FIBRE
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes
[root@host1 network-scripts]#
[root@host1 network-scripts]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.2.4 (January 28, 2008)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth4
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth4
MII Status: up
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:0e:22:4c
Slave Interface: eth5
MII Status: up
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:0e:22:4d
[root@host1 network-scripts]# modinfo ixgbe | grep ver
filename:       /lib/modules/2.6.18-128.2.1.4.44.el5xen/kernel/drivers/net/ixgbe/ixgbe.ko
version:        3.9.17-NAPI
description:    Intel(R) 10 Gigabit PCI Express Network Driver
srcversion:     31C6EB13C4FA6749DF3BDF5
vermagic:       2.6.18-128.2.1.4.44.el5xen SMP mod_unload Xen 686 REGPARM 4KSTACKS gcc-4.1
[root@host1 network-scripts]#brctl show
bridge name     bridge id               STP enabled     interfaces
vlan301         8000.90e2ba0e224c       no              bond0.301
vlan302         8000.90e2ba0e224c       no              vif1.0
                                                        bond0.302
vlan303         8000.90e2ba0e224c       no              bond0.303
vlan304         8000.90e2ba0e224c       no              bond0.304
[root@host2 test]# ifconfig eth5
eth5      Link encap:Ethernet HWaddr 90:E2:BA:0F:C3:15
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
          RX packets:4416730 errors:215 dropped:0 overruns:0 frame:215
          TX packets:2617152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:190977431 (182.1 MiB) TX bytes:3114347186 (2.9 GiB)
[root@host2 network-scripts]# ifconfig eth4
eth4      Link encap:Ethernet HWaddr 90:E2:BA:0F:C3:15
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
          RX packets:28616 errors:3 dropped:0 overruns:0 frame:3
          TX packets:424 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4982317 (4.7 MiB) TX bytes:80029 (78.1 KiB)
[root@host2 test]#
[root@host2 network-scripts]# ethtool eth4
Settings for eth4:
        Supported ports: [ FIBRE ]
        Supported link modes:   1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 1000baseT/Full
                                10000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 10000Mb/s
        Duplex: Full
        Port: FIBRE
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes
[root@host2 test]# ethtool eth5
Settings for eth5:
        Supported ports: [ FIBRE ]
        Supported link modes:   1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 1000baseT/Full
                                10000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 10000Mb/s
        Duplex: Full
        Port: FIBRE
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes
[root@host2 network-scripts]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.2.4 (January 28, 2008)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth5
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth5
MII Status: up
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:0f:c3:14
Slave Interface: eth4
MII Status: up
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:0f:c3:15
[root@host2 network-scripts]# modinfo ixgbe | grep ver
filename:       /lib/modules/2.6.18-128.2.1.4.44.el5xen/kernel/drivers/net/ixgbe/ixgbe.ko
version:        3.9.17-NAPI
description:    Intel(R) 10 Gigabit PCI Express Network Driver
srcversion:     31C6EB13C4FA6749DF3BDF5
vermagic:       2.6.18-128.2.1.4.44.el5xen SMP mod_unload Xen 686 REGPARM 4KSTACKS gcc-4.1
[root@host2 network-scripts]#brctl show
bridge name     bridge id               STP enabled     interfaces
vlan301         8000.90e2ba0fc315       no              bond0.301
vlan302         8000.90e2ba0fc315       no              bond0.302
vlan303         8000.90e2ba0fc315       no              bond0.303
vlan304         8000.90e2ba0fc315       no              vif1.0
       bond0.304
Thanks....
Jay

Hi,
Thanks for reply..but the RX errors count is keep on increasing and the transfer speed between 2 servers are max 60MB/ps on 10GB FC card. Even on storage also, i am getting the same speed when i try to transfer data from server to storage on 10GB FC card. Servers and storage are connected through Nexus 5548 switch.
#ifconfig eth5
eth5      Link encap:Ethernet HWaddr 90:E2:BA:0E:22:4C
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
          RX packets:21187303 errors:1330 dropped:0 overruns:0 frame:1330
          TX packets:17805543 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:624978785 (596.0 MiB) TX bytes:2897603160 (2.6 GiB)
JP

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.

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

Nexus 5548 - VM Traffic through Nexus failed

Similar Messages

Maybe you are looking for