What is an "Unused" port

mbayard
mbayard
in SAN
Hello,

I activated 2 ports on a SAN switch 2 days ago, they are used as a trunk for ISL with another switch within the fabric. However, in Stor2RRD, they remain in the "Unused" section of the ports ... Any idea why ? Because there is no traffic (yet) on them ?

Thanks.

Comments

  • Karel
    Karel
    Hello,

    what physical state do your 2 ports have?

    You can find it by these snmpwalk commands:
    snmpwalk -v 1 -c public <SAN SWITCH IP> 1.3.6.1.4.1.1588.2.1.1.1.6.2.1.37
    snmpwalk -v 1 -c public <SAN SWITCH IP> 1.3.6.1.4.1.1588.2.1.1.1.6.2.1.3

    If they have statuses noTransceiver or noSigDet, so we take them as unused.

    Description:
    swFCPortSpecifier 1.3.6.1.4.1.1588.2.1.1.1.6.2.1.37
    - This string indicates the physical port number of the addressed port.
    - The format of the string is: <slot/>port, 'slot' being present only for bladed systems.

    swFCPortPhyState 1.3.6.1.4.1.1588.2.1.1.1.6.2.1.3
    - The physical state of the port.
    - Possible values are:
    • noCard        (1)   - No card is present in this switch slot.
    • noTransceiver (2)   - No Transceiver module in this port (Transceiver is the generic name for GBIC, SFP, and so on).
    • laserFault    (3)   - The module is signaling a laser fault (defective GBIC).
    • noLight       (4)   - The module is not receiving light.
    • noSync        (5)   - The module is receiving light but is out of sync.
    • inSync        (6)   - The module is receiving light and is in sync.
    • portFault     (7)   - The port is marked faulty (defective GBIC, cable, or device).
    • diagFault     (8)   - The port failed diagnostics (defective G_Port or FL_Port card or motherboard).
    • lockRef       (9)   - The port is locking to the reference signal.
    • validating    (10)  - The module is being validated.
    • invalidModule (11)  - The module is invalid.
    • noSigDet      (14)  - No Signal is detected in the port.
    • unknown       (255) - The module is unknown.
  • mbayard
    mbayard
    Hello Karel,

    Both ports are in (6) status :

    SNMPv2-SMI::enterprises.1588.2.1.1.1.6.2.1.3.1 = INTEGER: 6
    SNMPv2-SMI::enterprises.1588.2.1.1.1.6.2.1.3.2 = INTEGER: 6

    They are also "green" in the Health Status section / Ports tab.

  • Karel
    Karel
    Hello Martin,

    this is really strange...

    Send us outputs from these commands via email to support@stor2rrd.com or you can share it here, thanks.

    cd /home/stor2rrd/stor2rrd # or where is your STOR2RRD working dir
date
ls -l data/<affected switch name>/unused_ports.txt
cat data/<affected switch name>/unused_ports.txt
ls -l tmp/menu.txt
  • mbayard
    mbayard
    edited April 2018 
    [apache@server stor2rrd_MUTU]$ date
    Mon Apr  9 12:50:28 CEST 2018

    [apache@server stor2rrd_MUTU]$ ls -l data/SWITCH/unused_ports.txt
    -rw-r--r-- 1 apache apache 64 Mar  8 14:32 data/SWITCH/unused_ports.txt

    [apache@server stor2rrd_MUTU]$ cat data/SWITCH/unused_ports.txt  
    port1 : noTransceiver : unknown
    port2 : noTransceiver : unknown

    [apache@server stor2rrd_MUTU]$ ls -l tmp/menu.txt
    -rwxr-xr-x 1 apache apache 143232 Apr  9 00:15 tmp/menu.txt


    Seems that data/SWITCH/unused_ports.txt has wrong date ...




  • Karel
    Karel
    Hello Martin,

    yes, that is an issue.
    This file should be removed if the switch has not unused ports. We will add this function to our code.

    Just remove this old file and run load.sh, it should help.

    cd /home/stor2rrd/stor2rrd # or where is your STOR2RRD working dir
    rm data/<affected switch name>/unused_ports.txt
    rm tmp/2.*
    ./load.sh

    Let us know, thanks.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Categories

In this Discussion