Nexus 7000 single supervisor replacement

Does anyone have a good process for replacing a N7k single supervisor setup if say the supervisor died and had to be replaced. With N7k's and VDC's this becomes more problematic as the global vdc and other vdc's use separate config files . What is the easiest way to get everything back on to the new supervisor ? I have searched all over and can't find a decent process on how this might be done . We do have the configs on a SCP server . It's not as easy as the IOS boxes where you have a single config file to get back on . thanks...

Hi Glen,
I think you could use the below as a useful guide.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/hw/nexus7000/installation/guide/n7k_hig_book/n7k_replacing.html#pgfId-1410535
You could copy the current configuration of all vdc to a usb drive and later restore them back to new sup.
copy running-config usb1:configuration_file_name vdc-all
and later copy the config file back to running config on new sup. Kindly go through the above link to understand better.
Hope this helps you.
Thanks,
Madhu

Similar Messages

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 ~]#

Nexus 7000's Supervisor Module cannot boot up

Hi all,
I have one of redundant supervisor module in Nexus 7010 that cannot boot up. I tried to do recovery from loader but it cannot boot the kickstart image and reboot again. The log is :
loader> set ip 192.168.253.10 255.255.255.0
Correct - ip addr is 192.168.253.10, mask is 255.255.255.0
Found Intel 82546GB [2:9.0] at 0xe040, ROM address 0xf980
Probing...[Intel 82546GB]
Management interface
Link UP in 1000/full mode
Ethernet addr: C0:62:6B:AD:35:80
Address: 192.168.253.10
Netmask: 255.255.255.0
Server: 0.0.0.0
Gateway: 0.0.0.0
loader> boot tftp://192.168.253.43/n7000-s1-kickstart.5.1.5.bin
Address: 192.168.253.10
Netmask: 255.255.255.0
Server: 192.168.253.43
Gateway: 0.0.0.0
Filesystem type is tftp, using whole disk
Booting: /n7000-s1-kickstart.5.1.5.bin console=ttyS0,9600n8nn quiet loader_ver=
"3.22.0"....
....................Image verification OK
INIT: owner_pc=c03a7956 held lock for 5010 msec
NX7 SUP Ver 3.22.0
Serial Port Parameters from CMOS
PMCON_1: 0x200
PMCON_2: 0x0
PMCON_3: 0x3a
PM1_STS: 0x101
Performing Memory Detection and Testing
Total mem found : 4096 MB
Performing memory test... Passed.
NumCpus = 2.
Status 61: PCI DEVICES Enumeration Started
Status 62: PCI DEVICES Enumeration Ended
Status 9F: Dispatching Drivers
Status 9E: IOFPGA Found
Status 9A: Booting From Primary ROM
Status 98: Found Cisco IDE
Status 98: Found Cisco IDE
Status 98: Found Cisco IDE
Status 90: Loading Boot Loader
Reset Reason Registers: 0x0 0x8
              GNU GRUB version 0.97
                Loader Version 3.22.0
Netbooting via EOBC ...
Found Intel 82571EB [4:0.1] at 0xc000, ROM address 0x0000
Probing...[Intel 82571EB]
Sup-to-sup interface
Ethernet addr: 00:00:00:00:05:00
Address: 127.1.2.5
Netmask: 255.255.0.0
Server: 127.1.1.6
Gateway: 0.0.0.0
Address: 127.1.2.5
Netmask: 255.255.0.0
Server: 127.1.1.6
Gateway: 0.0.0.0
Filesystem type is tftp, using whole disk
Booting: /img-sync/curr-ks.img console=ttyS0,9600n8nn isanimg=tftp://127.1.1.6/
img-sync/curr-isan.img quiet loader_ver="3.22.0"....
....................Image verification OK
INIT: version 2
Does anybody have an idea?
Thanks.

That makes sense.
1. Restore the default VDC config.
2. Create your second VDC.
3. Restore the second VDC config.
Don't forget to have a backup of any license files that you may have purchased, for example MPLS.

Nexus 7000 supervisor replacement

I'm trying to get my head around how to replace a supervisor module on a nexus 7000 with a single supervisor. The setup has the default vdc and one other defined. So if a sup was faulty what is the best way to handle this? I have the default vdc config and the other vdc on a tftpboot server. Whats the easiest and fastest way to hand this . In the default vdc add address and copy the default vdc config and then when that's in copy the other vdc config file. Just used to IOS where you normally had a single file and you got the box on the air enough to copy the config file into startup and reloaded . Hope this makes sense. Tried to read some of the docs but it's still not clear what exactly needs to be done. Thanks for any help...

That makes sense.
1. Restore the default VDC config.
2. Create your second VDC.
3. Restore the second VDC config.
Don't forget to have a backup of any license files that you may have purchased, for example MPLS.

Nexus N7K Sup 1 replacement to SUP2E rollback plan and EPLD upgrad time.

Dear Expert,
My customer has N7K SUP1 with HA as below and I need to replace 2 with SUP2E 6.1.2 from SUP1(6.1.1).
As per Cisco document, it is required EPLD upgrade from SUP1 to SUP2E with Fabric-2 module, but there is no guide time for EPLD.
Mod Ports Module-Type                         Model              Status
1    0      Supervisor module-1X                N7K-SUP1           active *
2    0      Supervisor module-1X                N7K-SUP1           ha-standby
3    48     1000 Mbps Optical Ethernet XL Modul N7K-M148GS-11L     ok
4    48     1/10 Gbps Ethernet Module           N7K-F248XP-25      ok
5    24     10 Gbps Ethernet Module             N7K-M224XP-23L     ok
Mod Sw              Hw
1    6.1(1)          3.0
2    6.1(1)          3.0
3    6.1(1)          1.3
4    6.1(1)          1.0
5    6.1(1)          2.0
1. Can I have no downtime to do this activity ?
As per Cisco HW installation guide, It seems I should replace 2 SUP at same time, but if I can replace separately, please let me know.
2. How many minute is required for upgrade EPLD with above HW inventory ?
I assummed this time about 1hr ~ 90 min(max), is it correct ?
3. If this upgrade is failed, then I need to rollback from SUP2E(S2-6.1.2) to original SUP1(S1-6.1.1).
Is below step is correct for rollback ?
- Turn off the power to the switch
- For each Supervisor 2E module installed in the switch, remove the module and replace it with a Supervisor 1 module.
- Power on and verify all module is fine, sh version to check to rollback to S1-6.1.1.
- Run ‘install all epld bootflash:n7000-s1-epld.6.1.1a.img parallel’ after rebooting with original SUP1.
- Verify configuration and status
4. when I downgrade to n7000-s1-epld-6.1.1a, only linecard will be downgrade > or All SUP and FAN or Power module EPLD also downgrade ?
If so, how many minute will re required with previous HW inventory ?
I assummed this time about 40 ~ 60 min(max), is it correct ?
5. From S1-6.1.1a to S2-6.1.2a upgrade, will N2K FEX Software be upgrade as well ?
I need to update this downtime by tomorrow morning, so I seek your advice urgently.
Please share your experinece with me, thanks in advance.
Jason.

Hey Jason,
Regarding your queries:-
1. Can I have no downtime to do this activity ? As per Cisco HW installation guide, It seems I should replace 2 SUP at same time, but if I can replace separately, please let me know. - Replacing supervisors will have downtime as you need to move hardware physically in and out of chassis.
2. How many minute is required for upgrade EPLD with above HW inventory ? I assummed this time about 1hr ~ 90 min(max), is it correct ? - Once the supervisor is upgraded, you may upgrade all the modules parallely so considering the boot time of all these modules you are in safe limit.
3. If this upgrade is failed, then I need to rollback from SUP2E(S2-6.1.2) to original SUP1(S1-6.1.1). Is below step is correct for rollback ? - Indeed its correct.
4. when I downgrade to n7000-s1-epld-6.1.1a, only linecard will be downgrade > or All SUP and FAN or Power module EPLD also downgrade ? If so, how many minute will re required with previous HW inventory ? I assummed this time about 40 ~ 60 min(max), is it correct ? - Check this:
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/epld/epld_rn_6-1.html#wp93995. Also everything will b downgraded so again calculate the booting time + downgrade, i think with this inventory 60 minutes is managable.
5. From S1-6.1.1a to S2-6.1.2a upgrade, will N2K FEX Software be upgrade as well ? - Yes, it will be upgraded.
I also suggest the following links for smooth upgrade:
Replacing Supervisor 1 Modules with Supervisor 2 or Supervisor 2E Modules:http://www.cisco.com/c/en/us/td/docs/switches/datacenter/hw/nexus7000/installation/guide/n7k_hig_book/n7k_replacing.html#pgfId-1410535
Cisco Nexus 7000 Series FPGA/EPLD Upgrade Release Notes, Release 6.1: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/epld/epld_rn_6-1.html
HTH.
Regards,
RS.

Connecting IBM B22 FEXes to Nexus 7000

Hello everybody,
Could someone give an definite answer, better to based on personal experience - is it possible to attach B22 FEX going to the IBM chassis to Nexus 7000 via F2 series 48-port 10G card?
NXOS is currently running 6.1.5a but we plan to upgrade to 6.2.8 or 6.2.12 once we get new 4GB DIMMs for SUP1 modules.
Thanks.

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.

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, 2000, FCOE and Fabric Path

Hello,
I have a couple of design questions that I am hoping some of you can help me with.
I am working on a Dual DC Upgrade. It is pretty standard design, customer requires a L2 extension between the DC for Vmotion etc. Customer would like to leverage certain features of the Nexus product suite, including:
Trust Sec
VDC
VPC
High Bandwidth Scalability
Unified I/O
As always cost is a major issue and consolidation is encouraged where possible. I have worked on a couple of Nexus designs in the past and have levergaed the 7000, 5000, 2000 and 1000 in the DC.
The feedback that I am getting back from Customer seems to be mirrored in Cisco's technology roadmap. This relates specifically to the features supported in the Nexus 7000 and Nexus 5000.
Many large enterprise Customers ask the question of why they need to have the 7000 and 5000 in their topologies as many of the features they need are supported in both platforms and their environments will never scale to meet such a modular, tiered design.
I have a few specific questions that I am hoping can be answered:
The Nexus 7000 only supports the 2000 on the M series I/O Modules; can FCOE be implemented on a 2000 connected to a 7000 using the M series I/O Module?
Is the F Series I/O Module the only I/O Module that supports FCOE?
Are there any plans to introduce the native FC support on the Nexus 7000?
Are there any plans to introduce full fabric support (230 Gbps) to the M series I/O module?
Are there any plans to introduce Fabric path to the M series I/O module?
Are there any plans to introduce L3 support to the F series I/O Module?
Is the entire 2000 series allocated to a single VDC or can individual 2000 series ports be allocated to a VDC?
Is Trust Sec only support on multi hop DCI links when using the ASR on EoMPLS pwire?
Are there any plans to inroduce Trust Sec and VDC to the Nexus 5500?
Thanks,
Colm

Hello Allan
The only IO card which cannot co-exist with other cards in the same VDC is F2 due to specific hardware realisation.
All other cards can be mixed.
Regarding the Fabric versions - Fabric-2 gives much bigger throughoutput in comparing with Fabric-1
So in order to get full speed from F2/M2 modules you will need Fab-2 modules.
Fab2 modules won't give any advantages to M1/F1 modules.
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/data_sheet_c78-685394.html
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/prodcut_bulletin_c25-688075.html
HTH,
Alex

Nexus 7000 vPC modification - avoiding type1 inconsistencies

Hi Everyone,
I need to configure some features on a pair of Nexus 7000's running 4.2(6) - one of them is Root Guard.
I am aware that when I enable Root Guard on the first vPC peer, the vPC will go into suspended state until I configure the other vPC peer identically.
This is causing me a big service disruption headache as I need to do this for a whole Data Centre.
I see on the Nexus 5k, you can do port-profiles which seems to enabled config synchronisation across vPC peers - so I assume the vPC would stay up due to both peers receiving config at exactly the same time - but this feature is not available on Nexus 7k.
Does anybody know for sure if I were to create a scheduled job to run at the same time on both vPC peers with identical config content - i.e. apply Root Guard to vPC - would this prevent the vPC going into suspend state?
If not, do you know of any other ways to prevent vPC going into suspend?
Thanks in advance for any advice!

Hi Raj,
thankyou for your response.
We have VPC between Core - Aggregation - all 7k and Aggregation to Access (5ks). VPC down from Core all the way to Access and also up all the way from Access to Core.
So from a STP point of view, the topology is a single switch for Core, Aggregation and Access - so no loops.
I agree this limits the potential for trouble if a switch is plugged into the access layer by mistake for example - but the customer is adamant they want it (RootGuard).
Thanks,
Oswaldo

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.

Nexus 7000 and 2000. Is FEX supported with vPC?

I know this was not supported a few months ago, curious if anything has changed?

Hi Jenny,
I think the answer will depend on what you mean by is FEX supported with vPC?
When connecting a FEX to the Nexus 7000 you're able to run vPC from the Host Interfaces of a pair of FEX to an end system running IEEE 802.1AX (802.3ad) Link Aggregation. This is shown is illustration 7 of the diagram shown on the post Nexus 7000 Fex Supported/Not Supported Topologies.
What you're not able to do is run vPC on the FEX Network Interface that connect up to the Nexus 7000 i.e., dual-homing the FEX to two Nexus 7000. This is shown in illustrations 8 and 9 of under the FEX topologies not supported on the same page.
There's some discussion on this in the forum post DualHoming 2248TP-E to N7K that explains why it's not supported, but essentially it offers no additional resilience.
From that post:
The view is that when connecting FEX to the Nexus 7000, dual-homing does not add any level of resilience to the design. A server with dual NIC can attach to two FEX so there is no need to connect the FEX to two parent switches. A server with only a single NIC can only attach to a single FEX, but given that FEX is supported by a fully redundant Nexus 7000 i.e., SE, fabrics, power, I/O modules etc., the availability is limited by the single FEX and so dual-homing does not increase availability.
Regards

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

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

Nexus 7000 single supervisor replacement

Similar Messages

Maybe you are looking for