Using CDP to trace physical networking connections in Netapp Data ONTAP

Have you ever been on a Data ONTAP system without a clear idea of how the physical network is connected, and wish you could interrogate your network to try and find out? If so, CDP – the Cisco Discovery Protocol – might be the help you’re looking for. This can be very useful on systems with large or complex Ethernet configurations.

Once CDP is enabled in Data ONTAP, your Cisco switches will become aware of which NetApp systems are cabled to which ports. It wil know both the source port (on the NetApp) and the destination port (on the Cisco switch).

CDP has been available in Netapp Data ONTAP since version 7.3.3, and is supported in both 7-mode and cDOT, and it’s simply enabled with an option command.

To enable CDP in 7-mode:

options cdpd.enable on

To enable CDP in cDOT:

node run -node * options cdpd.enable on

NOTE that the command is cdpd.enable, not cdp.enable

The nice thing about NetApp’s CDP implementation is that it is bi-directional. That means you can query CDP from either the Cisco switch or the NetApp controller and see information — meaning you don’t have to rely on a network administrator to provide you the information!

To view CDP information from 7-mode Data ONTAP, you would use the cdpd show-neighbors command.

Here’s some sample output:

nas1> cdpd show-neighbors

Local  Remote          Remote                 Remote           Hold  Remote   

Port   Device          Interface              Platform         Time  Capability

------ --------------- ---------------------- ---------------- ----- ----------

e0M    charles         e0M                    FAS3170           146   H        

e0M    nane-cat4948-sw GigabitEthernet1/8     cisco WS-C4948-.  174   RSI      

e3a    nane-nx5010-sw. Ethernet1/4            N5K-C5010P-BF     173   SI       

e4a    nane-nx5010-sw. Ethernet1/14           N5K-C5010P-BF     177   SI

Note that we can see that Filer’s HA partner, charles, is in the output. Here we can see that e0M is cabled to port Giga1/8 on nane-cat4948, whereas e3a and e4a are cabled to Eth1/4 andEth1/14 on nane-nx5010-sw respectively.

This is incredibly useful information if you’re ever trying to track down how a system is cabled!

To view CDP information from clustered Data ONTAP, use the run -node nodeName cdpd show-neighbors command.

The output is the same format as in 7-mode:

dot83cm::> node run -node local cdpd show-neighbors

Local  Remote          Remote                 Remote           Hold  Remote   

Port   Device          Interface              Platform         Time  Capability

------ --------------- ---------------------- ---------------- ----- ----------

e6a    nane-nx5010-sw. Ethernet1/12           N5K-C5010P-BF     145   SI       

e6b    nane-nx5010-sw. Ethernet1/5            N5K-C5010P-BF     145   SI       

e4a    dot83cm-01      e4a                    FAS3240           161   H        

e4b    dot83cm-01      e4b                    FAS3240           161   H        

e0a    nane-cat4948-s. GigabitEthernet1/9     cisco WS-C4948-.  168   RSI

In this case, e6a and e6b go to the same switch, with e4a and e4b going to the other node in this HA pair — that’s my switchless cluster interconnect. e0a goes to an older Catalyst switch.

To view CDP information from Cisco IOS or NX-OS, use the show cdp neighbors command.

Sample output:

nane-nx5010-sw# show cdp neighbors

Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge

                  S - Switch, H - Host, I - IGMP, r - Repeater,

                  V - VoIP-Phone, D - Remotely-Managed-Device,

                  s - Supports-STP-Dispute, M - Two-port Mac Relay

Device ID              Local Intrfce   Hldtme  Capability  Platform      Port ID

US-WLM-LS02            mgmt0           124     R S I       WS-C6509      Gig5/1

nane-cat4948-sw        Eth1/2          179     R S I       WS-C4948-10GE Ten1/49

dot83cm-01             Eth1/3          163     H           FAS3240       e6b   

mystic                 Eth1/4          127     H           FAS3170       e3a   

dot83cm-02             Eth1/5          158     H           FAS3240       e6b

In IOS/NX-OS, you may wish to run show cdp neighbors detail to gather more information.

To view CDP information using the vSphere/VI Client: Connect to the vCenter Server/Virtual Center or ESX host using the vSphere/VI Client.

·         Select the ESX host in the Inventory.

·         Click the Configuration tab.

·         Click Networking.

·         Click the Info icon to the right of the vSwitch, under Properties.

More detailed information about the output of CDP commands can be found in the relevant Ontap Network Management Guide, Cisco and VMware documentation.

Hope you don’t have to trace the network cables the hard way anymore!

Password Recovery Procedure for the MDS 9000 Series Multilayer Directors and Fabric Switches

Introduction

This document describes the procedure to recover a lost administrator password from the console port of a Cisco MDS 9000 Series Switch.

Prerequisites

Requirements

You must perform the password recovery procedure on the Supervisor Engine module that will become the active Supervisor Engine module after completion of the recovery procedure. In order to ensure that the other Supervisor Engine module does not become the active module, perform one of these two options:

• Physically remove the other Supervisor Engine module from the chassis.
• Change the console prompt of the other Supervisor Engine module to one of these two prompts until you complete the procedure:
  
  • loader>
  • switch (boot)#
  Note: Refer to the Cisco MDS 9000 Family of Multilayer Directors and Fabric Switches configuration guide for more information about these prompts.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Step-by-Step Procedure

Perform these steps in order to recover a lost administrator password from the console port of a MDS 9000 switch:

1. Perform these steps in order to establish a console session to the MDS 9000 switch:
   
   1. Connect one of the supplied RJ-45-to-DB-9 adapters to the PC serial (COM) port.
   2. Connect the other end of the supplied RJ-45-to-DB-9 adapter to the RS-232 management port on the MDS 9000 switch.
      Note: The RS-232 management port is labeled CONSOLE.
      
      
   3. Launch HyperTerminal on the PC.
      Terminal emulation software enables communication between the storage router and your PC during setup and configuration. The terminal emulation software is frequently a PC application such as HyperTerminal or ProComm Plus.
   4. Choose these settings:
      
      • Bits per second: 9600
      • Data bits: 8
      • Parity: None
      • Stop bits: 1
      • Flow control: None
      Note: You can set the Bits per second field to 38400 if this configuration connects to an MDS 9500.
      
2. Reboot the switch in one of these ways:
   
   • Issue the reload command if there is a Telnet session with administrator rights.
     

     switch#reload
     
     The supervisor is going down for reboot NOW!

   • If the command is not available, power reset the switch.
3. When the switch begins its SAN-OS software boot sequence, hold the Ctrl key and press the ] key to generate the Ctrl-] key sequence.
   This key sequence brings up the switch(boot)# prompt.
   

   Ctrl-]
   
   switch(boot)#

   Note: If you use different terminal emulation software, the break key sequence can differ. Refer to Standard Break Key Sequence Combinations During Password Recovery for commonly used break key sequences.
   Note the bin image file name that is displayed on the screen after the "Booting kickstart image" message while the device is booting.
4. Change to configuration mode.
   

   switchboot#configure terminal
   

5. Issue the admin-password command in order to reset the administrator password.
   In this example, the password is set to “password”.
   

   switch(boot-config)#admin-password password
   

6. Exit to the EXEC mode.
   

   switch(boot-config)#exit
   
   switchboot#

7. Issue the load command in order to load the SAN-OS software image. This is the image name that was noted as part of step 3.
   In this example, san-ios.img is the name of the software. Most likely, the format looks like m9500-sf1ek9-mz-2.1.2b.bin.
   

   switch(boot)#load bootflash:san-ios.img
   

8. Save the software configuration.
   

   switch#copy running-config startup-config
   

   Note: The next time that you try to connect to the console port of the MDS 9000 switch, you must enter either the new administrator password or the monitor password that you created.
9. Insert the Supervisor Engine that you previously removed, log in, and verify the changed password.

Install Cisco MDS9124 / MDS9148 additional FC port licenses

Install Cisco MDS9124  / MDS9148 additional FC port licenses

Login to Cisco License portal at www.cisco.com/go/license

****

Use the PAK (Product Authorization Key) number that came with the printed card beside the switch or SFPs.

To obtain the license, you will be required to provide the switch serial number along with the PAK. Use the following procedure to obtain the switch serial number:

Login to the switch command console

Issue the “show license host” command. The serial number is the character string after the “=” sign.

For example:

CISCOSWITCH# show license host
License hostid: VDH=FOX12345ABC

Here, the switch serial number is “FOX12345ABC”

Follow the wizard in Cisco’s web site to obtain the license. It will arrive to your email mailbox, or it can be downloaded directly from this portal.

Login to Cisco device manager app as admin

Go to the menu Admin, Flash Files

****

Click Copy …

****

Select:

Direction: Server - > Switch
Protocol: tftp
Server Address: Type in the IP address of the tftp server where the “.lic” file is
Server file: locate the file in the tftp server, but remove all the path, except for the filename. This is because it needs to be relative to the tftp server root
Switch File: use “bootflash:/FILENAME.lic”, being FILENAME.lic the same name as the original file.

Most of the parameters here will be auto-populated, but need to be verified.

****

Click Apply.

Then Close and refresh the previous window. The file should be listed in the bootflash:

****

Click Close

At this point, there are two ways to install the license in the switch:

Option 1, using the command line

Login to the switch using a ssh session and type the command to activate the license as follows:

CISCO-MDS9124 login: admin

Password:

Cisco Storage Area Networking Operating System (SAN-OS) Software

TAC support: http://www.cisco.com/tac

Copyright (c) 2002-2007, Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software may be covered under the GNU Public

License or the GNU Lesser General Public License. A copy of

each such license is available at

http://www.gnu.org/licenses/gpl.html and

http://www.gnu.org/licenses/lgpl.html

CISCO-MDS9124# install license bootflash:FILENAME.lic

Installing license .......done

CISCO-MDS9124# exit

Option 2, using the device manager:

Go to the Cisco device manager and goto admin, Licenses

****

Click the Install tab and click the arrow at the end of the “URI” box. It will show a drop down list of the license files present in the switch. Select the one that was recently transferred to the switch.

Both boxes, URI and Target Filename will be automatically populated

Click Install

****

After a few seconds the Status should say “success”

****

Verify that the licenses were installed properly:

Go to the Cisco device manager and goto admin, Licenses

****

The additional licenses should show up in the Features tab, Installed Count column

****

And on the main window, also the ports should be activated.