Re: help with some show commands on 6454 FI

nflnetwork · ‎09-29-2020

I'm trying to determine where a set of 6454 FI's (f/w 4.1) are connected to as I'm doing some discovery on a new network.

I see that FC Ports 1-2 on FI-A and FI-B are being used however i have no idea what is connected to these ports. (I assume it's a SAN Switch) but I'm not 100% sure. I have noted the WWPN of these FC ports and searched the zoning configuration / aliases on the SAN switches but I could not find anything .

Is there any "show neighbor" type of command I could run on these ports?

How do I figure out what is connected to the ports without having physical access to the site?

Also to note is that the SAN switching would be Brocade in this scenario and not MDS. Maybe that is why I dont see anything?

Kirk J · ‎09-29-2020

End host mode for FC, is somewhat limited for this query, although you can try:

connect nxos
nx-os# show npv internal info external-interface all

Kirk..

nflnetwork · ‎09-29-2020

i dont have those commands

root@FI-B(nx-os)# show npv internal ?
  errors         Show error logs of NPV
  event-history  Show various event logs of NPV
  events         Show important events of NPV
  mem-stats      Show memory allocation statistics of NPV
  msgs           Show various message logs of NPV

root@FI-B(nx-os)# show npv internal

Kirk J · ‎09-29-2020

I am logged in with local 'admin' account on 4.12a on 6454 and get:

UCS-B(nx-os)# show npv internal ?
errors Show error logs of NPV
event-history Show various event logs of NPV
events Show important events of NPV
info Show internal data structure information
mem-stats Show memory allocation statistics of NPV
msgs Show various message logs of NPV
pending-queue Show pending queue information

What does:

show npv status

show?

Not sure what is going on with your FIs.

Kirk...

nflnetwork · ‎09-29-2020

i got it - it was a permission issue with my login ....

Here is my output:

switch-A(nx-os)# show npv internal info external-interface all
External Interface Info:
========================

Interface Information:
  ifindex: fc1/1, Port VSAN: 13, Internal FLOGI VSAN: 13, fcid: 0x072b00
  Internal FLOGI Done: True, In Progress: False
  FSM current state: NPIVP_EXT_IF_ST_UP
  fabric mgmt addr: null
  fabric pwwn: 20:2b:50:eb:1a:8f:3f:c3, fabric nwwn: 10:00:50:eb:1a:8f:3f:c3
  my pwwn: 20:01:00:3a:9c:c0:5d:80, my nwwn: 20:0d:00:3a:9c:c0:5d:81
  fcf_mac: 003a:9cc0:5d88
  Pinned Server Intf Count: 4 Num Logins: 4
  FIP Pinned Server Intf Count: 38

Port Parameters:
  Operational port mode: NP(0x4000),  Logical Ifindex: (0x0)
  Rx B2B Credits: 64, Multiplier: 0, Buff Size: 2112
  Tx B2B Credits: 8, Multiplier: 0, Buff Size: 2048, bbscn: 0
  bbscn_capable: FALSE bbscn_max: 0, port_bbscn: 0

Virtual Fabric Parameters:
 VF Tagging Enabled: FALSE, Core supports VF: FALSE,  Port Mode: NP
 Physical Login Done: FALSE Port Channel: FALSE

Timer & Retry Information:
  Busy Timer              (1), id: 10, active: FALSE time remaining: 0
  Fail Retry Timer        (7), id: 00, active: FALSE time remaining: 0

Statistics:
  flogi retry count            : 1
  ns registration retry count  : 0
Others:
NPIV not enabled on core sysloged: FALSE
VSAN mis-match on core sysloged: FALSE
FC Delete Response Received: TRUE


VSAN 13:

  Timers:
  FDISC Response Timer    (2), id: 72, active: FALSE time remaining: 0
  Error Clear Timer       (6), id: 17518, active: TRUE time remaining: 513

  Statistics:
    number of LS_RJTs rcvd (in last 10 secs) : 0
    LS_RJT timestamp                         : Sat Jun 20 13:23:32 2020

    retry count                  : 5
    pending queue size           : 0

  FLOGIs on this VSAN:
    pwwn : 20:00:00:b1:91:0a:00:08,     fcid : 0x072b01
    pwwn : 20:00:00:b1:91:0a:00:04,     fcid : 0x072b02
    pwwn : 20:00:00:b1:91:0a:00:03,     fcid : 0x072b03
    pwwn : 20:00:00:b1:91:0a:00:02,     fcid : 0x072b04


Interface Information:
  ifindex: fc1/2, Port VSAN: 13, Internal FLOGI VSAN: 13, fcid: 0x072f00
  Internal FLOGI Done: True, In Progress: False
  FSM current state: NPIVP_EXT_IF_ST_UP
  fabric mgmt addr: null
  fabric pwwn: 20:2f:50:eb:1a:8f:3f:c3, fabric nwwn: 10:00:50:eb:1a:8f:3f:c3
  my pwwn: 20:02:00:3a:9c:c0:5d:80, my nwwn: 20:0d:00:3a:9c:c0:5d:81
  fcf_mac: 003a:9cc0:5d89
  Pinned Server Intf Count: 4 Num Logins: 4
  FIP Pinned Server Intf Count: 35

Port Parameters:
  Operational port mode: NP(0x4000),  Logical Ifindex: (0x0)
  Rx B2B Credits: 64, Multiplier: 0, Buff Size: 2112
  Tx B2B Credits: 8, Multiplier: 0, Buff Size: 2048, bbscn: 0
  bbscn_capable: FALSE bbscn_max: 0, port_bbscn: 0

Virtual Fabric Parameters:
 VF Tagging Enabled: FALSE, Core supports VF: FALSE,  Port Mode: NP
 Physical Login Done: FALSE Port Channel: FALSE

Timer & Retry Information:
  Busy Timer              (1), id: 15, active: FALSE time remaining: 0
  Fail Retry Timer        (7), id: 00, active: FALSE time remaining: 0

Statistics:
  flogi retry count            : 1
  ns registration retry count  : 0
Others:
NPIV not enabled on core sysloged: FALSE
VSAN mis-match on core sysloged: FALSE
FC Delete Response Received: TRUE


VSAN 13:

  Timers:
  FDISC Response Timer    (2), id: 66, active: FALSE time remaining: 0
  Error Clear Timer       (6), id: 17317, active: TRUE time remaining: 486

  Statistics:
    number of LS_RJTs rcvd (in last 10 secs) : 0
    LS_RJT timestamp                         : Sat Jun 20 13:23:38 2020

    retry count                  : 5
    pending queue size           : 0

  FLOGIs on this VSAN:
    pwwn : 20:00:00:b1:91:0a:00:05,     fcid : 0x072f01
    pwwn : 20:00:00:b1:91:0a:00:07,     fcid : 0x072f02
    pwwn : 20:00:00:b1:91:0a:00:01,     fcid : 0x072f03
    pwwn : 20:00:00:b1:91:0a:00:06,     fcid : 0x072f04



switch-A(nx-os)#

nflnetwork · ‎09-29-2020

so these are the WWNN/WWPN of the device connected to fc1/1 and fc1/2 ?

  fabric pwwn: 20:2b:50:eb:1a:8f:3f:c3, fabric nwwn: 10:00:50:eb:1a:8f:3f:c3

  fabric pwwn: 20:2f:50:eb:1a:8f:3f:c3, fabric nwwn: 10:00:50:eb:1a:8f:3f:c3

is there any way to know what physical port on that switch is connected? or since they are Brocade it cannot detect that .