membership of VPC - nexus 5000

Hello guys,.

I have a small conceptual question on vPC. Is it possible to add more then 2 devices in one area of the vPC?

I want to add 4 nexus 5000 devices to a vPC-domain, make a vPC on all 4 devices.

I found nothing on that in the internet, this is why I ask.

Thanks in advance!

2 only allowed in an area of the vPC.

http://www.Cisco.com/c/en/us/products/collateral/switches/nexus-5000-SER...

Tags: Cisco Network

Similar Questions

  • Configure ports on Nexus 5000/2000 for the grouping of network server adapters

    Hello

    I have two Nexus 5000 and Nexus two, 2000.  The 5000 s are peers of vpc.  I would like to connect my server with cluster NIC in a port on each 2000 and all have both be active.  Is this possible?  What are the steps?  I thought it should be this:

    CPR_NEXUS_5K01 (config) # int eth100/1/32

    CPR_NEXUS_5K01(Config-if) # channel - group 32

    CPR_NEXUS_5K01 (config) # int eth101/1/32

    CPR_NEXUS_5K01(Config-if) # channel - group 32

    on the Nexus two.

    Thank you, Jerry

  • Frames in Nexus 5000

    Hello:

    We have 2 Nexus 5000 Switch with n5000 - uk9.5.0.3.N2.2.bin system image file.

    2 Nexus divided in 2 centres and directly connected.

    In each of the switches, there is an Oracle server. These Oracle servers are grouped and connected by a link of heartbeat.

    The Oracle administrator ask us to set up frames in the heart rate.

    How can I do this?

    Thank you!!!

    All you have to do is put this configuration on all your 5ks nexus:

    Switch (config) #type of policy-map network-qos jumbo

    Switch(config-pmap-NQ) #network-qos default class type class

    Switch(config-pmap-c-NQ) #mtu 9216

    Switch(config-pmap-c-NQ) #exit

    Switch(config-pmap-NQ) #exit

    Switch (config) #qos system

    Switch(config-sys-QoS) #jumbo qos network type of service-strategy

    This will allow wide global capacity jumbo frame.

    To check if it works, do a "show int eth x / y", if you see Configuring jumbo rising and packages are not walked on, his work.

    Also note that the mtu will not change on the interface itself, it's a global command, not an order "by interface. But it's ok, even if mtu 1500, says it can still accept frames if you have applied global config.

    Example:

    Ethernet1/1 is on the rise

    ...

    RX

    0 1221713 packages 2644 multicasts packets broadcast unicast packets

    packages of entry 1224357 91236171 bytes

    ---> 458 jumbo packets 0 packets of repression storm

    short frame overflow of data entry error 0 Giants 0 0 0 0 against the imbedding

    0 0 surveillance so to the bottom of the fall

    0 entry with dribble 0 rejection of entry

    Rx pause 0

  • Using SNMP to monitor Cisco Nexus 5000

    Hello

    I would like to know what specific OID to use to monitor the following using SNMP on a Nexus 5000:

    -L' total CPU usage

    -Power supply status

    -Status of Fan chassis

    The Nexus is quite different from other devices Cisco - any help will be appreciated!

    CPU: oid to use is: 1.3.6.1.4.1.9.9.305.1.1.1 (cseSysCPUUtilization) is a part of the MIB:

    CISCO-SYSTEM-EXT-MIB

    It displays the value as a percentage of the processor.

    ME-TestBed-A (nxos) # display system resources

    Load average: 1 minute: 0.26 5 minutes: 0.41 15 minutes: 0.43

    Process: 393 1 total, running

    CPU States: inactive user of 1.0%, 4.0% of the kernel, 95.0%

    Memory usage: total 3634820K, 1728600K used, 1906220K free

    81256K buffers, 1037176K cache

    DHCP-171-69-89-49: ~ lulu-mbp$ snmpwalk - public - Cabarrus 2 c 172.25.180.5

    1.3.6.1.4.1.9.9.305.1.1.1

    SNMPv2-SMI::enterprises.9.9.305.1.1.1.0 = Gauge32 : 5

    As you can see, show sys resources indicates 95% idle, valuation is 5% cpu and the snmp poster value.

    -------------

    Power and Fans, it is fairly limited

    The cisco mib envmon is not yet supported on the 5K, looks like.

    This leaves us with the FRU mib: 1.3.6.1.4.1.9.9.117 ftp://ftp.cisco.com/pub/mibs/oid/CISCO-ENTITY-FRU-CONTROL-MIB.oid

    The index values will come from oid: entPhysicalTable)

    1.3.6.1.2.1.47.1.1.1) is part of the ENTITY-MIB

    DHCP-171-69-89-49: ~ lulu-mbp$ snmpwalk - public - Cabarrus 2 c 172.25.180.5

    1.3.6.1.4.1.9.9.117

    SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.1.470 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.1.1000470 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.2.470 = STRING : « CentiAmps @ 12V »

    SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.2.1000470 = STRING : « CentiAmps @

    12V.

    SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.3.470 = INTEGER : 4538

    SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.3.1000470 = INTEGER : 0

    SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.4.470 = INTEGER : 29

    SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.4.1000470 = INTEGER : 0

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.22 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.23 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.470 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.1000022 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.1000470 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.3000022 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.22 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.23 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.470 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.1000022 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.1000470 = INTEGER : 4

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.3000022 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.22 = ENTIER :-2910

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.23 = INTEGER : -83

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.470 = INTEGER : 29

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.1000022 = INTEGER : 0

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.1000470 = INTEGER : 0

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.3000022 = INTEGER : 0

    SNMPv2-SMI::enterprises.9.9.117.1.1.3.0 = INTEGER : 0

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.1.22 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.1.23 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.1.1000022 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.1.3000022 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.2.22 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.2.23 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.2.1000022 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.2.3000022 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.3.22 = INTEGER : 0

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.3.23 = INTEGER : 0

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.3.1000022 = INTEGER : 0

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.3.3000022 = INTEGER : 0

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.4.22 = Timeticks : 0:00:10.27 (1027)

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.4.23 = Timeticks : 0:01:25.20 (8520)

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.4.1000022 = Timeticks :

    (41634711) 4 days, 19:39:07.11

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.4.3000022 = Timeticks :

    (41634712) 4 days, 19:39:07.12

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.5.22 = Timeticks : (0) 0:00:00.00

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.5.23 = Timeticks : (0) 0:00:00.00

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.5.1000022 = Timeticks : (0)

    0:00:00.00

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.5.3000022 = Timeticks : (0)

    0:00:00.00

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.6.22 = « »

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.6.23 = « »

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.6.1000022 = « »

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.6.3000022 = « »

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.8.22 = Gauge32 : 0

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.8.23 = Gauge32 : 0

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.8.1000022 = Gauge32 : 0

    SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.8.3000022 = Gauge32 : 0

    SNMPv2-SMI::enterprises.9.9.117.1.3.1.0 = ENTIER : 1

    SNMPv2-SMI::enterprises.9.9.117.1.4.1.1.1.534 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.4.1.1.1.535 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.4.1.1.1.536 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.4.1.1.1.537 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.10 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.22 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.23 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.149 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.214 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.215 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.278 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.279 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.342 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.343 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.470 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.534 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.535 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.536 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.537 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4950 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4951 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4952 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4953 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4954 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4955 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4956 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4957 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4958 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4959 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4960 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4961 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4962 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4963 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4964 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4965 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4966 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4967 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4968 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4969 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5206 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5207 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5208 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5209 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5210 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5211 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5212 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5213 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21590 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21591 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21592 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21593 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21594 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21595 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21596 = INTEGER : 2

    SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21602 = INTEGER : 2

    You can read in:

    FTP://FTP.Cisco.com/pub/MIBs/v1/Cisco-entity-FRU-control-MIB-V1SMI.my

    that means values integer by OID.

    Take for example (look at the file

    ( ftp://ftp.cisco.com/pub/mibs/oid/CISCO-ENTITY-FRU-CONTROL-MIB.oid)

    cefcFRUPowerOperStatus: 1.3.6.1.4.1.9.9.117.1.1.2.1.2 for one of the

    index:

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.22 = INTEGER : 2

    We now need to find 22-year-old:

    SNMPv2-SMI::mib-2.47.1.1.1.1.7.22 = STRING : « 20 port 10GE SFP + / superviseur

    in the Module fixed-1"

    That means now the INTEGER 2 from:

    SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.22 = INTEGER : 2

    Lets look at: CISCO-ENTITY-FRU-CONTROL-MIB-V1SMI.my, section

    cefcFRUPowerOperStatus, if you are looking for in this file you will find: we (2),

    That measn this controller is actually turned on and powered.

  • Nexus 5000 native FC disk array and tape library

    Is it possible to have servers to connect by FCoE to nexus 5000 switches as well as native berries FC of attached disk and tape library without requiring additional CF as the MDS 9000 switch? The reason why I ask, is that all the patterns I've seen on consolidated IO to this point show switches connected to the FC ports native on the nexus 5000 MDS. I thought that the Nexus 5000 would be able to replace the MDS attaching devices FCoE and native Fibre Channel devices. You see only such a diagram has me second guessing my initial thought.

    Yes, you can use FCoE and FC of Nexus 5000 to connect to networks. I tested and it works very well without any problems.

    FCoE, you have module FCoE in the bays and the appropriate license.

    RAM

  • groups of IP addresses are supported on Nexus-5000 and models down?

    Looking online, I see the ip address of the object-group is explicitly listed as

    supprted on Nexus 7000 but on other model documents command is confusing.

    For example, for Nexus-5000 references to IP address source/destination to refuse the order group objects exist in the documentation older versions of NX - OS 4.0 and 4.1 (with no explicit object-group command is listed in the same CLI reference) but in v5.x current source/destination shows no Group of IP addresses as available choice.

    Can one with access to the Nexus 5000 or 3000 check if the ip address of the object-group is an order valid on this platform?

    It seems full support (like on IOS), using the IP address groups was established in v6 NX - OS (which only works on platform 7000).

    There was also presented on the lower models?

    Thank you.

    Hi Alexandre

    This feature is not currently supported on N5k/N3k

    If you have specific requirements for this feature, please join your team has to describe your network design. And they will be able to help you.

    HTH,

    Alex

  • Nexus 5000 operating as a standalone FibreChannel Switch

    Hello world

    Does anyone know if the Nexus 5000 can be used as a standalone FibreChannel Switch? Which means I don't want to run NPV on this and connect it up to a MDS or a different type of switch FibreChannel. I'm looking to create a 'Pod' scenario. Where a few servers and a storage Bay would hang the 5K on a login F_Ports is local FLOGI DB and be able to use zoning and traffic went immediately from the 5K, etc etc? I know that 5 K is not a full blown fibre channel switch such that it has some limitations, but again I think to a "Pod" as scenario.

    If the script above won't work for some reason any using CF can achieve us with FCoE CNAs on servers & storage Bay?

    Finally, FC domain IDS how 5 K can cause?

    Sorry for the questions. I'm new to SAN switching at this stage.

    Thank you all!

    Yes, it works even FC code NX - OS like a switch MDS switch.

    You connect FC HBAS, ports SAN or FCoE CNAs to Nexus.

    However, you need to license storage.

    Nexus 5010 supports up to 8 4 G FC or FC G 6 8 ports with the expansion module

    Nexus 5020 supports up to 16 4 G FC or 12 8 G FC ports with the expansion module

    Nexus 5548UP supports up to ports FC 32 4 / 8G without the expansion module

    Nexus 5548UP supports up to 48 4 FC ports / 8G with the expansion module

    Nexus 5596UP supports up to 48 4 FC ports / 8G without the expansion module

    Nexus 5596UP supports up to 96 4 FC ports / 8G with the expansion module

  • Connectivity HP C7000 and Nexus 5000

    We spend our ESX servers in a rack mount environment at C7000 enclosures with blades. Can someone talk about compatibility box blade HP and Nexus 5000? The little that I find seems to suggest that this match may not be 100% ready for primetime.

    I have a HP Virtual Connect modules or exactly what FCoE lokks like with HP blades. Does anyone have more information on this specific vegetables or aware of this configuration, used successfully?

    There is full compatibility between the HP 7000 and the Cisco Nexus 5000.

    What you need to make sure if it is that you are up-to-date with all HP firmware and drivers Nic ESX.

    Take a look on my blog that goes into this in detail:

    http://www.wooditwork.com/2010/08/09/Flex-10-ESX-pre-requisites/

    http://www.wooditwork.com/2011/02/17/Flex-10-ESX-design-with-simplicity-and-scalability-part-1/

    http://www.wooditwork.com/2011/02/17/Flex-10-ESX-design-with-simplicity-and-scalability-part-2/

    http://www.wooditwork.com/2011/02/18/scripting-Flex-10-ESX-design-with-PowerCLI/

    http://www.wooditwork.com/2010/10/19/HP-Virtual-connect-for-the-Cisco-network-administrator/

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

    Hi guys,.

    It would sound really trivial, but it's very strange behavior.

    -We have a server connected to a 2, 5000 s Nexus (for resiliancy)

    -When there is that no config on the ethernet interfaces don't either, the ethernet interface is up / upward, there is a minimum amount of traffic on the link, etc. For example

    Ethernet1/16 is in place
    Material: 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
    Lighthouse is off
    Input stream control is turned off, output flow control is disabled
    Flow mode is dedicated
    Switchport monitor is off
    Last link flapped 00:00:07
    Last clearing of "show interface" counters 05:42:32
    entry 30 seconds 0 bps, 0 packets/s rate
    exit rate of 30 seconds 96 bps, 0 packets/s
    Load-time #2: 5 minutes (300 seconds)
    heat flow 0 bit/s, 0 pps; output rate 8 bits/s, 0 pps
    RX
    0 packets unicast packets multicasts 0 0 broadcast packets
    entry packets 0 0 bytes
    0 packets of removal of storm Jumbo packets 0
    Giants of Runts 0 0 0 CRC 0 no buffer
    short entry error 0 0 0 overflow under-run 0 0 ignored
    0 0 bad etype watchdog fall 0 bad proto place 0 if drop
    0 entry with dribble 0 rejection of entry
    Rx pause 0
    TX
    0 163 0 multicasts packets packets broadcast unicast packets
    packages of exit 163 15883 bytes
    0 jumbo packets
    collision of errors 0 0 released 0 postponed end collision 0
    0 lost 0 carrier no carrier 0 chatter
    Tx break 0
    1 interface resets

    -As soon as I set up the link to be an access port, the link goes down, "inactivity" example of markup

    SH int e1/16
    Ethernet1/16 is down (inactive)
    Material: 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
    Lighthouse is off
    Input stream control is turned off, output flow control is disabled
    Flow mode is dedicated
    Switchport monitor is off
    Last link flapped 05:38:03
    Last clearing of "show interface" counters 05:41:33
    entry 30 seconds 0 bps, 0 packets/s rate
    exit rate of 30 seconds 0 bps, 0 packets/s
    Load-time #2: 5 minutes (300 seconds)
    heat flow 0 bit/s, 0 pps; output rate 0 bps, 0 pps
    RX
    0 packets unicast packets multicasts 0 0 broadcast packets
    entry packets 0 0 bytes
    0 packets of removal of storm Jumbo packets 0
    Giants of Runts 0 0 0 CRC 0 no buffer
    short entry error 0 0 0 overflow under-run 0 0 ignored
    0 0 bad etype watchdog fall 0 bad proto place 0 if drop
    0 entry with dribble 0 rejection of entry
    Rx pause 0
    TX
    0 packets 146 0 multicasts packets broadcast unicast packets
    packets to exit 146 13083 bytes
    0 jumbo packets
    collision of errors 0 0 released 0 postponed end collision 0
    0 lost 0 carrier no carrier 0 chatter
    Tx break 0
    0 resets interface

    -This behavior is visible on the two 5Ks

    -J' have tried to use a different set of ports, SFP and fiber cabling without result changed

    -I can't understand this behavior?  In this, why to configure the port would cause the link to go down?

    -If anyone has experience this before, or could shed some light on this problem, it would be appreciated.

    SH ver
    Operating system (NX - OS) Cisco Nexus software
    TAC support: http://www.cisco.com/tac
    Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
    The copyright in certain works contained in this document are the property of
    other third parties and are used and distributed under license.
    Portions of this software are covered by 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
    Charger: version N/A
    Kickstart: version 4.2 (1) N1 (1)
    system: version 4.2 (1) N1 (1)
    power-seq: version v1.2
    Compile of the BIOS time: 19/06/08
    kickstart image file is: bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin
    Kickstart compile time: 2010-04-29 19:00 [2010-04-30 02:38:04]
    filesystem image is: bootflash:/n5000-uk9.4.2.1.N1.1.bin
    compile time: 2010-04-29 19:00 [30/04/2010 03:51:47]

    Thank you

    Sheldon

    Hello

    If you have configured ports such as access to VLANs ports, who are either:

    (a) not configured on the switch / present in the database for vlan.

    or

    (b) present in the database, but it is in a suspended state.

    You will encounter this problem.  Please can you check the status of the VLAN?

    Hope this helps

    Martin

  • Fails to PI 2.0 Configuration Archive Cisco Nexus 5000

    Hello

    We have recently improved Cisco IP from 1.3 to 2.0 and I thought that this problem would be resolved, but he did not. I added two switches 5548 Nexus I can monitor and configure via Cisco first but I am not able to read the boot och running configuration to the Configuration Archive. When I start work, I get the following error:

    "device fig: java.net.SocketTimeoutException: Read timed out".

    Current NXOS: 5.2 (1) N1(2a)

    Before troubleshooting I would just answer if it should be possible to archive the Nexus to Cisco configs first Infrastructure?

    See you soon! Mattias Andersson

    Yes, I do it with success on a couple of first 2.0 facilities. My case later included NX - OS - 5548UP and 5596UP 5.2 (1) N1 (4) running and 6.0 (2) N2(1b).

  • Nexus 5000 ports do not convert in Ethernet

    Greetings. I'm trying to convert Ethernet ports 17-24 of FibreChannel. However, when I run the following commands, this is what happens:

     Aero5K(config)# slot 1 Aero5K(config-slot)# port 17-24 type ethernet ERROR: Invalid Port Range specified

    Here's the relevant current config. I hate usually pasting configs, but in this case, I want to give the answering machine the best chance to tell me my problem.

     version 7.0(5)N1(1) feature fcoe hostname Aero5K feature telnet feature interface-vlan feature lacp feature lldp slot 1 port 17-32 type fc slot 2 vrf context management vsan database vsan 11 name "fabric_aero5k" fcdomain fcid database vsan 11 wwn 50:06:01:60:36:e0:11:66 fcid 0x008400ef dynamic vsan 11 wwn 50:06:01:68:36:e0:11:66 fcid 0x008401ef dynamic interface Vlan1 interface Vlan100 no shutdown ip address 10.0.100.9/24 vsan database vsan 11 interface fc1/17 vsan 11 interface fc1/18 vsan 11 interface fc1/19 vsan 11 interface fc1/20 vsan 11 interface fc1/21 vsan 11 interface fc1/22 vsan 11 interface fc1/23 vsan 11 interface fc1/24 vsan 11 interface fc1/25 vsan 11 interface fc1/26 vsan 11 interface fc1/27 vsan 11 interface fc1/28 vsan 11 interface fc1/29 vsan 11 interface fc1/30 vsan 11 interface fc1/31 vsan 11 interface fc1/32 interface fc1/17 interface fc1/18 interface fc1/19 interface fc1/20 interface fc1/21 interface fc1/22 interface fc1/23 interface fc1/24 interface fc1/25 interface fc1/26 interface fc1/27 interface fc1/28 interface fc1/29 interface fc1/30 interface fc1/31 no shutdown interface fc1/32 no shutdown

    I guess you had ports slot 1 Ethernet 1-16 and 17-32 FC ports!

    Now you want ports 17-24 to become Ethernet as well.

    That's why you need

     port 1-24 type ethernet

  • Double room Nexus 2348UPQ / Max ports for vPC links

    Hi people,

    Cisco Nexus 2348UPQ has 24 to 10 GB uplink interfaces. Supposedly on the distribution layer, we have a pair of Cisco Nexus 5548UP, how many ports we can group about 2348 for vPC for double-homing links.

    Thank you very much!!!

    Hi Chris,

    Using an Extender of fabric with a Cisco Nexus 5000 and 6000 Series Switch Cisco Nexus

    http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus2000/HW/installation/guide/nexus_2000_hig/overview.html#pgfId-1415984

    -If you decide to use the drop cable instead of the 40 G uplinks, please note the following limitation:

    The 2348TQ of Cisco Nexus and Nexus 2348UPQ FEX, if a port channel is used to connect a switch parent with a tissue Expander device, the port channels can have up to 8 ports.

    Nexus 2348 FEX devices have a total of 6 * 40 Gigabit Ethernet uplink ports to the parent switch. If these are used with native port of 40G uplinks on a switch of parent, there is no limitation. 6 ports can be used in a hosted configuration only hosted or double. You can also use 40 Gigabit Ethernet uplink ports on the extensor of N2348 fabric with 10 Gigabit Ethernet ports on the switch to parent when it is used with the appropriate wiring. A maximum of 8 ports can be added to the string of port between the parent switch and the fabric Extender. If it's a double hosted configuration, VPC for the extensor of fabric, only 4 ports per switch are allowed in the channel of the port.

    Cisco Nexus 5600 series NX - OS Layer 2 switching Configuration Guide, version 7.x - configuration of the fabric Extender

    http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus5600/SW/Layer2/7x/b_5600_Layer2_Config_7x/b_6k_Layer2_Config_7x_chapter_01110.html

    -SFP support and cables are listed in the Cisco Nexus 2300 platform fabric Extender card (http://www.cisco.com/c/en/us/products/collateral/switches/nexus-2000-series-fabric-extenders/datasheet-c78-731663.html).

    I'd be suspicious of this bug;

    https://Tools.Cisco.com/bugsearch/bug/CSCuu88175/?reffering_site=dumpcr

    "If it's a double configuration hosted, vpc for fex, that only 4 ports per switch are permitted in the Port-Channel"

    HTH,

    Qiese Sa'di

  • Nexus 5 k with L3

    Hello

    Could you explain the following paragraph, located at the following ADDRESS:

    http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus5000/SW/operations/interfaces/602_n1_1/N5K_Interfaces_Ops_Guide/L3_w_vpc_5500platform.html#wp1014116

    «In some circumstances, you might consider having a distinct link between both vPC switches, to form the layer 3 Protocol Routing peering or transport traffic VLAN no - vPC.» * While this design is compatible with the Cisco Nexus 7000 Series switch, it does not work on the Cisco Nexus 5000 series switch *. With the Cisco Nexus 5000 Series switch, we recommend using a link of vPC for Layer 3 peering peers in order to perform the vPC and non - vPC VLAN. »

    I have deployments of Nexus 5 k with L3 cards which have separate links for L3 and no vpc VLAN instead of having them on the link of peers VPC and they seem to work well. This is a mistake in the documentation or could I have problems?

    Thank you

    Eric Lauriault, CCIE 27521

    Hi Eric,.

    In the URL you have specified http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html

    Take a look at Figure 3-10 and now add another layer 3 linking N5K N5K-1-2.

    1 multicast is sent on N5K - 1

    2. multicast routing on N5K - 1.  A copy is sent to the interface of L3 and another copy is sent to the peer-link in vlan reserved (in the vpc bin - vrf default vlan xxxx).

    3. the packet received on the interface of layer 3 multicasting will still get replicate by the peers-Link.

    Thank you

    -KL

  • Bpdguard and nexus portfast

    HW SW INFO:

    UCS B200MII

    Nexus 5K

    PVS 7.1

    7.1 XD

    http://support.Citrix.com/article/CTX123158

    According to this link, I need to enable portfast and disable bpdguard in Cisco and Nexus

    My friend argument, no need to enable the portfast because pvs and vm win7 all using vnic, which there is no user disconnect nic physical port.

    Is this true?

    If set to false then can I globally enable portfast and disable bpdguard on base sw and nexus

    Thank you

    Sorry, I wasn't clear, see below

    Q1. no need to activate the portfast because pvs and vm win7 all using vnic

    A. your answer is Yes, it means without having to enable portfast

    Yes, but if you do, it does nothing

    I am referring only to the network between UCS fabric interconnection and N5k

    See, for example. https://supportforums.Cisco.com/thread/2070841

    There is no tree cover in UCS EHM run below your uplinks, so you can use Port Fast safely.

    PortFast should only be enabled on ports connected to a single host. Connecting hubs, concentrators, switches, bridges, etc. to this interface when the portfast is enabled, may cause temporary bridges loops.

    Please see for establishing a vpc

    http://www.Cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/configuration_guide_c07-543563.html

    Q2. I have in the world, enable portfast and disable bpdguard on base sw and nexus

    According to my interpretation, without having to enable portfast global and disable bpdguard on base sw and nexus

    Is your overall question or interface? I would certainly by interface.

    How can I check that end host in FI mode is used or not?

    This is the default value.

  • EEM with Nexus 5020?

    Hello

    I wonder if it is possible to use the cmdlets to EEM with the Nexus 5000? Based on http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/fundamentals/513_n2_1/b_Cisco_Nexus_5000_Series_NX-OS_Fundamentals_Configuration_Guide_Release_513_N21.pdf of this document, it should be possible, but my 5020 does not know the command "event manager applet. Is there a feature that I need to activate it first?

    Best regards

    Pille

    EEM is supported only on the N7K right now.  While I pushed to get it on the 5K, I don't have any ETA.

Maybe you are looking for