SFP Detail Diagnostics Information Nexus 7000

Hello guys,
I have a question about why one port on a Nexus 7000 with a N7K-M132XP-12 (32 port 10G card) doesn't show any values
when looking at "show inter e 9/27 transceiver details", all values are just zero.
N7K# show inter e 9/27 transceiver details
Ethernet9/27
 transceiver is present
 type is 10Gbase-SR
 name is CISCO-EXCELIGHT
 part number is SPP5101SR-C1
 revision is A
 serial number is EXX13050136
 nominal bitrate is 10300 MBit/sec
 Link length supported for 50/125um OM2 fiber is 82 m
 Link length supported for 62.5/125um fiber is 26 m
 Link length supported for 50/125um OM3 fiber is 300 m
 cisco id is --
 cisco extended id number is 4
 number of lanes 1
 SFP Detail Diagnostics Information (internal calibration)
 Current Alarms Warnings
 Measurement High Low High Low
 Temperature N/A 0.00 C 0.00 C 0.00 C 0.00 C
 Voltage N/A 0.00 V 0.00 V 0.00 V 0.00 V
 Current N/A 0.00 mA 0.00 mA 0.00 mA 0.00 mA
 Tx Power N/A 0.00 dBm 0.00 dBm 0.00 dBm 0.00 dBm
 Rx Power N/A 0.00 dBm 0.00 dBm 0.00 dBm 0.00 dBm
 Transmit Fault Count = 2
 Note: ++ high-alarm; + high-warning; -- low-alarm; - low-warning
Tried to remove the SFT+ and inserted a new, but same results, all values are 0.
Does anyone know why it doesn't show any values?
We are runing version 6.2(8)
And here's the port configuration:
interface Ethernet9/27
 switchport
 switchport mode trunk
 spanning-tree port type edge trunk

You are correct.  There isn't any option for seeing the hit count on the prefix-list on the Nexus series.
HTH

Similar Messages

  • NEXUS 7000 xcvrInval

    Hi,
    I have some Nexus 7000 with FET-10G with xcvrInval status
    Eth7/33          N5k-S1-3T-1/3   xcvrInval trunk     auto    auto    Fabric Exte
    and some other FET-10G with notconn status
    Eth7/8           FEX-101         notconnec 1         auto    auto    Fabric Exte
    If I inter exchange the position of both FET-10G the status port doesn´t change
    FET-10G from 7/8 to 7/33
    FET-10G from 7/33 to 7/8
    7/33 holds xcvrInval status
    7/8 holds notconnec status
    I have reconfigured from default interface with same results
    Next you´ll find the same serial number in deferent port, the diference is the current
    when is xcvrInva or when is notconnec
    What can I do to get FET10G in e7/33 validated?
    sh interface e7/33   transceiver details
    Ethernet7/33
          transceiver is present
          type is Fabric Extender Transceiver
          name is CISCO-FINISAR  
          part number is FTLX8570D3BCL-C2
          revision is A  
          serial number is FNS17201TE5    
          nominal bitrate is 10300 MBit/sec
          Link length supported for 62.5/125um fiber is 10 m
          Link length supported for 50/125um OM3 fiber is 100 m
          cisco id is --
          cisco extended id number is 4
          cisco part number is 10-2566-02
          cisco product id is FET-10G            
          cisco vendor id is V02
          number of lanes 1
                 SFP Detail Diagnostics Information (internal calibration)
                    Current              Alarms                  Warnings
                    Measurement     High        Low         High          Low
        Temperature   19.30 C        75.00 C      5.00 C     70.00 C       10.00 C
    [7m--More-- [m
        Voltage        3.31 V         3.63 V      2.97 V      3.46 V        3.13 V
        Current        0.06 mA  --     11.80 mA     4.00 mA    10.80 mA       5.00 mA
        Tx Power          N/A        22.69 dBm    8.69 dBm     18.69 dBm     12.69 dBm
        Rx Power          N/A        22.99 dBm    6.09 dBm     18.99 dBm     10.09 dBm
        Transmit Fault Count = 0
        Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning
    now in slot 7/8
    Ethernet7/8
          transceiver is present
          type is Fabric Extender Transceiver
          name is CISCO-FINISAR  
          part number is FTLX8570D3BCL-C2
          revision is A  
          serial number is FNS17201TE5    
          nominal bitrate is 10300 MBit/sec
          Link length supported for 62.5/125um fiber is 10 m
          Link length supported for 50/125um OM3 fiber is 100 m
          cisco id is --
          cisco extended id number is 4
          cisco part number is 10-2566-02
          cisco product id is FET-10G            
          cisco vendor id is V02
          number of lanes 1
                 SFP Detail Diagnostics Information (internal calibration)
                    Current              Alarms                  Warnings
                    Measurement     High        Low         High          Low
        Temperature   23.17 C        75.00 C      5.00 C     70.00 C       10.00 C
    [7m--More-- [m
        Voltage        3.30 V         3.63 V      2.97 V      3.46 V        3.13 V
        Current        7.50 mA       11.80 mA     4.00 mA    10.80 mA       5.00 mA
        Tx Power      17.65 dBm      22.69 dBm    8.69 dBm     18.69 dBm     12.69 dBm
        Rx Power     -12.21 dBm --   22.99 dBm    6.09 dBm     18.99 dBm     10.09 dBm
        Transmit Fault Count = 0
        Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning
    NX7K-1-VDC-3T-S1-L2FP# sh int e7/33
    Ethernet7/33 is down (Transceiver validation failed)
    admin state is up, Dedicated Interface
      Belongs to Po51
      Hardware: 1000/10000 Ethernet, address: 8478.ac23.6cec (bia 8478.ac23.6cec)
      Description: N5k-S1-3T-1/3
      MTU bytes (CoS values):  MTU  1500(0-2,4-7) bytes  MTU  2112(3) bytes
      BW 10000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, medium is broadcast
      Port mode is trunk
    auto-speed  auto-duplex,, media type is 10G
      Beacon is turned off
      Auto-Negotiation is turned on
      Input flow-control is off, output flow-control is off
      Auto-mdix is turned on
      Rate mode is dedicated
      Switchport monitor is off
      EtherType is 0x8100
      EEE (efficient-ethernet) : n/a
      Last link flapped never
      Last clearing of "show interface" counters 07:22:09
      0 interface resets
      Load-Interval #1: 30 seconds
        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)
        300 seconds input rate 0 bits/sec, 0 packets/sec
        300 seconds output rate 0 bits/sec, 0 packets/sec
      RX
        88 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/FCS  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
        88 unicast packets  0 multicast packets  0 broadcast packets
        0 output packets  0 bytes
        0 jumbo packets
        0 output error  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble  0 output discard
        0 Tx pause
    NX7K-1-VDC-3T-S1-L2FP# sh int e7/33
    Ethernet7/8 is down (Link not connected)
    admin state is up, Dedicated Interface
      Belongs to Po101
      Hardware: 1000/10000 Ethernet, address: 8478.ac23.6cd3 (bia 8478.ac23.6cd3)
      Description: FEX-101
      MTU bytes (CoS values):  MTU  1500(0-2,4-7) bytes  MTU  2112(3) bytes
      BW 10000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, medium is p2p
      Port mode is fex-fabric
    auto-speed  auto-duplex,, media type is 10G
      Beacon is turned off
      Auto-Negotiation is turned on
      Input flow-control is off, output flow-control is off
      Auto-mdix is turned on
      Rate mode is dedicated
      Switchport monitor is off
      EtherType is 0x8100
      EEE (efficient-ethernet) : n/a
      Last link flapped 5week(s) 1day(s)
      Last clearing of "show interface" counters never
      0 interface resets
      Load-Interval #1: 30 seconds
        30 seconds input rate 0 bits/sec, 0 packets/sec
    [7m--More-- [m
        30 seconds output rate 0 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        300 seconds input rate 0 bits/sec, 0 packets/sec
        300 seconds output rate 0 bits/sec, 0 packets/sec
      RX
        10588 unicast packets  0 multicast packets  0 broadcast packets
        4 input packets  0 bytes
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC/FCS  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
        10588 unicast packets  1 multicast packets  0 broadcast packets
        4 output packets  5688 bytes
        0 jumbo packets
        0 output error  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble  0 output discard
        0 Tx pause

    Hi Ans,
    You are rigth, I have defaulted againt the port, now configured with switchport mode FEX, and now the FET-10G is validated
    NX7K-1-VDC-3T-S1-L2FP(config-if)#  description FEX-101
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   switchport
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   switchport mode fex-fabric
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   fex associate 101
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   medium p2p
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   channel-group 101
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   no shutdown
    NX7K-1-VDC-3T-S1-L2FP(config-if)#
    NX7K-1-VDC-3T-S1-L2FP(config-if)# sh int e7/33 status
    Port             Name            Status    Vlan      Duplex  Speed   Type
    Eth7/33          FEX-101         notconnec 1         auto    auto    Fabric Exte
    NX7K-1-VDC-3T-S1-L2FP(config-if)#
    Thanks for your help, and have a nice weekend.
    Atte,
    EF

  • Nexus 7000-Error Message

    Hi
    We are having 2 nexus switches configured in the network as core with HSRP configured between them..The access switches are connected withdual 10G links to both core switches with VPC configured in Nexus..In both core switches 10G module is used for uplink termination..In one of the core switch for this 10 G module we get the follwoing error
    Module-1 reported minor temperature alarm. Sensor=20 Temperature=101 MinThreshold=100 2011 Dec 22 08:10:19 CORE-SEC %PLATFORM-2-MOD_TEMPOK:
    Module-1 recovered from minor temperature alarm. Sensor=20 Temperature=99 MinThreshold=100 even though the room temprature is 23 Degree still we get this error wherein as per the nexus documenation allowed room temparature is 0-40 Degree (Operating temperature: 32º to 104ºF (0º to 40ºC) `
    show module`
    Mod  Ports  Module-Type                      Model                            Status
    1    8      10 Gbps Ethernet XL Module      N7K-M108X2-12L        ok
    2    32    1/10 Gbps Ethernet Module        N7K-F132XP-15          ok
    3    48    10/100/1000 Mbps Ethernet XL Mod N7K-M148GT-11L    ok
    5    0      Supervisor module-1X            N7K-SUP1                      active *
    As per the nexus module documentation for module1 the allwed temparature is 0-40degree wherein the actual room temparatue is 23degree..below is the exception message for module1
    exception information --- exception instance 1 ----
    Module Slot Number: 1
    Device Id         : 49
    Device Name       : Temperature-sensor
    Device Errorcode : 0xc3114203
    Device ID         : 49 (0x31)
    Device Instance   : 20 (0x14)
    Dev Type (HW/SW) : 02 (0x02)
    ErrNum (devInfo) : 03 (0x03)
    System Errorcode : 0x4038001e Module recovered from minor temperature alarm
    Error Type       : Minor error
    PhyPortLayer     :
    Port(s) Affected :
    DSAP             : 39 (0x27)
    UUID             : 24 (0x18
    Same module exists in second Nexus 7000 which is in same datacenter but not getting this alarm..
    can anyone please suggest on the same..Software details are as below
    Software
      BIOS:      version 3.22.0
    kickstart: version 5.1(3)
      system:    version 5.1(3)
      BIOS compile time:       02/20/10
      kickstart image file is: bootflash:///n7000-s1-kickstart.5.1.3.bin
      kickstart compile time:  12/25/2020 12:00:00 [03/11/2011 07:42:56]
      system image file is:    bootflash:///n7000-s1-dk9.5.1.3.bin
      system compile time:     1/21/2011 19:00:00 [03/11/2011 08:37:35]

    Hi Sameer
    Temperature alarm means that one particular sensor on the linecard warms up to 101 degree.
    This can be caused by damaged sensor or problems with cooling in that particular part of chassis.
    You can check temperature on the module using following command:
    show environment temperature module 1
    Tru to move the module to another slot. If the issue reoccure - open a TAC case.
    HTH,
    Alex

  • Nexus 7000 Platform Logging

    Hello,
    We recently had a power supply failure in one of our Nexus 7000s, and I noticed that the syslog for the Platform is only present in the default VDC, and not in any of the other VDCs syslogs. Is this by design, or is there a logging level I can turn up in another VDC to capture this log? Thanks for any input
    syslog from default VDC -
    2013 Mar 18 23:10:34  %PLATFORM-2-PS_CAPACITY_CHANGE: Power supply PS3 changed i
    ts capacity. possibly due to power cable removal/insertion (Serial number xxxxxxxx)
    nothing in the VDC where I would like to get the logging
    default VDC logging level -
    xxx7K02# show log level platform
    Facility        Default Severity        Current Session Severity
    platform                5                       5
    0(emergencies)          1(alerts)       2(critical)
    3(errors)               4(warnings)     5(notifications)
    6(information)          7(debugging)
    xxx7K02#
    loggging from the specific VDC where we have management tools.
    xxx-LOW# show log level platform
    Facility        Default Severity        Current Session Severity
    platform                5                       5
    0(emergencies)          1(alerts)       2(critical)
    3(errors)               4(warnings)     5(notifications)
    6(information)          7(debugging)
    xxx-LOW#

    Hello Carl,
    What version of code are you running on your Nexus 7k?
    The expected behavior is:
    "When a hardware issue occurs, syslog messages are sent to all VDCs."
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/nx-os/virtual_device_context/configuration/guide/vdc_mgmt.html#wp1170241
    Dave

  • Dell Servers with Nexus 7000 + Nexus 2000 extenders

    << Original post by smunzani. Answered by Robert. Moving from Document section to Discussions>>
    Team,
    I would like to use some of the existing Dell Servers for new network design of Nexus 7000 + Nexus 2000 extenders. What are my options for FEC to the hosts? All references of M81KR I found on CCO are related to UCS product only.
    What's best option for following setup?
    N7K(Aggregation Layer) -- N2K(Extenders) -- Dell servers
    Need 10G to the servers due to dense population of the VMs. The customer is not up for dumping recently purchased dell boxes in favor of UCS. Customer VMware license is Enterprise Edition.
    Thanks in advance.

    To answer your question, the M81KR-VIC is a Mezz card for UCS blades only.  For Cisco rack there is a PCIe version which is called the P81.  These are both made for Cisco servers only due to the integration with server management and virtual interface functionality.
    http://www.cisco.com/en/US/prod/collateral/ps10265/ps10493/data_sheet_c78-558230.html
    More information on it here:
    Regards,
    Robert

  • Privilege Level for Tacacs Account in Nexus 7000

    Hi,
    I have configured the Tacacs (ACS 4.2v) on Nexus 7000 (as mentioned below) and works fine but unlike IOS (6509) It's doesn't prompt that you are in userexec mode (>) and then need to type enable and password for full privilege.
    In n7k when I entered into "configure terminal" It won't allow me to access other commands.
    How to login into level 15 privilege mode after authenticating from tacacs
    (config)# show running-config tacacs+
    tacacs-server key 7 "xxxxx"
    tacacs-server host x.x.x.x key 7 "xxxx"
    aaa group server tacacs+ TacServer
        server x.x.x.x (same ip as tacacs-server host)
        use-vrf management
        source-interface Vlan2
    (config)# show running-config aaa
    aaa authentication login default group TacServer
    aaa authentication login console local
    aaa user default-role
    Here below are the commands accessible in "Terminal" currently
    (config)# ?
      no        Negate a command or set its defaults
      username  Configure user information.
      end       Go to exec mode
      exit      Exit from command interpreter
    isb.n7k-dcn-agg-1-sw(config)#

    Hi Jan.nielsen
    Issue is resolved but by another way.
    I have found the same resolution too of custom attirbute command but the Custom attribute Option for shell command wasn't available in ACS v4.2, so after enabling shell for users and by clicking exec--> Shell Exec and enabling priviledge level 15 in the same box of Shell options, It start working without any command

  • Query Nexus 7000 Enviroment Status

    Hi,
    I am trying to figure out how to query a Nexus 7010 Chassis about its enviroment. For our IOS Switches we use SNMP and OID 1.3.6.1.4.1.9.9.13.1 and the related sub OIDs. But this does not work on the Nexus 7010 with version 5.1. Is querying the information not supported or is there another OID?

    Hi,I am trying to figure out how to query a Nexus 7010 Chassis about its enviroment. For our IOS Switches we use SNMP and OID 1.3.6.1.4.1.9.9.13.1 and the related sub OIDs. But this does not work on the Nexus 7010 with version 5.1. Is querying the information not supported or is there another OID?
    Hi,
    Check out the below link for nexus 7000 MIB reference ..
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/mib/quickreference/Cisco_Nexus_7000_Series_NX-0S_MIB_Quick_Reference_chapter1.html#con_40545
    Hope to Help !!
    Ganesh.H

  • Log configuration changes to syslog on Nexus 7000?

    I need to be able to log any configuration changes to syslog on our Nexus switches. On IOS this is easy with the archive commands, but I'm a little stuck trying to do this on our Nexus gear. On the IOS gear I run the commands:
    archive
    log config
    logging enable
    logging size 100
    hidekeys
    notify syslog
    How do I do the equivalent on NX-OS?

    ​Cisco NX-OS can log configuration change events along with the individual changes when AAA command accounting is enabled.
    With command accounting enabled, all CLI commands entered, including configuration commands, are logged to the configured AAA server. Using this information, a forensic trail for configuration change events along with the individual commands entered for those changes can be recorded and reviewed.
    Because of this capability, it is strongly advised that AAA command accounting be enabled and configured.
    Refer to the “TACACS+ Command Accounting” section of this document for more information.
    The Nexus 7000, by default keeps a local accounting log of all the configuration commands entered on the device; you can view this with the 'show accounting log' command.
    In NX-OS, we changed the way logging works.  We keep a local accounting log of all the
    configuration changes ("show accounting log"), but if you want to send those logs to a
    server, it must be done with through a TACACS server.  Please see the below documentation:
    Configuring AAA on Nexus
    TACACS command accounting
    -Thanks
    Vinod
    **Encourage Contributors. RATE Them.**

  • EtherChannel problem on Nexus 7000

    Dear NetPro gurus,
    One of my customer is trying to setup an EtherChannel (LACP) on a pair of Nexus 7000.  However, doesn't matter what we do, the port Eth 1/17 always become suspended.  We have tried swapping fiber cables and also swapping SFPs, but no help.
    The 1st Nexus 7010 - called 'VIWLRCA'
    The 2nd Nexus 7010 - called 'VIWLRCB'
    Originally port eth 1/17 are left as 'normal' trunk port, and we can see eth 1/17 shows up fine under 'show interface brief'
    viwlrca-PROD# sh run int eth 1/17
    interface Ethernet1/17
      switchport
      switchport mode trunk
      udld disable
      no shutdown
    viwlrca-PROD# sh run int eth 1/18
    interface Ethernet1/18
      switchport
      switchport mode trunk
      udld disable
      channel-group 20 mode active
      no shutdown
    viwlrca-PROD# sh int brief
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/17       1       eth  trunk  up      none                        10G(S) --
    Eth1/18       1       eth  trunk  up      none                        10G(S) 20
    Eth1/19       --      eth  routed down    SFP not inserted           auto(S) --
    Eth1/20       --      eth  routed down    SFP not inserted           auto(S) --
    Eth1/21       --      eth  routed down    Administratively down      auto(S) --
    Eth1/22       --      eth  routed down    Administratively down      auto(S) --
    Eth1/23       --      eth  routed down    Administratively down      auto(S) --
    Eth1/24       --      eth  routed down    Administratively down      auto(S) --
    Eth2/25       --      eth  routed down    Administratively down      auto(D) --
    Eth2/26       --      eth  routed down    Administratively down      auto(D) --
    Eth2/27       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/28       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/29       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/30       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/31       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/32       --      eth  routed down    SFP not inserted           auto(D) --
    viwlrca-PROD#
    But as soon as I add the Eth 1/17 back onto PortChannel 20
    The Eth 1/17 becomes "Suspended" straight away
    viwlrca-PROD# sh int brief
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Por
    t
    Interface                                                                    Ch
    Eth1/17       1       eth  trunk  down    suspended                  auto(S) 20
    Eth1/18       1       eth  trunk  up      none                        10G(S) 20
    Eth1/19       --      eth  routed down    SFP not inserted           auto(S) --
    Eth1/20       --      eth  routed down    SFP not inserted           auto(S) --
    Eth1/21       --      eth  routed down    Administratively down      auto(S) --
    Eth1/22       --      eth  routed down    Administratively down      auto(S) --
    Eth1/23       --      eth  routed down    Administratively down      auto(S) --
    Eth1/24       --      eth  routed down    Administratively down      auto(S) --
    Eth2/25       --      eth  routed down    Administratively down      auto(D) --
    Eth2/26       --      eth  routed down    Administratively down      auto(D) --
    Eth2/27       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/28       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/29       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/30       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/31       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/32       --      eth  routed down    SFP not inserted           auto(D) --
    viwlrca-PROD#
    viwlrca-PROD# 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
    20    Po20(SU)    Eth      LACP      Eth1/17(s)   Eth1/18(P)  
    viwlrca-PROD#
    Config on Primary Nexus:-
    viwlrca-PROD# sh run
    !Command: show running-config
    !Time: Tue Mar 22 06:04:26 2011
    version 5.1(1a)
    hostname PROD
    cfs eth distribute
    feature udld
    feature interface-vlan
    feature lacp
    feature vpc
    feature vtp
    username admin password 5 $1$pkJaKHZW$Sx4wpDG5xXYkD.QfDk/Cg.  role vdc-admin
    no ip domain-lookup
    ip domain-name vfc.com
    crypto key param rsa label viwlrca-PROD.vfc.com modulus 2048
    snmp-server user admin vdc-admin auth md5 0x05f7328e3b39a70be09abc3056ec2819 pri
    v 0x05f7328e3b39a70be09abc3056ec2819 localizedkey
    vrf context management
    spanning-tree pathcost method long
    spanning-tree port type edge bpduguard default
    spanning-tree loopguard default
    spanning-tree vlan 1-3967,4048-4093 priority 4096
    interface Vlan1
    interface Vlan161
      ip address 172.30.161.2/24
    interface Vlan162
      ip address 172.30.162.2/24
    interface Vlan163
      ip address 172.30.163.2/24
    interface Vlan164
      ip address 172.30.164.2/24
    interface Vlan165
      ip address 172.30.165.2/24
    interface Vlan190
      ip address 172.30.190.2/24
    interface port-channel20
      switchport
      switchport mode trunk
    interface Ethernet1/17
      switchport
      switchport mode trunk
      udld disable
      channel-group 20 mode active
      no shutdown
    interface Ethernet1/18
      switchport
      switchport mode trunk
      udld disable
      channel-group 20 mode active
      no shutdown
    interface Ethernet1/19
    interface Ethernet1/20
    interface Ethernet1/21
    interface Ethernet1/22
    interface Ethernet1/23
    interface Ethernet1/24
    interface Ethernet2/25
    interface Ethernet2/26
    interface Ethernet2/27
    interface Ethernet2/28
    interface Ethernet2/29
    interface Ethernet2/30
    interface Ethernet2/31
    interface Ethernet2/32
    interface Ethernet2/33
    interface Ethernet2/34
    interface Ethernet2/35
    interface Ethernet2/36
    interface Ethernet3/25
    interface Ethernet3/26
    interface Ethernet3/27
    interface Ethernet3/28
    interface Ethernet3/29
    interface Ethernet3/30
    interface Ethernet3/31
    interface Ethernet3/32
    interface Ethernet3/33
    interface Ethernet3/34
    interface Ethernet3/35
    interface Ethernet3/36
    line vty
    viwlrca-PROD#
    Config for Secondary Nexus 7000
    VIWLRCB-PROD# sh run
    !Command: show running-config
    !Time: Tue Mar 22 09:19:22 2011
    version 5.1(1a)
    hostname PROD
    cfs eth distribute
    feature interface-vlan
    feature lacp
    feature vpc
    feature vtp
    username admin password 5 $1$Lc486EOm$EtKhZWuxGjWWokfeuUsMk.  role vdc-admin
    no ip domain-lookup
    ip domain-name vfc.com
    crypto key param rsa label VIWLRCB-PROD.vfc.com modulus 2048
    snmp-server user admin vdc-admin auth md5 0xeb607b54234985ed6740c5fdbb8d84c6 pri
    v 0xeb607b54234985ed6740c5fdbb8d84c6 localizedkey
    vrf context management
    spanning-tree pathcost method long
    spanning-tree port type edge bpduguard default
    spanning-tree loopguard default
    spanning-tree vlan 1-3967,4048-4093 priority 8192
    interface Vlan1
    interface port-channel20
      switchport
      switchport mode trunk
    interface Ethernet1/17
      switchport
      switchport mode trunk
      channel-group 20 mode active
      no shutdown
    interface Ethernet1/18
      switchport
      switchport mode trunk
      channel-group 20 mode active
      no shutdown
    interface Ethernet1/19
    interface Ethernet1/20
    interface Ethernet1/21
    interface Ethernet1/22
    interface Ethernet1/23
    interface Ethernet1/24
    interface Ethernet2/25
    interface Ethernet2/26
    interface Ethernet2/27
    interface Ethernet2/28
    interface Ethernet2/29
    interface Ethernet2/30
    interface Ethernet2/31
    interface Ethernet2/32
    interface Ethernet2/33
    interface Ethernet2/34
    interface Ethernet2/35
    interface Ethernet2/36
    interface Ethernet3/25
    interface Ethernet3/26
    interface Ethernet3/27
    interface Ethernet3/28
    interface Ethernet3/29
    interface Ethernet3/30
    interface Ethernet3/31
    interface Ethernet3/32
    interface Ethernet3/33
    interface Ethernet3/34
    interface Ethernet3/35
    interface Ethernet3/36
    line vty
    VIWLRCB-PROD#
    Cheers,
    Hunt

    Quick troubleshoot:
    Default all interfaces in newly created port-channel as well as the port-channel interface, then delete port-channel interface.  Recreate port-channel without the LACP protocol:
    interface e1/17,e1/18
      switchport
      channel-group 20 mode on
      no shutdown
      exit
    interface port-channel20
      switchport
      switchport mode trunk
      no shutdown
      exit
    show port-channel summ
    show int trunk
    HTH,
    Sean

  • Frame generated by Nexus 7000 contains unexpected trailer when using GRE

    I have observed some unexpected behaviour on a Nexus 7000 running 6.1(2) in respect of the Ethernet II frame generated when the Nexus 7000 is a GRE Tunnel endpoint.
    The device receiving the Frame is discarding it and I waiting for the vendor to confirm the reason for this discard. However in case the reason is due to the Ethernet frame being "unusual" I am curious if any one else has come across this.
    To generate the Frame I perform a ping (on a workstation) which the Nexus 7000 in encapsulating in a GRE tunnel. Using Wireshark on the Nexus 7000 egress interface I observed that the Frame contains the following protocols as expected; ETH:IP:GRE:IP:ICMP:data
    When I issue the command "ping -l 1" on the workstation the Frame details from Wireshark are:
    Frame 84 bytes on wire
    Total IP payload = 53 bytes
     Outer IP header (20 bytes)
     GRE ( 4 bytes)
     Inner IP header (20 bytes)
     ICMP (header 8 bytes  payload 1 byte)
    Ethernet Trailer length = 17 bytes
    What is curious about this Frame is that;
    a) No Ethernet Trailer is needed as the IP payload exceeds 46 bytes
    b) The amount of padding applied is what would be needed if the Inner IP datagram were encapsulated directly in an Ethernet II Frame. The Inner ip datagram is 29 bytes octets and hence padding needed = 46 - 29  = 17.
    By doing ping sweep from length 1 to 18 the observed padding was;
    1,17
    2,16
    3,15
    17,1
    18,0
    So it would appear that the Nexus is adding padding to the Ethernet frame as though it were containing the pre GRE payload only.

    What module are you using?
    Ron

  • PortChannel table in Nexus 7000/5000 through MIB

    I  ma trying to query   "CISCO-PORT-CHANNEL"   mib on Nexus 7000 for portChannel table and I  am not getting any info.
    Nexus OS versions : Nexus   7000  -  System version: 5.1(5)
                                        Nuxus 5000 -    System version: 5.0(3)N1(1a)
    Any pointers  or other alternatives to query through MIB ?
    Thanks,
    Chandra.

    Hi Chandra
    Here is a list of MIBS supproted on n7k:
    ftp://ftp-sj.cisco.com/pub/mibs/supportlists/nexus7000/Nexus7000MIBSupportList.html
    You can use IF-MIB to poll general port-channel interface status and use following command to find port-channel interface indexes among other output:
    sh interface snmp-ifindex
    Also you can poll the CISCO-LAG-MIB for port-chanel details.
    HTH,
    Alex

  • Connecting Cisco ASA TenGig to Nexus 7000

    I am attempting to connect an ASA 5585 TenGig to a Nexus 7000 F2 TenGig port. 
    I am seeing the error message Transceiver validation failed when I insert the SFP into the port.  I know that the error is removed when I enter the command switchport mode fex-fabric, and have tried the configuration, but am unable to get the link to come up.at either end. I am also aware that LACP is not supported when switchport mode fex-fabric is configured. 
    ASA is in multiple context mode with portchannel interfaces allocated to the relevant ASA context.  Anyone know if I am overlooking something?  Anyone run into this issue before?
    Nexus 7000:
    Eth1/1       1       eth  access down    Transceiver validation fa  auto(D) 2
    Eth1/2       1       eth  access down    Transceiver validation fa  auto(D) 2
    interface Ethernet1/1
      switchport mode trunk
      switchport trunk allowed vlan 1-10
      channel-group 2 mode active
      no shutdown
    interface Ethernet1/2
      switchport mode trunk
      switchport trunk allowed vlan 2-10
      channel-group 2 mode active
      no shutdown
    interface port-channel2
      switchport mode trunk
      switchport trunk allowed vlan 2-10
    ASA5585:
    interface TenGigabitEthernet0/6
    channel-group 2 mode active
    interface TenGigabitEthernet0/7
    channel-group 2 mode active
    interface Port-channel2
    interface Port-channel2.2
    vlan 2
    interface Port-channel2.3
    vlan 3
    context inside
      allocate-interface Port-channel2.1
      allocate-interface Port-channel2.2
      config-url disk0:/inside.cfg

    In my case, I was getting this error on a interface of a Nexus C6001 with the FET-10G transceiver.  I was able to clear it up by temorarily replacing and configuring a slower GLC-T which worked as expected.  I then removed all the settings an got the FET-10G to link.

  • Ask the Expert: Basic Introduction and Troubleshooting on Cisco Nexus 7000 NX-OS Virtual Device Context

    With Vignesh R. P.
    Welcome to the Cisco Support Community Ask the Expert conversation.This is an opportunity to learn and ask questions of Cisco expert Vignesh R. P. about the Cisco® Nexus 7000 Series Switches and support for the Cisco NX-OS Software platform .
    The Cisco® Nexus 7000 Series Switches introduce support for the Cisco NX-OS Software platform, a new class of operating system designed for data centers. Based on the Cisco MDS 9000 SAN-OS platform, Cisco NX-OS introduces support for virtual device contexts (VDCs), which allows the switches to be virtualized at the device level. Each configured VDC presents itself as a unique device to connected users within the framework of that physical switch. The VDC runs as a separate logical entity within the switch, maintaining its own unique set of running software processes, having its own configuration, and being managed by a separate administrator.
    Vignesh R. P. is a customer support engineer in the Cisco High Touch Technical Support center in Bangalore, India, supporting Cisco's major service provider customers in routing and MPLS technologies. His areas of expertise include routing, switching, and MPLS. Previously at Cisco he worked as a network consulting engineer for enterprise customers. He has been in the networking industry for 8 years and holds CCIE certification in the Routing & Switching and Service Provider tracks.
    Remember to use the rating system to let Vignesh know if you have received an adequate response. 
    Vignesh 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 discussion forum shortly after the event. This event lasts through through January 18, 2013. Visit this forum often to view responses to your questions and the questions of other community members.

    Hi Vignesh
    Is there is any limitation to connect a N2K directly to the N7K?
    if i have a an F2 card 10G and another F2 card 1G and i want to creat 3 VDC'S
    VDC1=DC-Core
    VDC2=Aggregation
    VDC3=Campus core
    do we need to add a link between the different VDC's
    thanks

  • LMS 4.2.2 Interface utilisation on Nexus 7000

    Hi All,
    I'm trying to poll some interfaces for their utilization on a nexus 7000 through LMS 4.2.2.
    When I create a poller fot the specific instances, the LMS recognises the instances, but after activating the poller I get the error "No Such Instance - The specified instance is not available".
    No info is displayed when I generate an interface utilization report for the specific nexus.
    When I activate the automonitor for interface utilization, the interfaces on the nexus are polled.
    On the cisco website there are some features listed which LMS does not support on the Nexus 7000, but polling is not in that list (neither in the supported feature list).
    Any tips?
    Thanks for your help.
    Joris

    Any Idea..??

  • ESXi 4.1 NIC Teaming's Load-Balancing Algorithm,Nexus 7000 and UCS

    Hi, Cisco Gurus:
    Please help me in answering the following questions (UCSM 1.4(xx), 2 UCS 6140XP, 2 Nexus 7000, M81KR in B200-M2, No Nexus 1000V, using VMware Distributed Switch:
    Q1. For me to configure vPC on a pair of Nexus 7000, do I have to connect Ethernet Uplink from each Cisco Fabric Interconnect to the 2 Nexus 7000 in a bow-tie fashion? If I connect, say 2 10G ports from Fabric Interconnect 1 to 1 Nexus 7000 and similar connection from FInterconnect 2 to the other Nexus 7000, in this case can I still configure vPC or is it a validated design? If it is, what is the pro and con versus having 2 connections from each FInterconnect to 2 separate Nexus 7000?
    Q2. If vPC is to be configured in Nexus 7000, is it COMPULSORY to configure Port Channel for the 2 Fabric Interconnects using UCSM? I believe it is not. But what is the pro and con of HAVING NO Port Channel within UCS versus HAVING Port Channel when vPC is concerned?
    Q3. if vPC is to be configured in Nexus 7000, I understand there is a limitation on confining to ONLY 1 vSphere NIC Teaming's Load-Balancing Algorithm i.e. Route Based on IP Hash. Is it correct?
    Again, what is the pro and con here with regard to application behaviours when Layer 2 or 3 is concerned? Or what is the BEST PRACTICES?
    I would really appreciate if someone can help me clear these lingering doubts of mine.
    God Bless.
    SiM

    Sim,
    Here are my thoughts without a 1000v in place,
    Q1. For me to configure vPC on a pair of Nexus 7000, do I have to connect Ethernet Uplink from each Cisco Fabric Interconnect to the 2 Nexus 7000 in a bow-tie fashion? If I connect, say 2 10G ports from Fabric Interconnect 1 to 1 Nexus 7000 and similar connection from FInterconnect 2 to the other Nexus 7000, in this case can I still configure vPC or is it a validated design? If it is, what is the pro and con versus having 2 connections from each FInterconnect to 2 separate Nexus 7000?   //Yes, for vPC to UCS the best practice is to bowtie uplink to (2) 7K or 5Ks.
    Q2. If vPC is to be configured in Nexus 7000, is it COMPULSORY to configure Port Channel for the 2 Fabric Interconnects using UCSM? I believe it is not. But what is the pro and con of HAVING NO Port Channel within UCS versus HAVING Port Channel when vPC is concerned? //The port channel will be configured on both the UCSM and the 7K. The pro of a port channel would be both bandwidth and redundancy. vPC would be prefered.
    Q3. if vPC is to be configured in Nexus 7000, I understand there is a limitation on confining to ONLY 1 vSphere NIC Teaming's Load-Balancing Algorithm i.e. Route Based on IP Hash. Is it correct? //Without the 1000v, I always tend to leave to dvSwitch load balence behavior at the default of "route by portID". 
    Again, what is the pro and con here with regard to application behaviours when Layer 2 or 3 is concerned? Or what is the BEST PRACTICES? UCS can perform L2 but Northbound should be performing L3.
    Cheers,
    David Jarzynka

Maybe you are looking for

  • BI-IP: Change of characteristic value in ABAP EXIT planning function

    Hi I have created a planning function of the type EXIT with reference data without blocks. In method IF_RSPLFA_SRVTYPE_IMP_EXEC_REF~EXECUTE I am going to implement my code. Now, one of the purposes is to update the VALIDTO of an existing record. Is i

  • Dr8-a via usb2 external box

    I recently bought the msi dr8-a writer and have problems burning dvd's. I burnt the dvd that came with it without any problems, but when i tried to burn other media (ritek and bulkpaq) it keeps coming up with a "focus or tracking" error. I have conne

  • Multiple Files at sender side

    Hi Friends, Im working with a scenario which gives me two different files for a single sender file. My sender structure is having a filed "Position" which takes 2 values ( One and Two). When i give these values, my target structure will be of two mes

  • Website window size...Mac vs PC

    I created a website in Dreamweaver: MJADesign.biz. When I view it on my iMac at home it is a beautiful thing. When I view it at my local library on their PC it is huge (and ugly) thing. My website is 800x748. Why would it appear huge on the PC and ne

  • Facebook app not appearing

    My facebbok app got stuck so I deleted it. I reinstalled it but it's not appearing but the app store says it is installed.