Default interface command in Cisco Nexus 5000

It doesn't still work in 6.0.2.N1.1
xxx# sh version
Software
BIOS: version 3.6.0
loader: version N/A
kickstart: version 6.0(2)N1(1)
system: version 6.0(2)N1(1)
Power Sequencer Firmware:
Module 1: version v5.0
Module 2: version v1.0
Module 3: version v1.0
Module 4: version v1.0
Microcontroller Firmware: version v1.0.0.2
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.6.0.2.N1.1.bin
kickstart compile time: 1/29/2013 7:00:00 [01/29/2013 19:40:46]
system image file is: bootflash:///n5000-uk9.6.0.2.N1.1.bin
system compile time: 1/29/2013 7:00:00 [01/29/2013 21:44:48]
xxx(config)# default interface eth 3/16 ?
^
% Invalid parameter detected at '^' marker.
^
% Invalid parameter detected at '^' marker.

Sure.  Try this:
conf t
archive
!           “$h” means the appliance’s hostname will be the filename.  The filename format is hostname-month-!day-hour-minute-seconds-timezone-version, like “Hostname-Apr-23-10-51-13-AEST-0”.
!           Make sure you put a “-“ at the end of the “$h”.  Compare the two and you’ll see.  J
!           If you are using Windows to store these files, DO NOT USE “$t” because it won’t work.  Cisco will store the timestamps as “:” and Windows don’t like it. 
!           You can use TFTP, FTP, SCP and some more stuffs. 
  path tftp:///Subdirectory/$h-
!           The next two lines means that this command will run when someone saves the configuration and/or at a certain time, like 24 hours or weekly. 
  time-period
  write-memory
end

Similar Messages

  • Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

    Welcome to the Cisco® Support Community Ask the Expert conversation.  This is an opportunity to learn and ask questions about Cisco® NX-OS.
    The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
    vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
    This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
    Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
    Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
    Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response. 
    Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Hello Gustavo
    Please see my responses to your questions:
    Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
    Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
    http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
    Now for Data Plane we have two types of traffic – Unicast and Multicast.
    The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
    Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
    For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
    The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
    Similarity: For both products, loop avoidance is possible due to VSL bit
    The VSL bit is set in the DBUS header internal to the Nexus.
    It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
    This mechanism is used for loop prevention within the chassis.
    The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
    Differences:  In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
    It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
    For more details please see below presentation:
    https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
    DCI Scenario:  If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
    But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
    Let us know if you have further questions.
    Thanks,
    Vishal

  • Default interface command for SG50052

    Hello 
    I am trying to set an interface back to its defaults but with no success at all. Actually is a trunk interface and I want to make it access again. With no switchport mode and then switchport mode trunk I get a message about wrong VLAN assignments.

    Hi,
    Configure as below:
    switchxxxxxx(config)# interface gi1
    switchxxxxxx(config-if)# no switchport mode trunk
    switchxxxxxx(config-if)# switchport mode access
    switchxxxxxx(config-if)# switchport access vlan 2(required vlan number)
    regards
    Moorthy

  • Cisco Nexus 5000 upgrade

        Is there any gotchas or things we should know when going from version  5.1(3)N2(1)   to a  7.X level code ?   Is it as simple as getting the code and kickstarter images on and then using the install command.  these are all single supervisor module boxes .  We are using single  attached fexes on these also .   I have read the install procedures and didn't seem to see anything while reading as an issue . This is the first time we have done the Nexus boxes so I wanted to throw this out there to people that have done this before .  Thanks ...

    There is nothing special about the upgrade.  The nice thing about 5ks is that they come with a USB ports.  So just load the images from USB to the switch and run the install command.
    Good Luck
    Reza

  • Comandos Nexus 5000

    Hola alguien me podria decir cual es el comendo en Nexus 5000 para mandar a Default una interface                  

    Hi,
    Disculpas, no hablo español. Apologies, I don't speak Spanish, but I think the answer you're looking for is as follows:
    From the Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(4) section of the Release Notes:
    CSCth06584 The enhancement request filed requesting the "default interface" capability in Cisco Nexus 5000 and 5500 Series switches.
    Regards

  • The meaning of Interface Ethernet250/1 under the Nexus 2000 is connected to Nexus 5000 switch

    Dear all,
       Recently, I prepared and deploy a network monitoring system to monitor the new generation Nexus connected network.  With using snmpwalk to query the interfacs information from the Nexus 5000 switch (one Nexus 2000 is connected to it via FlexLink), I found that other than normal Nexus 5000 and 2000 ports(ifName to be Ethernet1/1, Ethernet1/2, ... Ethernet190/1/1, Ethernet190/1/2...), a series of interface with ifName Ethernet250/1, Ethernet250/2, .... to be appeared in the interface SNMP tree.   With logged into the Nexus 5000 and issue display interface command, I can only found the information on the normal interfaces but not the abnormal interface Ethernet250/1, ...
       Would someone know what is it (do E250/1 is a logical interface like port channel or VLAN) and how to monitor it ?  Thanks in advances.
    HC Wong

    I've not seen that myself. Could it perhaps be a VPC (Virtual Portchannel)?

  • PFC configuration on Nexus 5000

    Hi,
    I have a CNA in my server connected to cisco nexus 5000 interfcae. I Want to genearate pause frames for FCOE class of traffic using the default class class-fcoe and cos value 3, the firmware version running is 5.0(3) N1 (1b). Can anyone tell me how can i configure it ?
    Thanks,
    Manju

    Sorry for the delayed response, Here is what you asked
    Cisco-5020# sh mod
    Mod Ports  Module-Type                      Model                  Status
    1    40     40x10GE/Supervisor               N5K-C5020P-BF-SUP      active *
    2    8      4x10GE + 4x1/2/4G FC Module      N5K-M1404              ok
    Mod  Sw              Hw      World-Wide-Name(s) (WWN)
    1    5.0(3)N1(1b)    1.2     --
    2    5.0(3)N1(1b)    1.0     20:41:00:0d:ec:b2:15:40 to 20:44:00:0d:ec:b2:15:40
    Mod  MAC-Address(es)                         Serial-Num
    1    000d.ecb2.1548 to 000d.ecb2.156f         JAF1303ACES
    2    000d.ecb2.1570 to 000d.ecb2.1577         JAF1245AJLF
    Cisco-5020#
    Cisco-5020#
    Cisco-5020# sh run
    !Command: show running-config
    !Time: Fri Oct 28 17:40:02 2005
    version 5.0(3)N1(1b)
    feature fcoe
    feature npiv
    feature telnet
    feature lldp
    username admin password 5 $1$v9Tm8Y77$ZSdbOfBxe1.Z9Oz1V9V2B0  role network-admin
    no password strength-check
    ip domain-lookup
    hostname Cisco-5020
    logging event link-status default
    service unsupported-transceiver
    class-map type qos class-fcoe
    class-map type queuing class-all-flood
      match qos-group 2
    class-map type queuing class-ip-multicast
      match qos-group 2
    class-map type network-qos class-all-flood
      match qos-group 2
    class-map type network-qos class-ip-multicast
      match qos-group 2
    policy-map type network-qos jumbo
      class type network-qos class-fcoe
        pause no-drop
        mtu 2158
      class type network-qos class-default
        mtu 9216
    system qos
      service-policy type network-qos jumbo
    snmp-server user admin network-admin auth md5 0x2694501fdfbe5abed9e85d51e4e31038 priv 0x2694501fdfbe5abed9e85d51e4e31038 localizedkey
    snmp-server host 138.239.198.184 traps version 2c public  udp-port 1163
    snmp-server host 138.239.198.184 traps version 2c public  udp-port 1164
    snmp-server host 138.239.198.200 traps version 2c public  udp-port 1163
    snmp-server host 138.239.198.200 traps version 2c public  udp-port 1164
    snmp-server host 138.239.200.118 traps version 2c public  udp-port 1163
    snmp-server host 138.239.198.200 traps version 2c public  udp-port 1163
    snmp-server enable traps entity fru
    snmp-server community snmpv3 group network-operator
    vrf context management
      ip route 0.0.0.0/0 10.192.207.254
    vlan 1-2,8
    vlan 10
      fcoe vsan 10
    vlan 20
      fcoe vsan 20
    vlan 30
    vlan 35
      fcoe vsan 35
    vlan 40,50
    vlan 52
      fcoe vsan 52
    vsan database
      vsan 20
      vsan 52
    fcdomain fcid database
      vsan 52 wwn 10:00:00:00:c9:b1:e5:3d fcid 0x180000 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:3b fcid 0x180001 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:4d:e3 fcid 0x180002 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:ad fcid 0x180003 dynamic
      vsan 52 wwn 10:00:00:00:c9:ad:ac:41 fcid 0x180004 dynamic
      vsan 52 wwn 10:00:00:00:c9:ad:ac:b9 fcid 0x180005 dynamic
      vsan 52 wwn 10:00:00:00:c9:ad:ac:b5 fcid 0x180006 dynamic
      vsan 52 wwn 10:00:00:00:c9:f2:73:d1 fcid 0x180007 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:4d:e1 fcid 0x180008 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:a9 fcid 0x180009 dynamic
      vsan 52 wwn 10:00:00:00:c9:f2:73:d5 fcid 0x18000a dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:5d fcid 0x18000b dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:9b fcid 0x18000c dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:99 fcid 0x18000d dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:5b fcid 0x18000e dynamic
      vsan 1 wwn 10:00:00:00:c9:f2:73:b3 fcid 0x050000 dynamic
      vsan 52 wwn 10:00:00:00:c9:ad:ac:47 fcid 0x18000f dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a7:93 fcid 0x180010 dynamic
      vsan 52 wwn 10:00:00:00:c9:91:f8:19 fcid 0x180011 dynamic
      vsan 52 wwn 10:00:00:00:c9:9c:e0:77 fcid 0x180012 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a7:d3 fcid 0x180013 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a3:bb fcid 0x180014 dynamic
      vsan 52 wwn 10:00:00:00:c9:97:3b:c5 fcid 0x180015 dynamic
      vsan 52 wwn 10:00:00:00:c9:f2:73:91 fcid 0x180016 dynamic
      vsan 52 wwn 10:00:00:00:c9:a4:00:91 fcid 0x180017 dynamic
      vsan 52 wwn 10:00:00:00:c9:f2:73:8d fcid 0x180018 dynamic
      vsan 52 wwn 20:0f:00:11:0d:7f:a8:00 fcid 0x180019 dynamic
      vsan 52 wwn 20:0f:00:11:0d:7f:a8:01 fcid 0x18001a dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a3:b7 fcid 0x18001b dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a5:27 fcid 0x18001c dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a3:53 fcid 0x18001d dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:c8:37 fcid 0x18001e dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:76:e5 fcid 0x18001f dynamic
      vsan 20 wwn 10:00:00:00:c9:5b:a3:83 fcid 0xd30000 dynamic
      vsan 52 wwn 10:00:00:00:c9:91:00:00 fcid 0x180020 dynamic
      vsan 52 wwn 10:00:00:00:00:91:f7:f1 fcid 0x180021 dynamic
      vsan 1 wwn 10:00:00:00:c9:5b:4d:e3 fcid 0x050001 dynamic
      vsan 52 wwn 10:00:00:00:c9:97:3b:0f fcid 0x180022 dynamic
      vsan 52 wwn 10:00:00:00:c9:3c:8e:21 fcid 0x180023 dynamic
      vsan 52 wwn 10:00:00:00:c9:97:3b:11 fcid 0x180024 dynamic
      vsan 20 wwn 10:00:00:00:c9:b1:e6:b7 fcid 0xd30001 dynamic
      vsan 52 wwn 10:00:f8:19:00:91:f8:19 fcid 0x180025 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a3:8b fcid 0x180026 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e4:ff fcid 0x180027 dynamic
      vsan 52 wwn 10:00:00:00:c9:3c:8e:25 fcid 0x180028 dynamic
      vsan 52 wwn 50:06:01:61:44:60:23:4f fcid 0x1800ef dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:d6:b9 fcid 0x180029 dynamic
      vsan 52 wwn 10:00:00:00:c9:ad:ac:43 fcid 0x18002a dynamic
      vsan 52 wwn 20:01:00:00:c9:5b:ab:99 fcid 0x18002b dynamic
      vsan 52 wwn 20:02:00:00:c9:5b:ab:99 fcid 0x18002c dynamic
      vsan 52 wwn 50:06:01:60:44:60:23:4f fcid 0x1801ef dynamic
      vsan 52 wwn 10:00:00:00:c9:9d:1f:bf fcid 0x18002d dynamic
      vsan 52 wwn 10:00:00:00:c9:9d:1f:c1 fcid 0x18002e dynamic
      vsan 52 wwn 10:00:00:00:c9:f2:73:d3 fcid 0x18002f dynamic
      vsan 20 wwn 10:00:00:00:c9:bb:c8:37 fcid 0xd30002 dynamic
      vsan 52 wwn 10:00:00:00:c9:12:34:56 fcid 0x180030 dynamic
      vsan 52 wwn 10:00:00:00:c9:12:34:57 fcid 0x180031 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:ea:81 fcid 0x180032 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:ea:7f fcid 0x180033 dynamic
      vsan 20 wwn 10:00:00:00:c9:12:34:56 fcid 0xd30003 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:1b fcid 0x180034 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:1d fcid 0x180035 dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:c7:8f fcid 0x180036 dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:cb:8f fcid 0x180037 dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:cb:93 fcid 0x180038 dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:c7:93 fcid 0x180039 dynamic
      vsan 20 wwn 10:00:00:00:c9:12:34:57 fcid 0xd30004 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:c4 fcid 0x18003a dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:17:b7 fcid 0x18003b dynamic
      vsan 52 wwn 10:00:00:00:c9:a0:ce:2d fcid 0x18003c dynamic
      vsan 52 wwn 10:00:00:00:c9:91:f7:f1 fcid 0x18003d dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:c0 fcid 0x18003e dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:5f fcid 0x18003f dynamic
      vsan 52 wwn 10:00:00:00:c9:e3:06:89 fcid 0x180040 dynamic
      vsan 52 wwn 50:06:01:68:44:60:23:4f fcid 0x1802ef dynamic
      vsan 1 wwn 50:06:01:61:44:60:23:4f fcid 0x0500ef dynamic
      vsan 52 wwn 10:00:00:00:c9:d1:16:24 fcid 0x180041 dynamic
      vsan 52 wwn 10:00:00:00:c9:d1:16:25 fcid 0x180042 dynamic
      vsan 52 wwn 10:00:00:00:c9:d1:0a:6d fcid 0x180043 dynamic
      vsan 20 wwn 10:00:00:00:c9:d1:16:25 fcid 0xd30005 dynamic
      vsan 20 wwn 10:00:00:00:c9:d1:16:24 fcid 0xd30006 dynamic
      vsan 20 wwn ff:f2:00:00:c9:12:34:78 fcid 0xd30007 dynamic
      vsan 20 wwn ff:f2:00:00:c9:d1:16:46 fcid 0xd30008 dynamic
      vsan 52 wwn ff:f2:00:00:c9:d1:0a:8c fcid 0x180044 dynamic
      vsan 20 wwn ff:f3:00:00:c9:d1:16:46 fcid 0xd30009 dynamic
      vsan 52 wwn ff:f0:00:00:c9:d1:0a:8c fcid 0x180045 dynamic
      vsan 52 wwn 10:00:00:00:c9:d1:0a:6c fcid 0x180046 dynamic
      vsan 20 wwn ff:f2:00:00:c9:d1:0a:8c fcid 0xd3000a dynamic
      vsan 20 wwn 10:00:00:00:c9:d1:0a:6d fcid 0xd3000b dynamic
      vsan 52 wwn ff:f2:00:00:c9:d1:16:46 fcid 0x180047 dynamic
      vsan 20 wwn ff:f3:00:00:c9:12:34:78 fcid 0xd3000c dynamic
      vsan 52 wwn ff:f3:00:00:c9:12:34:78 fcid 0x180048 dynamic
      vsan 52 wwn 50:06:01:69:44:60:23:4f fcid 0x1803ef dynamic
      vsan 52 wwn ff:f3:00:00:c9:d1:16:46 fcid 0x180049 dynamic
      vsan 52 wwn 10:00:00:00:c9:12:34:5b fcid 0x18004a dynamic
      vsan 52 wwn 10:00:00:00:c9:12:34:5a fcid 0x18004b dynamic
      vsan 52 wwn ff:f2:00:00:c9:12:34:78 fcid 0x18004c dynamic
      vsan 52 wwn 10:00:00:00:c9:a5:ac:f3 fcid 0x18004d dynamic
      vsan 52 wwn 10:00:00:00:c9:a5:ad:15 fcid 0x18004e dynamic
      vsan 52 wwn 10:00:00:00:c9:a5:ac:f5 fcid 0x18004f dynamic
      vsan 52 wwn 20:01:00:00:c9:a5:ac:f3 fcid 0x180050 dynamic
      vsan 52 wwn 20:02:00:00:c9:a5:ac:f3 fcid 0x180051 dynamic
      vsan 52 wwn ff:f3:00:00:c9:12:34:85 fcid 0x180052 dynamic
      vsan 52 wwn 20:00:00:11:0d:77:9c:00 fcid 0x180053 dynamic
      vsan 52 wwn 20:01:00:11:0d:77:9d:00 fcid 0x180054 dynamic
    interface port-channel3
    interface vfc1
      no shutdown
    interface vfc4
    interface vfc9
      bind interface Ethernet1/9
      no shutdown
    interface vfc10
    interface vfc11
      bind interface Ethernet1/11
      no shutdown
    interface vfc19
      bind interface Ethernet1/19
      no shutdown
    interface vfc21
      bind interface Ethernet1/21
      no shutdown
    interface vfc22
      bind interface Ethernet1/22
      switchport trunk allowed vsan 52
      no shutdown
    interface vfc24
      bind interface Ethernet1/24
      switchport trunk allowed vsan 52
      no shutdown
    interface vfc25
      bind interface Ethernet1/25
      switchport trunk allowed vsan 52
      no shutdown
    interface vfc26
      bind interface Ethernet1/26
      switchport trunk allowed vsan 52
      no shutdown
    interface vfc27
      bind interface Ethernet1/27
      no shutdown
    interface vfc28
      bind interface Ethernet1/28
      no shutdown
    interface vfc29
      bind interface Ethernet1/29
      no shutdown
    interface vfc30
      bind interface Ethernet1/30
      switchport trunk allowed vsan 52
      no shutdown
    interface vfc31
      bind interface Ethernet1/31
      shutdown
    interface vfc32
      bind interface Ethernet1/32
      no shutdown
    interface vfc33
      bind interface Ethernet1/33
      no shutdown
    interface vfc34
      bind interface Ethernet1/34
      no shutdown
    interface vfc35
      bind interface Ethernet1/35
      no shutdown
    interface vfc36
      bind interface Ethernet1/36
      no shutdown
    interface vfc37
      bind interface Ethernet1/37
      no shutdown
    interface vfc38
      bind interface Ethernet1/38
      no shutdown
    interface vfc39
      bind interface Ethernet1/39
      no shutdown
    interface vfc40
      bind interface Ethernet1/40
      no shutdown
    vsan database
      vsan 52 interface vfc1
      vsan 52 interface vfc9
      vsan 52 interface vfc11
      vsan 52 interface vfc19
      vsan 52 interface vfc21
      vsan 52 interface vfc22
      vsan 52 interface vfc24
      vsan 52 interface vfc26
      vsan 52 interface vfc27
      vsan 52 interface vfc28
      vsan 52 interface vfc29
      vsan 52 interface vfc30
      vsan 52 interface vfc31
      vsan 52 interface vfc32
      vsan 52 interface vfc33
      vsan 52 interface vfc34
      vsan 20 interface vfc35
      vsan 52 interface vfc36
      vsan 52 interface vfc37
      vsan 52 interface vfc38
      vsan 52 interface vfc39
      vsan 52 interface vfc40
      vsan 52 interface fc2/1
      vsan 52 interface fc2/2
      vsan 52 interface fc2/3
      vsan 52 interface fc2/4
    interface fc2/1
      switchport trunk allowed vsan 1
      switchport trunk allowed vsan add 52
      switchport trunk mode auto
      no shutdown
    interface fc2/2
      switchport trunk mode auto
      no shutdown
    interface fc2/3
      no shutdown
    interface fc2/4
      no shutdown
    interface Ethernet1/1
    interface Ethernet1/2
      speed 1000
    interface Ethernet1/3
    interface Ethernet1/4
    interface Ethernet1/5
    interface Ethernet1/6
    interface Ethernet1/7
      switchport mode trunk
    interface Ethernet1/8
    interface Ethernet1/9
      switchport mode trunk
      switchport trunk allowed vlan 1,10,20,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/10
    interface Ethernet1/11
      priority-flow-control mode on
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/12
      switchport mode trunk
    interface Ethernet1/13
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/14
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/15
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/16
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/17
    interface Ethernet1/18
      switchport mode trunk
      switchport trunk allowed vlan 1,30
    interface Ethernet1/19
      switchport mode trunk
      switchport access vlan 10
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/20
      switchport mode trunk
      switchport access vlan 52
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/21
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/22
    interface Ethernet1/23
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/24
      switchport mode trunk
      switchport access vlan 52
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/25
      switchport mode trunk
      switchport trunk allowed vlan 1,8,30,52
    interface Ethernet1/26
      switchport mode trunk
      switchport access vlan 52
      switchport trunk allowed vlan 1,8,30,52
    interface Ethernet1/27
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/28
      switchport mode trunk
      switchport trunk allowed vlan 1,8,30,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/29
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/30
      description line
      switchport mode trunk
      switchport access vlan 52
      switchport trunk allowed vlan 1,8,30,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/31
      switchport mode trunk
      switchport trunk allowed vlan 1,10,20,52
    interface Ethernet1/32
      switchport mode trunk
      switchport trunk allowed vlan 1,10,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/33
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/34
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/35
      switchport mode trunk
      switchport access vlan 10
      switchport trunk allowed vlan 1,10,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/36
      switchport mode trunk
      switchport trunk allowed vlan 1,30,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/37
      switchport mode trunk
      switchport trunk allowed vlan 1,30,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/38
      switchport mode trunk
      switchport trunk allowed vlan 1,10,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/39
      shutdown
      switchport mode trunk
      switchport trunk allowed vlan 1,10,20,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/40
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet2/1
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet2/2
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet2/3
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet2/4
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface mgmt0
      ip address 10.192.194.111/20
    system default zone default-zone permit
    system default zone distribute full
    line console
    line vty
    boot kickstart bootflash:/n5000-uk9-kickstart.5.0.3.N1.1b.bin
    boot system bootflash:/n5000-uk9.5.0.3.N1.1b.bin
    interface fc2/1
    interface fc2/2
    interface fc2/3
    interface fc2/4
    zone default-zone permit vsan 20
    zone default-zone permit vsan 52
    zoneset distribute full vsan 1
    zoneset distribute full vsan 20
    zoneset distribute full vsan 52
    !Full Zone Database Section for vsan 1
    zone name bg-qa vsan 1
        member pwwn 10:00:00:00:c9:5b:ab:ca
        member pwwn 21:00:00:0c:50:c3:70:23
        member pwwn 21:00:00:0c:50:c3:70:22
        member pwwn 21:00:00:0c:50:c3:70:16
        member pwwn 21:00:00:0c:50:c3:70:1e
        member pwwn 22:00:00:0c:50:c3:70:26
        member pwwn 22:00:00:18:62:06:76:8a
        member pwwn 22:00:00:11:c6:17:68:c3
        member pwwn 22:00:00:0c:50:c3:70:1d
        member pwwn 22:00:00:0c:50:c3:6f:c2
        member pwwn 22:00:00:11:c6:17:68:dc
        member pwwn 21:00:00:0c:50:c3:6a:d0
        member pwwn 21:00:00:0c:50:79:92:90
        member pwwn 21:00:00:11:c6:17:69:a0
        member pwwn 21:00:00:0c:50:79:93:af
        member pwwn 22:00:00:0c:50:48:10:80
        member pwwn 22:00:00:11:c6:18:46:c6
        member pwwn 22:00:00:0c:50:32:2e:0f
        member pwwn 22:00:00:0c:50:48:10:74
        member pwwn 22:00:00:11:c6:18:46:f2
        member pwwn 21:00:00:00:87:13:cb:d1
        member pwwn 21:00:00:0c:50:79:91:0f
        member pwwn 10:00:00:00:c9:3c:8e:49
        member pwwn 10:00:00:00:c9:5b:ab:c2
        member pwwn 10:00:00:00:c9:5b:af:f3
    zone name sf_RAM vsan 1
        member pwwn 10:00:00:00:c9:5b:af:c9
        member pwwn 21:00:00:0c:50:b4:8e:20
    zone name anand vsan 1
        member pwwn 10:00:00:00:c9:65:69:31
        member pwwn 22:00:00:18:62:06:7f:f6
    zone name syedzone vsan 1
        member fwwn 20:11:00:0d:ec:56:7b:40
        member pwwn 50:06:01:60:44:60:23:4f
    zone name bg_qa vsan 1
    zoneset name TOM vsan 1
        member bg-qa
    zoneset name bg_dvt vsan 1
        member sf_RAM
    zoneset name lancer vsan 1
        member anand
    zoneset name bg-qa vsan 1
    zoneset name syed vsan 1
        member syedzone
    zoneset activate name lancer vsan 1
    !Full Zone Database Section for vsan 20
    zone name amrita_zone1 vsan 20
        member pwwn 10:00:00:00:c9:5b:a3:83
        member pwwn 22:00:00:04:cf:89:19:67
        member pwwn 22:00:00:0c:50:48:10:80
        member pwwn 22:00:00:11:c6:18:46:f2
        member pwwn 22:00:00:0c:50:79:93:ae
    zone name amr_zset vsan 20
    zoneset name amr_zset vsan 20
        member amrita_zone1
    zoneset activate name amr_zset vsan 20
    !Full Zone Database Section for vsan 52
    zone name vinod vsan 52
        member pwwn 50:06:01:69:44:60:23:4f
        member pwwn ff:f3:00:00:c9:12:34:78
        member pwwn 10:00:00:00:c9:12:34:5b
        member pwwn 10:00:00:00:c9:12:34:57
    zone name neha vsan 52
    zone name siv1 vsan 52
        member pwwn 10:00:00:00:c9:ad:ac:43
        member pwwn 50:06:01:61:44:60:23:4f
        member pwwn 10:00:00:00:c9:ad:ac:47
    zone name neha1 vsan 52
        member pwwn 10:00:00:00:c9:5b:ab:ad
        member pwwn 50:06:01:60:44:60:23:4f
    zone name neha2 vsan 52
        member pwwn 50:06:01:60:44:60:23:4f
        member pwwn 10:00:00:00:c9:5b:ab:a9
    zone name neha3 vsan 52
        member pwwn 10:00:00:00:c9:9d:1f:bf
        member pwwn 50:06:01:60:44:60:23:4f
    zone name neha4 vsan 52
        member pwwn 50:06:01:60:44:60:23:4f
        member pwwn 10:00:00:00:c9:9d:1f:c1
    zone name chetan vsan 52
        member pwwn 10:00:00:00:c9:f2:73:d3
        member pwwn 50:06:01:60:44:60:23:4f
        member pwwn 10:00:00:00:c9:ad:ac:47
    zone name siv2 vsan 52
        member pwwn 10:00:00:00:c9:d1:0a:6d
        member pwwn ff:f2:00:00:c9:d1:0a:8c
        member pwwn 22:00:00:0c:50:79:93:af
        member pwwn 22:00:00:0c:50:79:92:90
        member pwwn 22:00:00:0c:50:79:91:0f
        member pwwn 20:01:00:11:0d:77:9d:00
    zone name sroy vsan 52
        member pwwn 10:00:00:00:c9:b1:ea:7f
        member pwwn 50:06:01:60:44:60:23:4f
        member pwwn 10:00:00:00:c9:5b:ab:99
        member pwwn 10:00:00:00:c9:bb:cb:8f
        member pwwn 10:00:00:00:c9:5b:ab:c4
        member pwwn 10:00:00:00:c9:d1:16:25
        member pwwn 50:06:01:61:44:60:23:4f
        member pwwn 10:00:00:00:c9:a5:ac:f3
    zone name manju vsan 52
        member pwwn 10:00:00:00:c9:bb:c7:8f
        member pwwn 50:06:01:61:44:60:23:4f
    zone name ram vsan 52
        member pwwn 50:06:01:60:44:60:23:4f
        member pwwn 10:00:00:00:c9:a0:ce:2d
        member pwwn 10:00:00:00:c9:bb:17:b7
        member pwwn 10:00:00:00:c9:5b:a5:27
        member pwwn 10:00:00:00:c9:91:f7:f1
        member pwwn 10:00:00:00:c9:b1:e5:5f
    zone name jana vsan 52
        member pwwn 10:00:00:00:c9:91:f7:f1
        member pwwn 50:06:01:60:44:60:23:4f
    zone name priya vsan 52
        member pwwn 10:00:00:00:c9:e3:06:89
        member pwwn 50:06:01:60:44:60:23:4f
    zoneset name IBMraptor vsan 52
        member vinod
        member siv1
        member neha1
        member neha2
        member neha3
        member neha4
        member chetan
        member siv2
        member sroy
        member manju
        member ram
        member priya
    zoneset name ananda vsan 52
    zoneset name vinod vsan 52
    zoneset activate name IBMraptor vsan 52
    no system default switchport shutdown san
    Cisco-5020# sh system internal dcbx info interface ethernet 1/38
    Interface info for if_index: 0x1a025000(Eth1/38)
    tx_enabled: TRUE
    rx_enabled: TRUE
    dcbx_enabled: TRUE
    DCX Protocol: CIN
    Port MAC address:  00:0d:ec:b2:15:6d
    DCX Control FSM Variables: seq_no: 0x1, ack_no: 0x0,my_ack_no: 0x0, peer_seq_no:
    0x0 oper_version: 0x0,  max_version: 0x0 fast_retries 0x0
    Lock Status: UNLOCKED
    PORT STATE: UP
    LLDP Neighbors
    No DCX tlvs from the remote peer
    6 Features on this intf for Protocol CIN(0)
    3 Features on this intf for Protocol CEE(1)
    6 Features on this intf for Protocol CIN(0)
    Feature type LLS (6)sub_type FCoE Logical Link Status (0)
    feature type 6(LLS)sub_type 0
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 0
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x1d9
    Desired config cfg length: 1 data bytes:00
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Feature type PFC (3)
    feature type 3(PFC)sub_type 0
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
    Desired config cfg length: 1 data bytes:08
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Feature type App(Fcoe) (5)sub_type FCoE (0)
    feature type 5(App(Fcoe))sub_type 0
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
    Desired config cfg length: 1 data bytes:08
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Feature type PriMtu (8)
    feature type 8(PriMtu)sub_type 0
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
    Desired config cfg length: 16 data bytes:24    00    24    00    24    00    08    6e    24    00    24    00    24    00    24    00
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Feature type PriGrp (2)
    feature type 2(PriGrp)sub_type 0
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
    Desired config cfg length: 24 data bytes:32    32    00    00    00    00    00    00    00    0f    00    0f    00    0e    20    64    00    0e    00    0e
       00    0e    00    0e
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Feature type LLS (6)sub_type LAN Logical Link Status (1)
    feature type 6(LLS)sub_type 1
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0xaf
    Desired config cfg length: 1 data bytes:80
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Traffic Counters
    DCBX pkt stats:
        Total frames out: 20296
        Total Entries aged: 27
        Total frames in: 0
        DCBX frames in: 0
        Total frames received in error: 0
        Total frames discarded: 0
        Total TLVs unrecognized: 0
    Cisco-5020#
    Cisco-5020#
    Cisco-5020#
    I am new to this PFC, and first time trying to configure so you can see nothing being configured.

  • Nexus 5000 - Odd Ethernet interface behavior (link down inactive)

    Hi Guys,
    This would sound really trivial but it is very odd behavior.
    - We have a server connected to a 2, Nexus 5000s (for resiliancy)
    - When there is no config on the ethernet interfaces whatsoever, the ethernet interface is UP / UP, there is minimal amount of traffic on the link etc. E.g.
    Ethernet1/16 is up
      Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
      Description: shipley-p1.its RK14/A13
      MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is access
      full-duplex, 10 Gb/s, media type is 1/10g
      Beacon is turned off
      Input flow-control is off, output flow-control is off
      Rate mode is dedicated
      Switchport monitor is off
      Last link flapped 00:00:07
      Last clearing of "show interface" counters 05:42:32
      30 seconds input rate 0 bits/sec, 0 packets/sec
      30 seconds output rate 96 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 0 bps, 0 pps; output rate 8 bps, 0 pps
      RX
        0 unicast packets  0 multicast packets  0 broadcast packets
        0 input packets  0 bytes
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        0 unicast packets  163 multicast packets  0 broadcast packets
        163 output packets  15883 bytes
        0 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble
        0 Tx pause
      1 interface resets
    - As soon as I configure the link to be an access port, the link goes down, flagging "inactivity" E.g.
    sh int e1/16
    Ethernet1/16 is down (inactive)
      Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
      Description: shipley-p1.its RK14/A13
      MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is access
      auto-duplex, 10 Gb/s, media type is 1/10g
      Beacon is turned off
      Input flow-control is off, output flow-control is off
      Rate mode is dedicated
      Switchport monitor is off
      Last link flapped 05:38:03
      Last clearing of "show interface" counters 05:41:33
      30 seconds input rate 0 bits/sec, 0 packets/sec
      30 seconds output rate 0 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
      RX
        0 unicast packets  0 multicast packets  0 broadcast packets
        0 input packets  0 bytes
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        0 unicast packets  146 multicast packets  0 broadcast packets
        146 output packets  13083 bytes
        0 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble
        0 Tx pause
      0 interface resets
    - This behavior is seen on both 5Ks
    - I've tried using a different set of ports, changed SFPs, and fibre cabling to no avail
    - I can't seem to understand this behavior?!  In that, why would configuring the port cause the link to go down?
    - If anyone has experience this before, or could shed some light on this behavior, it would be appreciated.
    sh ver
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (c) 2002-2010, 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 1.2.0
      loader:    version N/A
      kickstart: version 4.2(1)N1(1)
      system:    version 4.2(1)N1(1)
      power-seq: version v1.2
      BIOS compile time:       06/19/08
      kickstart image file is: bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin
      kickstart compile time:  4/29/2010 19:00:00 [04/30/2010 02:38:04]
      system image file is:    bootflash:/n5000-uk9.4.2.1.N1.1.bin
      system compile time:     4/29/2010 19:00:00 [04/30/2010 03:51:47]
    thanks
    Sheldon

    I had identical issue
    Two interfaces on two different FEXes were INACTIVE. I have two Nexus 5596 in vPC and A/A FEXes.
    I also use config-sync feature.
    Very same configuration was applied to other ports on other FEXes and they were working with no problems.
    interface Ethernet119/1/1
      inherit port-profile PP-Exchange2003
    I checked VLAN status associated with this profile and it was active (of course it was, other ports were ok).
    I solved it by removing port profile from this port and re-applied it... voila, port changed state to up!
    Very very strange.

  • Ask the Expert: Cisco Nexus 2000, 5000, and 6000 Series Switches

    with Cisco Expert Vinayak Sudame
    Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions how to configure and troubleshoot the Cisco Nexus 2000, 5000 and 6000 Series Switches with Cisco subject matter expert Vinayak Sudame. You can ask any question on configuration, troubleshooting, features, design and Fiber Channel over Ethernet (FCoE).
    Vinayak Sudame is a Technical Lead in Data Center Switching Support Team within Cisco's Technical Services in RTP, North Carolina. His current responsibilities include but are not limited to Troubleshooting Technical support problems and Escalations in the areas of Nexus 5000, Nexus 2000, FCoE. Vinayak is also involved in developing technical content for Cisco Internal as well as external. eg, Nexus 5000 Troubleshooting Guide (CCO), Nexus 5000 portal (partners), etc. This involves cross team collaboration and working with multiple different teams within Cisco. Vinayak has also contributed to training account teams and partners in CAE (Customer Assurance Engineering) bootcamp dealing with Nexus 5000 technologies. In the past, Vinayak's responsibilities included supporting MDS platform (Fiber Channel Technologies) and work with EMC support on Escalated MDS cases. Vinayak was the Subject Matter Expert for Santap Technologies before moving to Nexus 5000 support. Vinayak holds a Masters in Electrical Engineering with Specialization in Networking from Wichita State University, Kansas. He also holds Cisco Certification CCIE (#20672) in Routing and Switching.
    Remember to use the rating system to let Vinayak know if you have received an adequate response.
    Vinayak might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the  Data Center sub-community, Other Data Center Topics discussion forum shortly after the event.
    This event last through Friday July 12, 2013. Visit the community often to view responses to youe questions of other community members.

    Hi Vinayak,
    Output of "show cfs internal ethernet-peer database"
    Switch 1
    ETH Fabric
    Switch WWN              logical-if_index
    20:00:54:7f:ee:b7:c2:80 [Local]
    20:00:54:7f:ee:b6:3f:80 16000005
    Total number of entries = 2
    Switch 2
    ETH Fabric
    Switch WWN              logical-if_index
    20:00:54:7f:ee:b6:3f:80 [Local]
    20:00:54:7f:ee:b7:c2:80 16000005
    Total number of entries = 2
    Output of "show system internal csm info trace"
    Switch 1 in which "show cfs peers" show proper output
    Mon Jul  1 05:46:19.145339  (CSM_T) csm_sp_buf_cmd_tbl_expand_range(8604): No range command in buf_cmd_tbl.
    Mon Jul  1 05:46:19.145280  (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
    Mon Jul  1 05:46:19.145188  (CSM_T) csm_sp_handle_local_verify_commit(4291):
    Mon Jul  1 05:46:19.145131  csm_continue_verify_ac[597]: peer is not reachable over CFS so continuing with local verify/commit
    Mon Jul  1 05:46:19.145071  csm_tl_lock(766): Peer information not found for IP address: '172.16.1.54'
    Mon Jul  1 05:46:19.145011  csm_tl_lock(737):
    Mon Jul  1 05:46:19.144955  (CSM_EV) csm_sp_build_tl_lock_req_n_send(941): sending lock-request for CONF_SYNC_TL_SESSION_TYPE_VERIFY subtype 0 to Peer ip = (172.16.1.54)
    Mon Jul  1 05:46:19.143819  (CSM_T) csm_copy_image_and_internal_versions(788): sw_img_ver: 5.2(1)N1(2a), int_rev: 1
    Mon Jul  1 05:46:19.143761  (CSM_T) csm_sp_get_peer_sync_rev(329): found the peer with address=172.16.1.54 and sync_rev=78
    Mon Jul  1 05:46:19.143699  (CSM_T) csm_sp_get_peer_sync_rev(315):
    Mon Jul  1 05:46:19.143641  (CSM_EV) csm_sp_build_tl_lock_req_n_send(838): Entered fn
    Mon Jul  1 05:46:19.143582  (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
    Switch 2 in which "show cfs peers" does not show proper output
    Mon Jul  1 06:13:11.885354  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 77 seq 482
    Mon Jul  1 06:13:11.884992  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 357 seq 369
    Mon Jul  1 06:13:11.884932  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 357 seq 368
    Mon Jul  1 06:13:11.884872  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 357 seq 367
    Mon Jul  1 06:13:11.884811  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 357 seq 366
    Mon Jul  1 06:13:11.884750  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 352 seq 365
    Mon Jul  1 06:13:11.884690  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 352 seq 364
    Mon Jul  1 06:13:11.884630  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 352 seq 363
    Mon Jul  1 06:13:11.884568  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 352 seq 362
    Mon Jul  1 06:13:11.884207  (CSM_EV) csm_sp_acfg_gen_handler(3011):  Preparing config into /tmp/csm_sp_acfg_1733916569.txt
    Mon Jul  1 06:13:11.878695  csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
    Mon Jul  1 06:13:11.878638  (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
    Mon Jul  1 06:12:29.527840  (CSM_T) csm_pss_del_seq_tbl(1989): Freeing seq tbl data
    Mon Jul  1 06:12:29.513255  (CSM_T) csm_sp_acfg_gen_handler(3106): Done acfg file write
    Mon Jul  1 06:12:29.513179  (CSM_EV) csm_sp_acfg_gen_handler(3011):  Preparing config into /tmp/csm_sp_acfg_1733911262.txt
    Mon Jul  1 06:12:29.508859  csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
    Mon Jul  1 06:12:29.508803  (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
    Mon Jul  1 05:53:17.651236  Collecting peer info
    Mon Jul  1 05:53:17.651181  Failed to get the argumentvalue for 'ip-address'
    Mon Jul  1 05:40:59.262736  DB Unlocked Successfully
    Mon Jul  1 05:40:59.262654  Unlocking DB, Lock Owner Details:Client:1 ID:1
    Mon Jul  1 05:40:59.262570  (CSM_T) csm_sp_del_buf_cmd(1713): Deleting comand with Id = 1
    Mon Jul  1 05:40:59.262513  DB Lock Successful by Client:1 ID:1
    Mon Jul  1 05:40:59.262435  Recieved lock request by Client:1 ID:1
    Mon Jul  1 05:40:41.741224  ssnmgr_ssn_handle_create_get: Session FSM already present, ID:1
    Mon Jul  1 05:40:41.741167  ssnmgr_handle_mgmt_request: Create/Get request received for session[process_n5kprof]
    show cfs lock gives no output.
    Just to further clarify, we have 4 5548UP switches in the same management vlan. 2 switches are in one location lets say location A and they are CFS peers and are working fine.
    These two switches which are having problem are in location B. All the switches are in the same vlan. Essentially the all CFS multicast messages will be seen by all 5548 switches as they are in the same vlan. I am assuming that this might not create any problems as we specify the peers in the respective configurations. Or do we have to change the CFSoIPv4 multicast addresses in location B or may be configure a different region.
    Regards.

  • Command for view i/o rate cisco nexus

    Hi
    I need a command for view input and output rate on all interface for device nexus 7000 and nexus 5000
    The command sh interface show more information, I only need view rx and tx
    on switch 3750, 2960 i use sh interface summary and in nexus do not exist
    Regards

    Hi,
    Show interface xxx | inc rate will give you in /out rate.
    For example -sh int e1/1 | i rate
    For show interface summary you can use grep feature on nexus multiple Include and exclude are possible.
    show interface E1/1 | inc rate|MTU | exclude pps
    Just to see interface counters -
    show interface counters detailed all
    Hope this helps.
    Thanks
    Ajay

  • HP Servers NIC Teaming with Cisco Nexus 2000/5000

    I have number of HP switches that will be connected to Cisco Nexus 2000/5000 switches.
    In  HP Servers, there are multiple options for NIC teaming.  I like to  connect each port in a NIC card to two different Nexus 2000 switches  extension to Nexus 5000 switches.  Nexus 5000 switches will be  configured as VPC for clustering.
    Wanted to know what whould be the best NIC teaming option from the followng HP Server's NIC Teaming options:
    Automatic
    802.3ad Dynamic with Fault Tolerence
    Switch-assisted load balancing with Fault Tolerance (SLB)
    Transmit load balancing with Fault Tolerance (TLB)
    Transmit Load Balancing with Fault tolerance and preference order
    Network Fault Tolerance Only (NFT)
    Network Fault Tolerance with Preference Order

    Nexus switches only support LACP (802.3ad) or ON mode.  So, to match your server config with your switch, the first option is the best one to use.  I think, SLB is a Microsoft propriety protocol.
    HTH

  • Aborting the show file command ouput in cisco nexus

    Hi all ,
    In order to verify the md5 value in cisco nexus image  we need to use show file bootflash:image md5sum command. But instead of that we given show file bootflash:image . And it is continiously showing the entire file content and full junk values coming in console. I have given ctrl+shift+6 to abort the ouput. But it is not stopping and now i am not able to do anything in console. Any suggestion to abort that.
    Thanks,
    Vijay

    Hi All,
    I just cleared the console session from tty lines using the below command,
    clear line linename.
    After this , console responded and we are able to access it.
    Thanks,
    Vijay.

  • Nexus 5000 command/log accounting

    Good afternoon gentlemen
    I need to configure the same as shown below in Nexus 5000 switches. The requirement is logging all user access login (whether failed or succeeded) and also logging all commands that users issue.
    #IOS commands
    no logging console
    logging buffered 307200 informational
    service timestamps log datetime localtime show-timezone
    logging trap debugging
    login on-failure log
    login on-success log
    archive
       log config
          logging enable
          logging size 500
          hidekeys
          notify syslog contenttype plaintext
    By now, I only found the command "show accounting log". But no way to export to a syslog server I think.
    If you guys have an idea please answear
    Regards
    Christian

    Good afternoon gentlemen
    I need to configure the same as shown below in Nexus 5000 switches. The requirement is logging all user access login (whether failed or succeeded) and also logging all commands that users issue.
    #IOS commands
    no logging console
    logging buffered 307200 informational
    service timestamps log datetime localtime show-timezone
    logging trap debugging
    login on-failure log
    login on-success log
    archive
       log config
          logging enable
          logging size 500
          hidekeys
          notify syslog contenttype plaintext
    By now, I only found the command "show accounting log". But no way to export to a syslog server I think.
    If you guys have an idea please answear
    Regards
    Christian

  • Logging of commands on syslog server (Cisco Nexus 7010)

    Please help.
    How to set up logging of commands on syslog server ? (cisco nexus 7010)

    Hi Igor
    Nexus has internal accounting log: sh accouting log
    But it can be sent only to the accounting server, not to a syslog server.
    If you want - you man manually export it to some log.
    HTH,
    Alex

  • UCS C-Series VIC-1225 to Nexus 5000 setup

    Hello,
    I have two nexus 5000 setup with a vpc peer link. I also have an cisco c240 m3 server with a vic-1225 card that will be running esx 5.1. I also have some 4 2248 fabric extenders. I have been searching for some best practice information on how to best setup this equipment. The nexus equipment is already running, so its more about connecting the c240 and the vic-1225 to the nexus switches. I guess this is better to do rather than to connect to the fabric extenders in order to minmize hops?
    All documention I have found involves setup/configuration etc with fabric interconnects which I dont have, and have been told that I do not need. Does anyone have any info on this? and can point me in the right direction to setup this correctly?
    More specifically, how should I setup the vic-1225 card to the nexus? just create a regular vpc/port-channel to the nexuses? use lacp and set it to active?
    Do I need to make any configuration changes on the vic card via the cimc on the c240 server to make this work?

    Hello again, Im stuck
    This is what I have done. I have created the vPC between my esx host and my two nexus 5000 switches, but it doesnt seem to come up:
    S02# sh port-channel summary
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
            M - Not in use. Min-links not met
    Group Port-       Type     Protocol  Member Ports
          Channel
    4     Po4(SD)     Eth      LACP      Eth1/9(D)
    vPC info:
    S02# sh vpc 4
    vPC status
    id     Port        Status Consistency Reason                     Active vlans
    4      Po4         down*  success     success                    -
    vPC config:
    interface port-channel4
      switchport mode trunk
      switchport trunk allowed vlan 20,27,30,50,100,500-501
      spanning-tree port type edge trunk
      vpc 4
    interface Ethernet1/9
      switchport mode trunk
      switchport trunk allowed vlan 20,27,30,50,100,500-501
      spanning-tree port type edge trunk
      channel-group 4 mode active
    Im unsure what I must configure on the cisco 240M3(esx host) side to make this work. I only have the two default interfaces(eth0 and eth1) on the vic-1225 installed in the esx host, and both have the vlan mode is set to TRUNK.
    Any ideas on what I am missing?
    Message was edited by: HDA

Maybe you are looking for