Unsolved
This post is more than 5 years old
3 Posts
0
2397
May 22nd, 2020 12:00
DELL S4810 - previously unused ports stopped working.
Hi all
We have a S4810 that, for some time (around a month or so) had no computer connected there. Previously the ports were working fine. It's using the DELL 1Gb SFP+ Copper.
When the computers needed to be connected again, noneof these ports came alive.
On the computer (iMAC 2013) I get a green sign of connection but can't reach anything on the network.
When watching the port status, when we plug the SFP on it, it starts bouncing between Active/Disconnected.
No one messed with the config. We tried to free up a PortChannel group of ports (2) that were on the same situation - it worked for some time then the computer was disconnected - these ones were unused for almost a year - and the same happened - no connection to those too. Tried the shutdown no shutdown for all these ports with no luck.
Only one VLan defined, very straight forward configuration besides the other two PortChannels and an uplink for the network router.
What could be wrong?? Impossible to restart the switch due to contínuos work, unless defining a maintenance window with some weeks ahead.
Any Help well appreciated.
Best regards
Goncalo
DELL-Josh Cr
Community Manager
•
9.7K Posts
•
43.2K Points
0
May 22nd, 2020 16:00
Hi,
What does Spanning tree show for the port status? It may be changing for forwarding to blocking.
Goncas
3 Posts
0
May 23rd, 2020 12:00
Hi Josh
I didn't had the time to look for what you suggested because another colleague of mine started the full diagnostic test and it's taking a long time (it's been for moe than two hours!!). He lost contact with the swtich on all the Maintenance ports and Console Port (by serial connection). Is this expected?
He told me that looking at the port logs he see's the SFP being recognized, he sees the cable being connected but nothing happens on the computer side. This is happening on several Ports. It's almost like the port is alive but "muted"
It's not the cabling, because the cables on a different switch/network are working fine.
Well, let's wait for the Diag to finish. If it continues like this can we safly power off the switch pulling out the AC power on the PSU's?
Best regards.
Goncalo
Goncas
3 Posts
0
May 24th, 2020 03:00
Hi Josh
Just found the error - not the solution.
The bad ports are gettting the:
LLDP-3-MAC_PHY_CFG: Configuration mismatch with neighbor on interface Te 0/**
error, being the ** the number of the bad ports
Running the
show lldp neighbors detail | find 0
we get:
Local Interface Te 0/24 has 1 neighbor
Total Frames Out: 15
Total Frames In: 7
Total Neighbor information Age outs: 0
Total Multiple Neighbors Detected: 0
Total Frames Discarded: 0
Total In Error Frames: 0
Total Unrecognized TLVs: 0
Total TLVs Discarded: 0
The neighbors are given below:
-----------------------------------------------------------------------
Remote Chassis ID Subtype: Mac address (4)
Remote Chassis ID: 98:4b:e1:ed:27:19
Remote Port Subtype: Mac address (3)
Remote Port ID: 98:4b:e1:ed:27:19
Local Port ID: TenGigabitEthernet 0/24
Locally assigned remote Neighbor Index: 3
Remote TTL: 3601
Information valid for next 1029 seconds
Time since last information change of this neighbor: 00:42:54
MAC PHY Configuration:
Auto-neg supported: 1
Auto-neg enabled: 1
Auto-neg advertised capabilities:
1000BASE-T full duplex mode
Operational MAU type:
unknown
MED Capabilities:
Supported:
LLDP-MED capabilities
Current:
LLDP-MED capabilities
Device Class: Endpoint Class I
---------------------------------------------------------------------------
========================================================================
Local Interface Te 0/26 has 1 neighbor
Total Frames Out: 3
Total Frames In: 3
Total Neighbor information Age outs: 0
Total Multiple Neighbors Detected: 0
Total Frames Discarded: 0
Total In Error Frames: 0
Total Unrecognized TLVs: 0
Total TLVs Discarded: 0
The neighbors are given below:
-----------------------------------------------------------------------
Remote Chassis ID Subtype: Mac address (4)
Remote Chassis ID: 98:4b:e1:ed:27:19
Remote Port Subtype: Mac address (3)
Remote Port ID: 98:4b:e1:ed:27:19
Local Port ID: TenGigabitEthernet 0/26
Locally assigned remote Neighbor Index: 1
Remote TTL: 3601
Information valid for next 781 seconds
Time since last information change of this neighbor: 00:47:02
MAC PHY Configuration:
Auto-neg supported: 1
Auto-neg enabled: 1
Auto-neg advertised capabilities:
1000BASE-T full duplex mode
Operational MAU type:
unknown
MED Capabilities:
Supported:
LLDP-MED capabilities
Current:
LLDP-MED capabilities
Device Class: Endpoint Class I
---------------------------------------------------------------------------
========================================================================
Local Interface Te 0/34 has 1 neighbor
Total Frames Out: 17
Total Frames In: 6
Total Neighbor information Age outs: 0
Total Multiple Neighbors Detected: 0
Total Frames Discarded: 0
Total In Error Frames: 0
Total Unrecognized TLVs: 0
Total TLVs Discarded: 0
The neighbors are given below:
-----------------------------------------------------------------------
Remote Chassis ID Subtype: Mac address (4)
Remote Chassis ID: 98:4b:e1:ed:27:19
Remote Port Subtype: Mac address (3)
Remote Port ID: 98:4b:e1:ed:27:19
Local Port ID: TenGigabitEthernet 0/34
Locally assigned remote Neighbor Index: 2
Remote TTL: 3601
Information valid for next 2702 seconds
Time since last information change of this neighbor: 00:15:01
MAC PHY Configuration:
Auto-neg supported: 1
Auto-neg enabled: 1
Auto-neg advertised capabilities:
1000BASE-T full duplex mode
Operational MAU type:
unknown
MED Capabilities:
Supported:
LLDP-MED capabilities
Current:
LLDP-MED capabilities
Device Class: Endpoint Class I
---------------------------------------------------------------------------
========================================================================
Local Interface Te 0/35 has 1 neighbor
Total Frames Out: 14
Total Frames In: 3
Total Neighbor information Age outs: 0
Total Multiple Neighbors Detected: 0
Total Frames Discarded: 0
Total In Error Frames: 0
Total Unrecognized TLVs: 0
Total TLVs Discarded: 0
The neighbors are given below:
-----------------------------------------------------------------------
Remote Chassis ID Subtype: Mac address (4)
Remote Chassis ID: 98:4b:e1:ed:27:19
Remote Port Subtype: Mac address (3)
Remote Port ID: 98:4b:e1:ed:27:19
Local Port ID: TenGigabitEthernet 0/35
Locally assigned remote Neighbor Index: 1
Remote TTL: 3601
Information valid for next 3121 seconds
Time since last information change of this neighbor: 00:08:02
MAC PHY Configuration:
Auto-neg supported: 1
Auto-neg enabled: 1
Auto-neg advertised capabilities:
1000BASE-T full duplex mode
Operational MAU type:
unknown
MED Capabilities:
Supported:
LLDP-MED capabilities
Current:
LLDP-MED capabilities
Device Class: Endpoint Class I
---------------------------------------------------------------------------
========================================================================
Local Interface Te 0/45 has 1 neighbor
Total Frames Out: 124
Total Frames In: 124
Total Neighbor information Age outs: 0
Total Multiple Neighbors Detected: 0
Total Frames Discarded: 0
Total In Error Frames: 0
Total Unrecognized TLVs: 0
Total TLVs Discarded: 0
Next packet will be sent after 9 seconds
The neighbors are given below:
-----------------------------------------------------------------------
Remote Chassis ID Subtype: Mac address (4)
Remote Chassis ID: 28:c6:8e:1e:de:ef
Remote Port Subtype: Locally assigned (7)
Remote Port ID: g19
Local Port ID: TenGigabitEthernet 0/45
Locally assigned remote Neighbor Index: 1
Remote TTL: 120
Information valid for next 91 seconds
Time since last information change of this neighbor: 01:02:00
Remote Management Address (IPv4): 192.168.0.5
---------------------------------------------------------------------------
What can be happening here?
Best regards
Gonçalo.
Dell-DylanJ
6 Operator
•
2.9K Posts
0
May 25th, 2020 14:00
Just to add to what Josh had already suggested, the message LLDP-3-MAC_PHY_CFG would have me looking at the physical configuration, just based on the text of the error. This is something I've tried on with success on servers, so you might consider it here, but you could turn off auto negotiation and manually configure that to 1 Gb.