Enabling NPIV in CISCO MDS 9500 Series

Hello!!!
If i could get the response for my query.
I need to enable NPIV as we have VM's to be created and allocate SAN storage to them so my CISCO MDS needs to have NPIV enabled. Following queries linked with this:
1. Can i enabled NPIV on single Fibre Channel Port or it gets enabled on the complete SAN Switch
2. Does enabling NPIV impact any other SAN operation. Also my 2- sites are connected via ISL, so is it important to enable NPIV across all my sites or i can enable it only at 1 site where my VM hosts are located.
3. Any reference document for NPIV and related zoning concept.
Thanks in advance.
Faizul Mufti
9958766711

Hi,
1. Can i enabled NPIV on single Fibre Channel Port or it gets enabled on the complete SAN Switch
whole switch
feature npiv
2. Does enabling NPIV impact any other SAN operation. Also my 2- sites are connected via ISL, so is it important to enable NPIV across all my sites or i can enable it only at 1 site where my VM hosts are located.
Will not impact any other SAN operation. Non-disruptive.
"feature npiv" is local to the switch, not fabric wide. Use this command on any switch you want multiple flogi's on a single interface.
3. Any reference document for NPIV and related zoning concept.
I suggest zoning by pwwn
Regards,
David

Similar Messages

Clear old logs in Cisco MDS 9500

Folks,
How i can safely clean the logs of an cisco switch (MDS 9500 family)?

Hi,
Log file is saved in the /var/log/external directory. You cannot change location of the log file. If you want to delete contents of the log file, just use clear logging logfile command. If you want to delete the log file,use delete log: command.
Regards,
S.Vusal

How to keep a Fabric port always enable in a Cisco MDS 9000 Switch?

Dear members:
I work in Datacenter automation solutions using most part of time Virtualization softwares.
I'm having an interst problem with a server while it is booting thru SAN using a logical volume stored in a EMC DMX4 array.
We are trying to boot a VMWare ESX 4.1 OS, but when OS tries to change HBA BIOS driver to ESX device driver during boot process, the Server's HBA logged off from MDS Fabric that it is connected, ESX can't boot and I got a ESX standard prompt.
I think that problem is becuase ESX 4.1 is taking too long to load Storage Drivers during boot process and the consequences is HBA logged off from Fabric.
I already tried to change FLOGI parameters in HBA and Topology architecture, but I didn't have success.
If a try to boot a Microsoft OS like Windows 2008, I don't have this behavior, and OS can boot from SAN without any problem.
Please, if anyone have any idea about how to keep fabric port always enabled, let me know. Any idea or help is very welcome.
Best Regards.
Alexandre Nicolau

Hi,
You can take a look at this document:
http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND_40/QoSCampus_40.html#wp1099352
Hope this helps, please rate if it does.
Kind regards,
- Adrian.

Cisco MDS 9k series

Hello,
I am new to this switch. I want to setup SMTP alerts whenever a port failure / hardware issue happens on the switch. Kindly assist, how we can setup this.
Thanks

Hello,
I believe you are looking to configure Cisco Callhome.
You may use Cisco Fabric Manager to configure callhome, and here is a
doc that talks about it step-by-step -
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/sw/5_0/configuration/guides/sy
smgnt/fm/call.html
The following link talks about configuring callhome, in detail, if you
want to use the command line interface, instead -
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/sw/5_0/configuration/guides/sy
smgnt/nxos/call.html#wp1393543
Here is an example -
callhome
   contract-id <>
   customer-id <>
   switch-priority 2
   email-contact <>
   phone-contact <>
   streetaddress <>
   destination-profile full_txt email-addr <>
   destination-profile short_txt email-addr <>
   destination-profile xml email-addr [email protected]
   no destination-profile full_txt alert-group all
   destination-profile full_txt alert-group environmental
   no destination-profile short_txt alert-group all
   destination-profile short_txt alert-group environmental
   transport email smtp-server port 25
   transport email from <>
   transport email reply-to <>
   enable
   no periodic-inventory notification
   periodic-inventory notification interval 30
Thanks,
Arun

Cisco MDS series switch details

Hello I 'm new to CISCO Switch world.
I 'm working as Clariion Admin and have have taken up the responsibilty to manage switches.Since,i am a novice i need little guidance on how work on cisco switches.I know the Zoning (how zoning done on MDS 9000 series switches) part ,but would like to venture deep into the details on CISCO MDS series switches.
Like, the use of Port channels etc.
Will really appreciate if some one can help me with a link or place ( not the configuration guide) where in i can find details on concentrated more on the theory part .
Thanks in advance!

Actually the best info is in the configuration guides. There are some external companies that run training sessions on the MDS to provide in depth training. There is the MDS cookbook available on CCO that is also a good point of information. If you search on 'MDS white papers' after you login into Cisco.com, there are several good documents that might meet your needs.
Hope this hels,
Mike

Cisco MDS 9509 and HP Blade server problem

I have a big problem , when i connected to MDS 9509 to HP VC-FC 8GB the module in MDS 9509 did not detect the HP module . I think this will be because MDS 9509 uses VSAN technology , but HP blade is not support this feature. Please help me

I am fairly certain that the HP blade chassis has HP branded Brocade FC switches. These switches need to be placed into AG mode and rebooted. On the Cisco MDS core the NPIV feature must be enabled.
Here is more info on the Brocade AG mode -
http://www.brocade.com/solutions-technology/technology/platforms/fabric-os/access_gateway.page
http://www.brocade.com/downloads/documents/data_sheets/product_data_sheets/AccessGateway_DS_02.pdf
Cisco NPIV info
http://www.cisco.com/en/US/prod/collateral/ps4159/ps6409/ps5989/ps9898/white_paper_c11-459263.html

Cisco Aironet 1300 Series Power

Can the 1310ap receive it's power from a POE switch?

Hi Edward,
Sadly the 1310 cannot be powered by PoE ,but, the Power Injector can be up to 100 meters away from the unit.
Dual coaxial cable to run from the power injector to the 1300. See attached notes:
Cisco Aironet 1300 Series
Cisco Aironet 1300 Series Access Point/Bridge Power Injector
The Cisco Aironet 1300 Series Outdoor Access Point/Bridge Power Injector,converts the standard 10/100 BaseT Ethernet interface that is suitable for weather protected areas to a dual F-Type connector interface for coax cables that are more suitable for harsh outdoor environments. The Power Injector also provides power to the outdoor unit over the same cables with a power discover feature and surge protection. To support longer cable runs from your wireless network switch or router, the Power Injector LR is designed to accommodate up to a 100 meter coaxial cable run plus 100 meters of indoor cat5 cable?enabling total cable runs up to 200 meters. The Cisco Aironet 1300 Series Outdoor Access Point/Bridge ships with the Power Injector LR2 and an AC power supply.
From this link:
http://www.cisco.com/en/US/products/ps5861/products_data_sheet09186a008022551d.html
Cisco Aironet 1300 Series Outdoor Access Point/Bridge Hardware Installation Guide
Ethernet Ports
The access point/bridge dual-coax Ethernet ports consists of a pair of 75-ohm F-type connectors, linking the unit to your 100BASE-T Ethernet LAN through the power injector. The dual-coax cables are used to send and receive Ethernet data and to supply inline 48-VDC power from the power injector to the access point/bridge.
Power
The access point/bridge receives inline power from the Cisco Aironet Power Injector (hereafter called the power injector). Dual-coax cables are used to provide Ethernet data and power from the power injector to the access point/bridge. The power injector is an external unit designed for operation in a sheltered environment, such as inside a building or vehicle. The power injector also functions as an Ethernet repeater by connecting to a Category 5 LAN backbone and using the dual-coax cable interface to the access point/bridge.
AIR-PWRINJ-BLR2
F-Type Connectors
Dual coaxial cable carries full-duplex Ethernet, DC power, and full-duplex console port (RS-232 connection)
From this link:
http://www.cisco.com/en/US/products/ps5861/products_data_sheet09186a00802252e1.html
Hope this helps!
Rob

Cisco MDS 9513/9509 LDAP/AD Auth via SSH & Fabric Manager

Hello Folks,
I am trying to look for working config with LDAP auth over SSH. I know how to use them over TACACS+ & Radius. But due to other internal issue, currently I am trying to get the Cisco MDS to directly auth using LDAP/AD. Also, I see no option of LDAP/AD in FM(Fabric Manager), but just TACACS+, Radius, LocalFM and MDS. Do using MDS uses default auth(ie whatever AAA authentication is configured for ? or local DB on the switch). Does the new DCNM supports LDAP/AD auth on the GUI ?
Larger goal is SSH(CLI) & FM(GUI) using the same LDAP/AD auth. I understand the snmp-server user issue. But once I have SSH working over LDAP/AD I can figure that out to..
Here's what I need to ensure when using LDAP/AD auth
1) What is the exact config for this LDAP/AD auth
2) How do I ensure that network-admin & network-opertor roles are assigned when certain AD Groups Logins in Like ADMIN-AD-GROUP , OPERATOR-AD-GROUP --> trying to login to the switch
3) Also using SSL port for LDAP, do details are encrypted over the network.
4) Do I need to use the PASSWORD in paintext when BINDING the BaseDN ?, can it be an encrypted password.
Appreciate any info on this. Thanks for your time.

As of DCNM 6.1 (aka - Fabric Manager Server) we support LDAP authentication adding to existing Radius, TACACS+, local and switch authentications. You can upgrade from Fabric Manager 5.0 to DCNM 5.2 to DCNM 6.1 if you like to keep current performance, events, config data alive. We do recommend fresh install as we don't know what state your server dabatabase might be in. Including some links for you to help out with deployment and best practices (see release notes).
Resources:
Main Website:
http://www.cisco.com/go/dcnm
How To Video Series: http://www.cisco.com/en/US/prod/netmgtsw/ps6505/ps9369/cisco_dc_nm_video_library.html
Install and Licensing Guide:
http://www.cisco.com/en/US/products/ps9369/prod_installation_guides_list.html
Evaluation Licenses: http://tools.cisco.com/SWIFT/LicensingUI/Home?FormId=65
Download Linux and Windows Executables: http://www.cisco.com/cisco/pub/software/portal/select.html?&i=!m&mdfid=281722751
Data Sheets: http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6505/ps9369/data_sheet_c78-639737.html
Install Guide: http://www.cisco.com/en/US/products/ps9369/prod_installation_guides_list.html
Configure Guide: http://www.cisco.com/en/US/products/ps9369/products_installation_and_configuration_guides_list.html
API Programming Guide:
http://www.cisco.com/en/US/products/ps9369/products_programming_reference_guides_list.html
Reference Guide: http://www.cisco.com/en/US/products/ps9369/prod_technical_reference_list.html
Release Notes: http://www.cisco.com/en/US/products/ps9369/tsd_products_support_general_information.html

Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco® NX-OS.
The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response.
Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Gustavo
Please see my responses to your questions:
Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
Now for Data Plane we have two types of traffic – Unicast and Multicast.
The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
Similarity: For both products, loop avoidance is possible due to VSL bit
The VSL bit is set in the DBUS header internal to the Nexus.
It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
This mechanism is used for loop prevention within the chassis.
The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
Differences: In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
For more details please see below presentation:
https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
DCI Scenario: If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
Let us know if you have further questions.
Thanks,
Vishal

ISCSI-to-FC routing in Cisco MDS 9000 Family

Hi,
I'm puzzled about support for iSCSI-to-FC routing in the MDS 9000 family. Earlier hardware such as the 9216i switch and the MPS-14/2 module had a feature to allow an iSCSI Initiator to connect transparently to an FC target. This equipment is now EOL and has been replaced by models such as the 9222i switch and the 18/4 Port Multiservice Module. The datasheets for these replacements strongly imply that they support iSCSI-to-FC routing in a similar way to the earlier products - for example "iSCSI for extension of the SAN to Ethernet attached servers - Extends the benefits of Fibre Channel SAN-based storage to Ethernet attached servers".
I tried to find some hard technical info to confirm this. Chapter 4, "Configuring iSCSI" in "Cisco MDS 9000 Family NX-OS IP Services Configuration Guide Release 5.0(1a)" says that the feature is only available on the IP Storage Module, the 9216i switch, and the MPS-14/2 module, all of which are now EOL. It doesn't mention the replacement models in connection with this functionality, though they are mentioned elsewhere in the book for other features such as FC over IP. I've searched for documentation of the iSCSI support on the new models and the only document which seems relevant is this chapter - but it says it doesn't apply to these models.
Do the replacement models support iSCSI-to-FC routing or not? The datasheets use wording nearly identical to the earlier models in this area, so I assume they do. If they do, how is it configured and where is it documented? I sent feedback on this to the documentation feedback address a while ago, but haven't had a reply.
Many Thanks,
                            jjf

The "Configuring iSCSI" chapter in both 3.3.3 and 4.1.1 documentation similarly talk about IPS and 14/2 modules but make no mention of 18/4, however I've used iSCSI on the 18/4 with both releases. I can only guess the same is true for 5.0 since I have yet to load 5.0 on any switches.
In terms of other documentation I don't think there is any, but all the required information is presented in the "Configuring iSCSI" chapters however it's not the easiest thing to understand from the documentation. Following is the overview I sent to a teammate on how to setup iSCSI.
1. configure Ethernet ports with ip addresses
1a. add a route to the host, iSCSI client, via the gigabit interface 2. enable iscsi on the switch
2a. enable iscsi on the module with the gige port
2b. 'no shut' the iscsi interface corresponding to gige port
      e.g. gige3/4 -> iscsi3/4
2c. no additional configuration of the interfaces is needed, although at some point turning on authentication would be a good idea
3. create iscsi initiator
3a. use the clients ip address as the initiator name, using the node name would be better but I haven't tried it that way so ymmv
      e.g. 'iscsi initiator ip-address xxx.xxx.xxx.xxx'
3b. use a "system assigned" nwwn and set it static
      e.g. 'static pWWN system-assign'
3c. allocate one "system assigned" pwwn and set it static
      e.g. 'static pWWN system-assign 1'
3d. assign vsans, an iscsi initiator can be in more than one vsan
      e.g. 'vsan xxx'
4. create targets
   spcsw1(config)# iscsi virtual-target name iqn.000190300646.fa02cb
   spcsw1(config-iscsi-tgt)# pwwn 50:06:04:8a:d5:f0:79:a1
   spcsw1(config-iscsi-tgt)# initiator ip address xx.xx.xx.xx permit
5. zone the iscsi initiator's pwwn to the target pwwns, use 'sh iscsi initiator configured' to see the pwwn
6. configure the hosts iscsi initiator, usually not much more than specifying the ip address of the gige port on the MDS

The Cisco MDS 9000 Port Analyzer Adapter

Hi,
At my client place, we are having an issue with BackUp via TSM and a library.
We would like to analyse the traffic that pass in the Fiber Channel of our MDS-9513.
From what we saw, Wireshark, our soft to analyse network traffic is only using NIC card to analyse.
Is the only way to analyse the FC traffic to pass via "The Cisco MDS 9000 Port Analyzer Adapter" ?
If that is the only way, is there a way tor ent this equipment for the time necesery to analyse our trace ?
Thank you in advance for you help.
Christian Carrier

The Cisco Traffic Analyzer provides real-time analysis of SPAN traffic or analysis of captured traffic through a Web browser user interface. Traffic encapsulated by one or more Port Analyzer Adapters can be analyzed concurrently with a single PC and ntop, which is public domain software enhanced by Cisco for Fibre Channel traffic analysis. This Cisco Traffic Analyzer solution enables you to quickly determine the throughput for traffic between specific Fibre Channel sources and destinations, all traffic in a particular Virtual SAN (VSAN), or all network traffic. Round trip response times, SCSI I/Os per second, SCSI read vs. write traffic throughput and frame counts, SCSI session status and management task information are provided. Additional statistics are also available on Fibre Channel frame sizes and network management protocols.
For further information click this link.
http://www.cisco.com/en/US/products/hw/ps4159/ps4358/products_data_sheet09186a0080142d34.html#wp1002317

AAA and Cisco MDS switches.........

have configured Cisco ACS 4.0 (TACACS) with Windows AD for all Cisco MDS switches and it is working fine. But local "admin" access to the Cisco MDS switches via telnet is not working. At the same time , if I create a user with "network-admin" role locally, that works but not the default admin user.
Could anyone help me in this regard.

local. Below is the script I used to configure TACACS (Cisco ACS 4.0) on Cisco MDS switches.
config t
# Enable TACACS+
tacacs+ enable
tacacs-server host nnn.nnn.nnn.nnn key 0 xxxxxx
tacacs-server host mmm.mmm.mmm.mmm key 0 xxxxx
# Specify TACACS+ Server groups
aaa group server tacacs+ tacgrp
server nnn.nnn.nnn.nnn
server mmm.mmm.mmm.mmm
aaa authentication login default group tacgrp
aaa authentication login console local
# Enable TACACS+ Accounting
aaa accounting default group tacgrp local
end
copy running-config startup-config
Thanks
MOhan

Cisco MDS Vsan for EVA8100 and EMC Clariion (Same or Seperate)

We have EMC Clariion Frame CX600,CX700 and Cisco MDS Fabric with 2 VSANS currently.
We have just procured EVA8100 and wanted to find out, do we create 2 additional VSANS to support it or add EVA8100 in the existing VSANS.
IVR is not enabled on Cisco MDS.
Also we'll be phasing out the EMC frames and want to migrate data from Clariion LUNS , so debating to put EVA8100 in same VSANS, so data can be migrated over same VSANS.
Also heard that earlier if EMC Clariion was brought online before EVA frame then CommandView would not find EVA, so EVA needs to be booted first (May have been fixed).
Thanks

G'day,
You do not need to create new vsan's when adding new devices to a fabric. You will however need to change the zoning configuration to allow hosts to see the newly attached storage array.
VSAN's are a way of segregating traffic within a single physical fabric. One good method of using them is to segregate development from production traffic.
For further info on VSAN's see "http://www.cisco.com/en/US/netsol/ns340/ns394/ns259/ns261/networking_solutions_white_paper09186a0080114c21.shtml"
Cheers

Cisco aironet 1200 Series access point dropping clients

We are having an issue where our Cisco Aironet 1220 Series AP is constantly dropping clients. We have 3 APs mounted on a single tower, all out of each others range and freq. There are approximatly 30 clients on each AP. We are noticing an increase in dropped customers (up to 20 at a time). ANy suggestions? This only became an issue in the last few weeks, and nothing major has changed.

Hi
Even I was facing almost the same kind of problem. But in my case it was wired clients to the workgroup bridge 350.
I had done lot of testings and reading at that time to resolve this problem.
However in your case I feel your problem can be resolved by keeping the option "Reliable multicast for Workgroup bridges" disabled in the APs under dot11radio interface settings. This is possibly because the radios cannot associate to more than 20 clients at a time if the option is in the enable mode.
You need to keep this option enabled in a root bridge when you have problems of dropping the wired clients to the workgroup bridge.
By keeping this option enabled, you are actually asking the Root bridges to consider the Workgroup bridges as Infrastructure devices and not as clients thereby making the roots to send all the multicasts to the WGBs. However in that case it losses the efficiency of associating more than 20 clients.
Let me know if this resolves your problem.
Regards

After upgrading ios Cisco Catalyst 6500 Series Supervisor Engine 2T ASA-SM is disabled

after upgrading ios Cisco Catalyst 6500 Series Supervisor Engine 2T to the latest release the ASA-SM module is not recognized it is disabled. the FPD
is not recognized any more. reverted back to previous ios with no luck

What IOS are you running on your Supervisor 2T? As long as it's 15.0(1)SY1 or later you should be OK. (Reference).
If it's not working with that I'd try reload of the ASA SM module (from IOS cli - e.g. "hw-module <module#> reset" and, failing that, "no power-enable module <module#>" followed by "power-enable module <module#>) while the new Supervisor is installed. Watch the log for relevant messages during that process.

Enabling NPIV in CISCO MDS 9500 Series

Similar Messages

Maybe you are looking for