Solved: Re: Nexus 5596 Port FC is UP/DOWN

carmijo · ‎04-02-2018

Hi everyone.

I have a two nexus 5596 with unified port, I am using NPIV and FCOE, the VFC ports work correctly, however when you want to use the FC ports, they remain infinitely UP / DOWN.

2018 Apr 2 14:21:46 Nexus1 last message repeated 1 time
2018 Apr 2 14:21:46 Nexus1 %PORT-5-IF_UP: %$VSAN 200%$ Interface fc4/12 is up in mode F
2018 Apr 2 14:21:50 Nexus1 %PORT-5-IF_DOWN_OLS_RCVD: %$VSAN 200%$ Interface fc4/12 is down (OLS received)
2018 Apr 2 14:21:51 Nexus1 last message repeated 1 time
2018 Apr 2 14:21:51 Nexus1 %PORT-5-IF_UP: %$VSAN 200%$ Interface fc4/12 is up in mode F
2018 Apr 2 14:21:55 Nexus1 %PORT-5-IF_DOWN_OLS_RCVD: %$VSAN 200%$ Interface fc4/12 is down (OLS received)
2018 Apr 2 14:21:55 Nexus1 last message repeated 1 time
2018 Apr 2 14:21:55 Nexus1 %PORT-5-IF_UP: %$VSAN 200%$ Interface fc4/12 is up in mode F
2018 Apr 2 14:21:59 Nexus1 %PORT-5-IF_DOWN_OLS_RCVD: %$VSAN 200%$ Interface fc4/12 is down (OLS received)
2018 Apr 2 14:21:59 Nexus1 last message repeated 1 time
2018 Apr 2 14:21:59 Nexus1 %PORT-5-IF_UP: %$VSAN 200%$ Interface fc4/12 is up in mode F
2018 Apr 2 14:22:03 Nexus1 %PORT-5-IF_DOWN_OLS_RCVD: %$VSAN 200%$ Interface fc4/12 is down (OLS received)

when I check through a show flogi database, I can see the ID but after a moment it goes away

Nexus1# sh flogi database
--------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
--------------------------------------------------------------------------------
fc4/12 200 0x0d00c0 21:00:00:24:ff:19:ae:46 20:00:00:24:ff:19:ae:46
fc4/13 200 0x0d00a0 50:01:43:80:27:2c:2d:c2 50:01:43:80:27:2c:2d:c1
fc4/14 200 0x0d0080 50:01:43:80:27:2c:2d:c5 50:01:43:80:27:2c:2d:c4
vfc43 200 0x0d0020 20:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc44 200 0x0d0000 21:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc45 200 0x0d0060 22:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc46 200 0x0d0040 23:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc4142 200 0x0d0100 50:06:0b:00:00:c3:5e:04 50:06:0b:00:00:c3:5e:05
vfc4142 200 0x0d0200 50:06:0b:00:00:c3:5e:0c 50:06:0b:00:00:c3:5e:0d
vfc4142 200 0x0d0300 50:06:0b:00:00:c3:5e:1c 50:06:0b:00:00:c3:5e:1d
vfc4142 200 0x0d0400 50:06:0b:00:00:c3:5e:14 50:06:0b:00:00:c3:5e:15
vfc4142 200 0x0d0500 50:06:0b:00:00:c3:5e:24 50:06:0b:00:00:c3:5e:25
vfc4142 200 0x0d0600 50:06:0b:00:00:c3:5e:2c 50:06:0b:00:00:c3:5e:2d

Total number of flogi = 13.

Nexus1# sh flogi database
--------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
--------------------------------------------------------------------------------
fc4/12 200 0x0d00c0 21:00:00:24:ff:19:ae:46 20:00:00:24:ff:19:ae:46
fc4/14 200 0x0d0080 50:01:43:80:27:2c:2d:c5 50:01:43:80:27:2c:2d:c4
vfc43 200 0x0d0020 20:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc44 200 0x0d0000 21:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc45 200 0x0d0060 22:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc46 200 0x0d0040 23:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc4142 200 0x0d0100 50:06:0b:00:00:c3:5e:04 50:06:0b:00:00:c3:5e:05
vfc4142 200 0x0d0200 50:06:0b:00:00:c3:5e:0c 50:06:0b:00:00:c3:5e:0d
vfc4142 200 0x0d0300 50:06:0b:00:00:c3:5e:1c 50:06:0b:00:00:c3:5e:1d
vfc4142 200 0x0d0400 50:06:0b:00:00:c3:5e:14 50:06:0b:00:00:c3:5e:15
vfc4142 200 0x0d0500 50:06:0b:00:00:c3:5e:24 50:06:0b:00:00:c3:5e:25
vfc4142 200 0x0d0600 50:06:0b:00:00:c3:5e:2c 50:06:0b:00:00:c3:5e:2d

Total number of flogi = 12.

Nexus1# 2018 Apr 2 14:29:46 Nexus1 %PORT-5-IF_DOWN_OLS_RCVD: %$VSAN 200%$ Interface fc4/13 is down (OLS received)
2018 Apr 2 14:29:47 Nexus1 last message repeated 1 time
2018 Apr 2 14:29:47 Nexus1 %PORT-5-IF_DOWN_OLS_RCVD: %$VSAN 200%$ Interface fc4/14 is down (OLS received)
Nexus1# sh flogi database
--------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
--------------------------------------------------------------------------------
fc4/12 200 0x0d00c0 21:00:00:24:ff:19:ae:46 20:00:00:24:ff:19:ae:46
vfc43 200 0x0d0020 20:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc44 200 0x0d0000 21:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc45 200 0x0d0060 22:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc46 200 0x0d0040 23:21:00:02:ac:01:f9:fb 2f:f7:00:02:ac:01:f9:fb
vfc4142 200 0x0d0100 50:06:0b:00:00:c3:5e:04 50:06:0b:00:00:c3:5e:05
vfc4142 200 0x0d0200 50:06:0b:00:00:c3:5e:0c 50:06:0b:00:00:c3:5e:0d
vfc4142 200 0x0d0300 50:06:0b:00:00:c3:5e:1c 50:06:0b:00:00:c3:5e:1d
vfc4142 200 0x0d0400 50:06:0b:00:00:c3:5e:14 50:06:0b:00:00:c3:5e:15
vfc4142 200 0x0d0500 50:06:0b:00:00:c3:5e:24 50:06:0b:00:00:c3:5e:25
vfc4142 200 0x0d0600 50:06:0b:00:00:c3:5e:2c 50:06:0b:00:00:c3:5e:2d

Total number of flogi = 11.

Thanks

some idea what could be happening

Walter Dey · ‎04-03-2018

additional questions

- are there FC hosts that work ok ?

- are only the FC tape libraries causing the Problems ?

- can you do a "show interfaces status err-disabled"

- is the tape library on the interop matrix ?

View solution in original post

carmijo · ‎04-04-2018

Finally we solved the problem by making a software update to the latest version. thanks to all.

View solution in original post

calopez2 · ‎04-02-2018

Hi,

On NPIV, get show flogi internal event-history errors

look for anything being rejected and post here.

Regards,

Carlos

carmijo · ‎04-02-2018

Hi Carlos:

1) Event:E_DEBUG, length:73, at 284536 usecs after Mon Apr 2 15:31:08 2018
[102] fs_flogi_send_flogi_reject: mts_q == 0, ifindex 0x118b000, port 0x0

2) Event:E_DEBUG, length:148, at 284532 usecs after Mon Apr 2 15:31:08 2018
[102] fs_flogi_send_flogi_reject(5728):fs_flogi_send_flogi_reject: flogi_fc2_req is FALSE pwwn[21:00:00:24:ff:19:ae:46] vsan[200
] ifindex [0x118b000]

3) Event:E_DEBUG, length:73, at 36400 usecs after Mon Apr 2 15:31:04 2018
[102] fs_flogi_send_flogi_reject: mts_q == 0, ifindex 0x118b000, port 0x0

4) Event:E_DEBUG, length:148, at 36396 usecs after Mon Apr 2 15:31:04 2018
[102] fs_flogi_send_flogi_reject(5728):fs_flogi_send_flogi_reject: flogi_fc2_req is FALSE pwwn[21:00:00:24:ff:19:ae:46] vsan[200
] ifindex [0x118b000]

5) Event:E_DEBUG, length:73, at 740796 usecs after Mon Apr 2 15:30:59 2018
[102] fs_flogi_send_flogi_reject: mts_q == 0, ifindex 0x118b000, port 0x0

6) Event:E_DEBUG, length:148, at 740792 usecs after Mon Apr 2 15:30:59 2018
[102] fs_flogi_send_flogi_reject(5728):fs_flogi_send_flogi_reject: flogi_fc2_req is FALSE pwwn[21:00:00:24:ff:19:ae:46] vsan[200
] ifindex [0x118b000]

7) Event:E_DEBUG, length:73, at 140328 usecs after Mon Apr 2 15:30:51 2018
[102] fs_flogi_send_flogi_reject: mts_q == 0, ifindex 0x118b000, port 0x0

8) Event:E_DEBUG, length:148, at 140324 usecs after Mon Apr 2 15:30:51 2018
[102] fs_flogi_send_flogi_reject(5728):fs_flogi_send_flogi_reject: flogi_fc2_req is FALSE pwwn[21:00:00:24:ff:19:ae:46] vsan[200
] ifindex [0x118b000]

9) Event:E_DEBUG, length:73, at 990327 usecs after Mon Apr 2 15:30:46 2018
[102] fs_flogi_send_flogi_reject: mts_q == 0, ifindex 0x118b000, port 0x0

10) Event:E_DEBUG, length:148, at 990323 usecs after Mon Apr 2 15:30:46 2018
[102] fs_flogi_send_flogi_reject(5728):fs_flogi_send_flogi_reject: flogi_fc2_req is FALSE pwwn[21:00:00:24:ff:19:ae:46] vsan[200

calopez2 · ‎04-02-2018

Hello,

1)

Do you see "waiting for port mode" ? in the output

2)

Can you open a TAC Service Request?

Regards,

Carlos

carmijo · ‎04-02-2018

Carlos:

I don´t see "waiting for port mode", I forced the F mode in the FC 4/12 interface until 4/14, but after a few minutes the interfaces remain in error disable.

2018 Apr 2 17:00:11 NexusA %PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 200%$ Interface fc4/12 is down (Error disabled)
2018 Apr 2 17:00:18 NexusA last message repeated 2 times
2018 Apr 2 17:00:18 NexusA %PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 200%$ Interface fc4/13 is down (Error disabled)

any ideas?

regards.

calopez2 · ‎04-02-2018

to verify the config, can you add:

show run interface fc x/y from both sides.

carmijo · ‎04-02-2018

Carlos:

interface fc4/12
switchport mode F
switchport trunk allowed vsan 200
switchport trunk mode auto
no shutdown

version 7.1(3)N1(1)

interface fc4/13
switchport mode F
switchport trunk allowed vsan 200
switchport trunk mode auto
no shutdown

version 7.1(3)N1(1)

interface fc4/14
switchport mode F
switchport trunk allowed vsan 200

regards.
switchport trunk mode auto
no shutdown

calopez2 · ‎04-02-2018

Ca you please remove the pruning, allow all VSANS and let me know if port comes up.

switchport trunk allowed vsan 200

carmijo · ‎04-02-2018

Again after a few minutes it has been in error disable

interface fc4/12
switchport mode F
switchport trunk mode auto
no shutdown

2018 Apr 2 17:24:06 NexusA %PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 200%$ Interface fc4/14 is down (Error disabled)

regards.

calopez2 · ‎04-02-2018

shut no shut the interface to get it out of error disable.

carmijo · ‎04-02-2018

Carlos:

After executing a "shut & no shut", the interface stays up for a few seconds and then falls into the disable error.

NexusA(config)# int fc 4/12-14
NexusA(config-if)# shutdown
NexusA(config-if)# 2018 Apr 2 17:30:27 NexusA last message repeated 2 times
2018 Apr 2 17:30:27 NexusA %PORT-5-IF_DOWN_ADMIN_DOWN: %$VSAN 200%$ Interface fc4/14 is down (Administratively down)
2018 Apr 2 17:30:27 NexusA %PORT-5-IF_DOWN_ADMIN_DOWN: %$VSAN 200%$ Interface fc4/13 is down (Administratively down)
2018 Apr 2 17:30:27 NexusA %PORT-5-IF_DOWN_ADMIN_DOWN: %$VSAN 200%$ Interface fc4/12 is down (Administratively down)

NexusA(config-if)#
NexusA(config-if)#
NexusA(config-if)# no shutdown
NexusA(config-if)# 2018 Apr 2 17:30:33 NexusA %PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 200%$ Interface fc4/14 is down (Error disabled)
2018 Apr 2 17:30:33 NexusA %PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 200%$ Interface fc4/12 is down (Error disabled)
2018 Apr 2 17:30:33 NexusA %PORT-5-IF_UP: %$VSAN 200%$ Interface fc4/12 is up in mode F
2018 Apr 2 17:30:33 NexusA %PORT-5-IF_UP: %$VSAN 200%$ Interface fc4/14 is up in mode F
2018 Apr 2 17:30:33 NexusA %PORT-5-IF_UP: %$VSAN 200%$ Interface fc4/13 is up in mode F

NexusA(config-if)#
NexusA(config-if)#
NexusA(config-if)#
NexusA(config-if)# sh flo da
--------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
--------------------------------------------------------------------------------
fc4/12 200 0x0d00c0 21:00:00:24:ff:19:ae:46 20:00:00:24:ff:19:ae:46
fc4/13 200 0x0d00a0 50:01:43:80:27:2c:2d:c2 50:01:43:80:27:2c:2d:c1
fc4/14 200 0x0d0080 50:01:43:80:27:2c:2d:c5 50:01:43:80:27:2c:2d:c4

Total number of flogi = 13.

NexusA(config-if)# sh co
config-profile configuration copp copyright cores
NexusA(config-if)# sh clock
17:31:23.032 UTC Mon Apr 02 2018
NexusA(config-if)# 2018 Apr 2 17:31:29 NexusA %PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 200%$ Interface fc4/14 is down (Error disabled)
2018 Apr 2 17:32:11 NexusA last message repeated 2 times
2018 Apr 2 17:32:11 NexusA %PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 200%$ Interface fc4/12 is down (Error disabled)

calopez2 · ‎04-02-2018

what is the interface configuration no the NPV?

carmijo · ‎04-02-2018

interface fc4/12
switchport mode F
interface fc4/13
switchport mode F
interface fc4/14
switchport mode F

calopez2 · ‎04-02-2018

If you are showing interface ports for the NPV device then

the port type must be NP.

carmijo · ‎04-02-2018

Carlos: I am using NPIV and FCoE, not NPV.. so I can only configure the following:

Nexus_A(config)# int fc 4/12
Nexus_A(config-if)# switchport mode ?
E E mode
F F mode
SD SD mode
auto Auto mode