How to use a USB console cable from Windows to connect to a NetApp controller
Applies to
- Windows host
- NetApp controller
Description
- NetApp controllers are equipped with an internal console micro USB or USB-C serial port
- Currently the AFF A70, AFF A90, AFF A1K, and FAS2820 uses the USB-C serial port, all users use micro USB
- Any standard USB cable can be used for connectivity
- The USB A to micro USB B NetApp supplied cable has part number X-26009-00, X65420, or 112-00508 (this is just a standard cable)
- The embedded serial port in the controller provides the logic, the cable is more of an extension to the serial port
- The USB serial interface is not to be confused with RS-232 electrical interfaces using mechanical USB form-factor connectors (for example, some E-Series controllers that provide a mini-USB connector but use conventional RS-232 signaling levels)
- This procedure identifies how to connect a USB-equipped Windows host to the serial port on the NetApp controller
Procedure
Perform the following steps:
- From the the Start menu, right-click Computer and select Manage. Alternately open the Run dialog (Windows-R) and enter devmgmt.msc.
- Select Device Manager from the left-hand panel.
- Expand the menu item Ports (COM & LPT).
- Make a note of the COM ports already present.
- When you connect the USB device, a new COM port will be visible.
- This port will be used to access the serial console.
- Connect the USB Type A end of the cable to your Windows Computer.
- Connect the USB type B end of the cable to the NetApp Controller.
- FAS/AFF PCM in the rear of the chassis
- (FAS9000/AFF A700) in front or rear of the chassis
- E-Series controller
- A new COM port should be visible under Ports (COM & LPT).
- Using the newly found COM port, follow the Serial Connectivity section to connect PuTTY via the COM port connection.
Additional Information
Windows Driver
- If you are having issues creating the USB COM link, check to ensure that your drivers are up to date using Windows Update.
- The device driver can be downloaded directly from Microchip.
Procedure for Apple Mac
Follow the embedded serial port manucfacturer instructions for use with Mac.
Alternate Procedures
Windows command line options when the use of Device Manager is not permitted by policy.
Registry Query
C:\Users> reg query HKLM\HARDWARE\DEVICEMAP\SERIALCOMM
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM
\Device\Serial0 REG_SZ COM3 <-- hardware COM port (i.e., an internal fax/modem card)
\Device\VCP0 REG_SZ COM4 <-- virtual COM port (USB)
\Device\VCP1 REG_SZ COM5 <-- virtual COM port (USB)Note the use of the "\" separator. If you use "/" req query will return "ERROR: Invalid key name".
mode command
C:\Users> mode
Status for device COM3:
-----------------------
Baud: 1200
Parity: None
Data Bits: 7
Stop Bits: 1
Timeout: OFF
XON/XOFF: OFF
CTS handshaking: OFF
DSR handshaking: OFF
DSR sensitivity: OFF
DTR circuit: ON
RTS circuit: ON
<...repeats for each available COM port>
NOTE1: 'mode' is a legacy configuration utility. Without arguments the mode command will list ports that are not already open. For example, if you already have COM3 open in PuTTY then COM3 would no longer be displayed in the 'mode' output.
NOTE2: Disregard the configuration settings shown in the output. Those are the defaults and the terminal application will change those as needed.
wmic command
C:\Users> wmic path CIM_LogicalDevice where "Description like '%USB Serial Port%'" get Caption Caption USB Serial Port (COM5) USB Serial Port (COM4)
No Comments