Nexus 7000 SNMP Polling of interfaces within VDC's ?

Hi all,
I hope this is a relatively easy question to answer.
I have some Nexus 7010's that I need to monitor via SNMP. Currently, we can poll the switch and get some info back, however we only see physical interfaces that belong to the Admin VDC.
In order to be able to poll interfaces within a non-Admin VDC, do I have to configure SNMP communities (and an IP to respond to the poll) within each VDC ? Or is there a way to poll them from the Admin VDC?
bash-2.05$ snmpwalk -v 2c -c public <ipaddr-in-admin-vdc> .1.3.6.1.2.1.31.1.1.1.1
IF-MIB::ifName.83886080 = STRING: mgmt0
< **** Eth 8/1 - 8/15 assigned to other VDC's ****>
IF-MIB::ifName.439939072 = STRING: Ethernet8/16
IF-MIB::ifName.439943168 = STRING: Ethernet8/17
IF-MIB::ifName.439947264 = STRING: Ethernet8/18
IF-MIB::ifName.439951360 = STRING: Ethernet8/19
IF-MIB::ifName.439955456 = STRING: Ethernet8/20
IF-MIB::ifName.439959552 = STRING: Ethernet8/21
IF-MIB::ifName.439963648 = STRING: Ethernet8/22
IF-MIB::ifName.439967744 = STRING: Ethernet8/23
IF-MIB::ifName.439971840 = STRING: Ethernet8/24
IF-MIB::ifName.439975936 = STRING: Ethernet8/25
IF-MIB::ifName.439980032 = STRING: Ethernet8/26
Thanks,
Anthony

Hi Anthony,
Think of each VDC as a separate switch. So you need to configure SNMP per VDC.
HTH

Similar Messages

Nexus 7000 w/ 2000 FEX - Interface Status When N7K has power issues

I have multiple nexus 2Ks connected to two N7Ks with my servers connecting to multiple N2Ks accordingly with dual NIC failover capability.
What happens, or what state do the N2K interfaces go into if one of my N7K's looses power given the N2K is effectivly still receiving power?

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 - Management best practice in multi-VDC environment

Hello all, my topology includes an Admin VDC, a Core\Agg VDC and a Storage VDC for FCoE traffic. In the absence of a dedicated OOB Management switch, could I patch from an interface in the Core\Agg VDC to the Mgmt0 interface of the SUP2 and get access to mgmt0 IP of all VDCs? Or is an OOB management switch a necessity to manage this topology?
Any information would be appreciated.
Kind regards
Rays

Thanks for the reply Richard. I understand the risk with not having an OOB network, thanks for that.
So without the OOB management network, are you saying I need a separate switch to which I can connect a physical interface from each VDC to, for management purposes? And to access the Storage and Admin VDC, would I connect the mgmt0 interfaces to the same switch? As i understand it you cannot allocate a physical i/f to the Admin VDC, so the only method is via console or mgmt0 interface...
Thanks for you're assistance...
Rays

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

Migration from Nexus 7000 without VDC to VDC

Hi all
I am working on a DataCenter architecture where we would like to implement Nexus 7000.
For the time being, there only one "context" but we may take the opportunity to implement VDC in a later future
I was not able to find a clear answer on the following :
Can we add the VDC licence & configure a new VDC on a Nexus 7000 running without VDC ?
I suppose this is possible. but does it need to have the whole configuration changed or adding a VDC can be done without any interruption on the current environnement ?
Thanks in advance !

Hello
To have VDC support on n7k you will require following license:
LAN_ADVANCED_SERVICES_PKG
To configure new vdc you need to run:
Nexus(config)# vdc
This will create new VDC which is separate from the current one. It shouldn't affect productional environment since separate processes started for new VDC.
Then you can allocate some interfaces to it and configure.
But you need to be careful to check whether you allocate unused interfaces and don't add resource excessive configuration.
Here is a very good explanation of what is VDC and how it works:
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/ps9512/White_Paper_Tech_Overview_Virtual_Device_Contexts.html
And here is VDC config guide:
http://www.cisco.com/en/US/docs/switches/datacenter/sw/nx-os/virtual_device_context/configuration/guide/vdc_nx-os_cfg.html
HTH,
Alex

Using SNMP to monitor Nexus 7000 Series Supervisor Module

Hello,
I got a Nexus 7000 supervisor module recently, I met a SNMP problem for this module
I would like to know which specific OIDs to use to monitor the following using SNMP on a Nexus 7000 supervisor module:
- Port status
- CPU total utilization
- Power Supply status
- Chassis Fan status
etc.
The Nexus is quite different from other Cisco devices - any help will be appreciated!

hope help, and
port status OID is ifOperStatus
CPU total utilization OID is 1.3.6.1.4.1.9.9.109.1.1.1.1.6.1
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 ifDescr.83886080
.1.3.6.1.2.1.2.2.1.2.83886080 = STRING: mgmt0
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 ifOperStatus.83886080
.1.3.6.1.2.1.2.2.1.8.83886080 = INTEGER: up(1)
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 1.3.6.1.4.1.9.9.109.1.1.1.1.6.1
.1.3.6.1.4.1.9.9.109.1.1.1.1.6.1 = Gauge32: 21
[root@NET-MONITOR-1 ~]#

SNMP polling of VLAN Interfaces on Switches/Routers

Hi,
We were trying to poll VLAN interface traffic using IF-MIB for 6500 Switches/3560 Switches and 7600 Routers. We are getting correct values only for 6500 Switch which shows exactly the traffic passed through that vlan whereas 7600 shows only for SVI interface and 3560 doesn't show for SVI or VLAN.
We would like to know if there are any other MIB files we have to use to get the VLAN traffic statistics of these switches or routers.
Thanks,
NIEG team

When you poll the vlan info, what SNMP community are you using? On some devices you have to for example public@20 where 20 is the vlan in question.
Sent from Cisco Technical Support iPad App

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

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

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

Nexus 7000 - unexpected shutdown of vPC-Ports during reload of the primary vPC Switch

Dear Community,
We experienced an unusual behavior of two Nexus 7000 switches within a vPC domain.
According to the attached sketch, we have four N7Ks in two data centers - two Nexus 7Ks are in a vPC domain for each data center.
Both data centers are connected via a Multilayer-vPC.
We had to reload one of these switches and I expected the other N7K in this vPC domain to continue forwarding over its vPC-Member-ports.
Actually, all vPC ports have been disabled on the secondary switch until the reload of the first N7K (vPC-Role: primary) finished.
Logging on Switch B:
20:11:51 <Switch B> %VPC-2-VPC_SUSP_ALL_VPC: Peer-link going down, suspending all vPCs on secondary
20:12:01 <Switch B> %VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain 1, VPC peer keep-alive receive has failed
In case of a Peer-link failure, I would expect this behavior if the other switch is still reachable via the Peer-Keepalive-Link (via the Mgmt-Port), but since we reloaded the whole switch, the vPCs should continue forwarding.
Could this be a bug or are there any timers to be tuned?
All N7K switches are running on NX-OS 6.2(8)
Switch A:
vpc domain 1
peer-switch
role priority 2048
system-priority 1024
peer-keepalive destination <Mgmt-IP-Switch-B>
delay restore 360
peer-gateway
auto-recovery reload-delay 360
ip arp synchronize
interface port-channel1
switchport mode trunk
switchport trunk allowed vlan <x-y>
spanning-tree port type network
vpc peer-link
Switch B:
vpc domain 1
peer-switch
role priority 1024
system-priority 1024
peer-keepalive destination <Mgmt-IP-Switch-A>
delay restore 360
peer-gateway
auto-recovery reload-delay 360
ip arp synchronize
interface port-channel1
switchport mode trunk
switchport trunk allowed vlan <x-y>
spanning-tree port type network
vpc peer-link
Best regards

Problem solved:
During the reload of the Nexus 7K, the linecards were powerd off a short time earlier than the Mgmt-Interface. As a result of this behavior, the secondary Nexus 7K received at least one vPC-Peer-Keepalive Message while its peer-link was already powerd off. To avoid a split brain scenario, the VPC-member-ports have been shut down.
Now we are using dedicated interfaces on the linecards for the VPC-Peer-Keepalive-Link and a reload of one N7K won't result in a total network outage any more.

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 fcoe expert advice

Hi,
I have one Nexus 7000 with a fcoe supported blade N7K-F132XP-15.
Want to deply this in the LAB. I created a fcoe port for test purpose which is working. But some things are not very clear to me. I am pointing them below.
How to create the interface membership for storage VDC. Right now i created shared interfcae with the default VDC. But can i create the interfcae dedicated? What is the difference between when the interface is shared and dedicated ?
Also, on my shared interfcae while configuring FCoE port, it did not allow me to create priority flow control settings. See the error below.
fcoe-dvt(config-if)# priority-flow-control mode auto
ERROR: pfc config not allowed on shared interface (0x1a000000)
fcoe-dvt(config-if)#
On Nexus 5020, we have priority flow control settings as "auto" for eahc fcoe interface. In the nexus 7000 case, i dont know what and how priority flow control is taking place.
Any white paper on Nexus 7000 fcoe will be greatly appreciated.
Thanks,

Marko,
Yes it is supported, here is a link to the interoperability matrix for storage, also you can find CNA compatibility
here as well. It is a difficult to find on cisco.com because it has been added in with the MDS.
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix1.html
Thanks,
Bill

SNMP Polling from UCS Manager 1.4

I am having trouble with SNMP Polling from UCS Manager 1.4(1j).
I seem to only get SNMP data from Nexus such as those described in (http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/mib/reference/NX5000_MIBRef.html) I don't see any OIDs corresponding to those mentioned specifically for UCS listed in (ftp://ftp.cisco.com/pub/mibs/supportlists/ucs/ucs-manager-supportlist.html).
Documentation on the cisco web site said that UCS Manager 1.4(1) and above will have MIBS such as CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB available.
Is there a separate IP addresses I should poll for these or any specific things that need to be set up?
I am not sure how we can gain access to the UCS related MIB objects exactly. The description on SNMP enable for UCS Manager is very brief (http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/1.4/UCSM_GUI_Configuration_Guide_1_4_chapter6.html#task_2054446421216050764)
It only described the community string set up under UCS Manager ->Admin->Communication Management -> Communication Services, bu didn’t really say anything about which IP addresses from the Management Interfaces should be used to get them.
Has anyone successfully polled data from say the CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB and be able to help?
Thanks in advance.

Yes indeed.
I learnt about the CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB and the other Cisco UCS Manager MIB Support list by selecting UCS Manager under the Unified Computing drop down on this http page you quoted.
(http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/mib/reference/UCS_MIBRef.html)
Is there anything specific from those docs you are referring to that would make it such that we get the Nexus MIBs rather than ones under UCS Manager?
The two IP addresses for Fabric Interconnect A and B under Management Interface only give us info from MIBs listed under the Nexus documentation only. Nothing fir say 1.3.6.1.4.1.9.9.719.1.15.
No SNMP data form the virtual IP address.
Not sure where data under 1.3.6.1.4.1.9.9.719.1.15 would be accessible

Broadcom LiveLink : Receiving MAC flaps with Cisco Nexus 7000

We are migrating from using two Nortel 8600's running VRRP at the distribution to Cisco Nexus 7K's using HSRP. So we have a server connected to two 3750G switches which then connect to the Nexi (previously the 8600's). As soon as we connected the 3750's to the Nexus and moved the gateway to Nexus, LiveLink forces all the servers to alternate traffic between NIC1 and NIC2.
Since LiveLink is a teaming application, it uses virtual mac for nic1 and nic2, but the virtual mac associated with the IP address moves to the active link.
LiveLink is used to check the availability of the gateway by polling the gateway out of each interface using an ARP request.
The problem does not exhibit itself in our Cisco VSS environment, and with Nortel's VRRP. I tried running VRRP on the Nexus but no joy.
Anyone know of a bug that could cause this issue?

Unfortunately we have LiveLink enabled on most of our Windows servers in our data centers. One of my colleagues sent me this bug issue. I'm not sure if this is the cause, but it's worth trying. We will update the NxOs (currently on 5.1.1) next week and see if that fixes the problem.
•CSCtl85080
Symptom: Incomplete Address Resolution Protocol (ARP) entries are observed on a Cisco Nexus 7000 Series switch, along with partial packet loss and a memory leak.
Conditions: This symptom might be seen when ARP packets have a nonstandard size (that is, greater than 64 bytes).
Workaround: This issue is resolved in 5.1.3.

Nexus 7000 SNMP Polling of interfaces within VDC's ?

Similar Messages

Maybe you are looking for