Nexus 5000 operating as a standalone FibreChannel Switch

Similar Questions

• 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

• 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

• 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...

• 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.

• 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

• 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

• 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

• Microsoft 5000 operating manual.

  I just bought a Microsoft 5000 keyboard and would really, really appreciate a manual on how to make use of all key activities.  Where can I get a manual operation.  Please

  Go to the keyboard icon in Control Panel and double click on it...

  Then click on the tab "mouse and keyboard Center"...

  Click on where it says «click here to...» "and you will see a list on what keys do, except for the number keys 1 to 5 on the top...

  To get these out to a State where they can be programmed, press "Star" just after the "5"...

  Assuming that you have installed the drivers, you will be presented with a screen where you can choose what does each key.

  Why is it like this? So you can reprogram the keys without having to go into control panel every time...

  Now you know as much as any textbook could show you, assuming that there is a manual in existence... :-)

• 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

• Configuration of Nexus 5 k for SAN switching between UCS 6100 s and NetApp storage

  We strive to get our configuration of the UCS environment make start SAN LUN on our NetApp storage. We have a pair of Nexus 5Ks with the company / SAN license on them and the 6-port FC module. What to do to configure Nexus 5000 to operate as the SAN switch between the target storage and environment of the UCS?

  You see the 6120 WWPN on the N5Ks? What is the result of 'show flogi database' and 'show int br '.

  You have mapped the FC ports on the 6120 for the proper VSAN?

  NPIV is enabled?

• Cisco Nexus switches

  I'm looking to deploy a series 5100 Cisco NEXUS switch at 10 Gbps.

  I know that the Nexus is supposed to work with the converged network adapter (for 10 Gbps FCoE, etc.), but can it operate without an ANC?

  I want to put some passthrough 10 Gbps modules in my Dell m1000 chassis and the cables directly to the Nexus switch.

  I know that the Nexus is perhaps overstated for this solution, but it is a step in the UCS solution for us.

  Thoughts?

  James

  Hi, you don't need special drivers for "low latency" 10 Gbit ethernet on a 5 k.

  for example, to switch non-nexus 5 k

  PING 10.10.10.1 (10.10.10.1) 56 (84) bytes of data.

  64 bytes of 10.10.10.1: icmp_seq = 1 ttl = 255 time = 0,530 ms

  64 bytes of 10.10.10.1: icmp_seq = 2 ttl = 255 time = 0.618 ms

  and a nexus 5000 with a qlogic 8152

  PING 172.16.78.3 (172.16.78.3) 56 (84) bytes of data.

  64 bytes from 172.16.78.3: icmp_seq = 1 ttl = 128 time = 0.150 ms

  64 bytes from 172.16.78.3: icmp_seq = 2 ttl = 128 time = 0,134 ms

  Oracle rac cluster will fly!

• What does Nexus 1000v Version number Say

  Can any body provide long Nexus 1000v version number, for example 5.2 (1) SV3 (1.15)

  And what does SV mean in the version number.

  Thank you

  SV is the abbreviation of "Swiched VMware"

  See below for a detailed explanation:

  http://www.Cisco.com/c/en/us/about/Security-Center/iOS-NX-OS-reference-g...

  The Cisco NX - OS dialing software

  Software Cisco NX - OS is a data-center-class operating system that provides a high thanks to a modular design availability. The Cisco NX - OS software is software-based Cisco MDS 9000 SAN - OS and it supports the Cisco Nexus series switch Cisco MDS 9000 series multilayer. The Cisco NX - OS software contains a boot kick image and an image of the system, the two images contain an identifier of major version, minor version identifier and a maintenance release identifier, and they may also contain an identifier of reconstruction, which can also be referred to as a Patch to support. (See Figure 6).

  Software NX - OS Cisco Nexus 7000 Series and MDS 9000 series switches use the numbering scheme that is illustrated in Figure 6.

  Figure 6. Switches of the series Cisco IOS dial for Cisco Nexus 7000 and MDS 9000 NX - OS

  

  For the other members of the family, software Cisco NX - OS uses a combination of systems independent of the platform and is dependent on the platform as shown in Figure 6a.

  Figure 6 a. software Cisco IOS NX - OS numbering for the link between 4000 and 5000 Series and Nexus 1000 switches virtual

  

  The indicator of the platform is N for switches of the 5000 series Nexus, E for the switches of the series 4000 Nexus and S for the Nexus 1000 series switches. In addition, Nexus 1000 virtual switch uses a designation of two letters platform where the second letter indicates the hypervisor vendor that the virtual switch is compatible with, for example V for VMware. Features there are patches in the platform-independent code and features are present in the version of the platform-dependent Figure 6 a above, there is place of bugs in the version of the software Cisco NX - OS 4.0(1a) are present in the version 4.0(1a) N1(1a).