Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

MD Series: Pulling MD3060e EMM logs by serial connection or Telnet

Summary: This article covers how to pull Enclosure Management Module (EMM) logs from the serial port on an MD3060e.

This article applies to   This article does not apply to 

Instructions

When using Software Defined Storage (SDS) with the MD3060e dense JBOD, there are no external tools to help pull EMM logs.
This article helps to pull the required logs from the system by connecting to the EMMs.

 

Logs can be pulled through direct serial connection or through a telnet session.

Telnet Prerequisites

  1. Connect a network cable to the EMM on the storage

    1. Port to the right of the red arrow
      Image shows the desired network port

  2. Note which EMM is connected to for future commands

    1. EMM 0 (Top) - 192.168.128.101
    2. EMM 1 (Bottom) - 192.168.128.102

 

Serial Prerequisites

  • Get the proprietary serial cable

    • Part number CT109 or MN657
      Image shows the serial cable connection ends of DB9 and PS2
  • Connect the cable to a serial connection on the device to be used for commands

  • Connect the other end to the EMM using the indicated port below
    Image shows the location of the desired port

 

Steps:

  1. Open software to make a serial or telnet connection

    1. The preferred tool is Putty, as seen below
  2. Create a connection to the EMM

    1. Set up logging in the tool
      Image shows the settings used for serial logging in Putty
    2. Serial connections use:
      • Baud rate: 38400
      • Data bits: 8
      • Stop bits: 1
      • Parity: None
      • Flow control: None
      Image shows the serial settings required for connection listed
  3. If the connection displays a message of "already in session" when using telnet,

    1. Run the following command
      echo "q" | telnet IP address
      Example output:
      [root@localhost ~]# echo "q" | telnet 10.0.150.27
      Trying 10.0.150.27…
      Connected to 10.0.150.27.
      Escape character is '^]'.
      Connection closed by foreign host.
      [root@localhost ~]#
    2. When complete, running the command should work correctly
      Example of a good connection command:
      [root@localhost ~]# telnet 10.0.150.27
      Trying 10.0.150.27…
      Connected to 10.0.150.27.
      Escape character is '^]'.
  4. Once we are correctly configured, we should see the ESM applications menu shown below

    _______________________________________________________________
    
                      ESM Applications 1 User Menu
      <Wemb1ey60 Tray 02, ESM-A, OEM 0, EBOD, FW 03.9D, Slots 60)
    _______________________________________________________________ 
            [c] Admin Interface
            [d] Dump State Capture Buffer (large)
            [e] Display Enclosure Status and Health
            [i] Display Enclosure Inventory
            [n] Display Network Configuration
            [p] Dump Configuration Profile
            [s] List Seven Segment Display Codes
            [?] HeIp
    <main>
  5. Copy and paste the following commands to get all possible output

    ?
    p
    e
    i
    c
    c
    date
    bootHist
    logDump
    nvLogDump
    sasPage81Show
    ddmDataShow
    dcmShow
    dcmCmdStats
    NVDump
  6. Repeat the process for each EMM for the best information

 

Affected Products

MD Series, PowerVault MD3060e