Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

6816

March 23rd, 2018 05:00

N1108 Series -- "Uplink" ports do not forward

I've got 40 new 1108s, all nicely configured with port 1, 9,10,11,12 configured as trunks with a default vlan of 1.

I have static addresses in all of the switches, and can ping and talk to the switches on port 1 no problem.

BUT, with exactly the same settings on ports 9-12 (as on port 1), i can't plug a computer into the "Uplink" labelled ports, i can't ping the switch's IP address on default vlan.

I tried connecting the two ports 9 of two switches with cat6, and with PC plugged in to port 1, i can ping the IP of the switch i am plugged into, but not the switch attached to the trunk.

To make it more confusing,  if i connect a dumb switch to the UPLINK ports (9) on each switch, and my pc to the dumb switch, i can talk to each switch perfectly through the dumb switch.

Why would the two switches not be linking on an "Uplink" port   What is the difference between it and a normal port when the config is exactly the same ?   Basically set to trunk, tagged all vlans, untagged default vlan 1

I'm confused !  Any help greatly appreciated... 

Cheers, Dan

 

March 23rd, 2018 20:00

Ok, so i solved this problem while waiting for Dell to come back to me.

Its the most stupid thing i have ever seen.

It has to do with green mode....  Apparently green mode is : 

The command enables both
send and receive sides of a link to disable some functionality for power savings
when lightly loaded. Transition to Low Power Mode does not change the link
status. Frames in transit are not dropped or corrupted in transition to and
from Low Power Mode
 
However, on these Dell 1108 switches, replace "disable some functionality" with  "disable all functionality"
 
To fix the problem, go to your config  and set  for the two Uplink copper ports  :
enable
configure
interface Gi1/0/9
no green-mode eee
!
interface Gi1/0/10
no green-mode eee
!
exit
!
exit
 
THAT"S IT !  Only took the better part of a day to discover it by mistake.  Everything works now.
Hope it helps !

5 Practitioner

 • 

274.2K Posts

March 23rd, 2018 10:00

Are there multiple ports connecting from switch to switch? Do you have a topology you can share with us? Feel free to post up the running config and we can help look through it.

5 Practitioner

 • 

274.2K Posts

March 23rd, 2018 13:00

Just to clarify, it is only port 9 that connects the two switches together? Can you show us the running config, please? # show run

What is the status of these interfaces? 
# show interfaces status

March 23rd, 2018 13:00

yes, only port 9 ... single cable between trunks.

when i first plug the uplink cable in, i can get 1 or 2 seconds of ping from the PC through switch 41 to 42, then it blocks, (like an STP block)

i am not onsite for another hour, and will get the configs and statuses then.

Cheers

 

March 23rd, 2018 13:00

Hi there,

A few of the service tags i have on the bench right now are : 

{Removed}

*****
*****
*****

The topology is very simple.  

switch ports 1-2 (client),9-12 (uplink GbE) all set to trunk all vlans, untagged vlan1 default  

switch addresses 192.168.99.41,42

pc plugged into 41/1

switches linked 41/9 to 42/9

when in this arrangement, i can ping 192.168.99.41 , but cannot ping 192.168.99.42

if i change pc to 42/1, i can ping 192.168.99.42 but not 192.168.99.41

if i connect a dumb switch 3 ports to PC, 41/9 and 42/9 , i can ping both switches.

if i connect 41/1 to 42/1 , PC into 41/2 or 42/2 , i can ping both switches

it's like the UPLINK ports have a different behaviour completely to the client ports

Cheers

March 23rd, 2018 17:00

Hi Daniel,

So i did something interesting... 

I rebooted two switches to factory default, and set only the IP address and a couple of vlans to keep it simple

This is the config in two switches the same , IP 57 and 58  : :::: 

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

console>enable

console#show run

!Current Configuration:
!System Description "Dell EMC Networking N1108P-ON, 6.4.1.4, Linux 3.6.5"
!System Software Version 6.4.1.4
!
configure
vlan 2-3
exit
vlan 2
name "Vlan2"
exit
vlan 3
name "Vlan3"
exit
slot 1/0 2 ! Dell EMC Networking N1108P-ON
stack
member 1 2 ! N1108P-ON
exit
interface vlan 1
ip address 192.168.99.57 255.255.255.0
exit
username "admin" password dce0dd972055a72af7c14fd7310c5a98 privilege 15 encrypted
application install SupportAssist auto-restart start-on-boot
snmp-server engineid local 800002a203e4f0044c896c
exit

 <<<<<<<<<<<<<<<<<<<

I plug PC into port 57/1

i plug link cable from port 57/8 to 58/8  -- can ping 57 and 58 no problems

i plug link cable from port 57/9 to 58/9 - can ping 57 ok, cannot ping 58

For some reason, the uplink port is being treated differently, even though the config is the same

Going in to the web admin, all ports 1-12 are untagged VLAN1

**bleep** ?

March 23rd, 2018 17:00

I have defaulted two switches to original. 

Assigned them an IP address only, and set up two extra vlans that are not tagged .

Default setup is Access on all ports 1-12  with vlan 1

Here is the basic config in two switches : 57 and 58

>>

console#show run

!Current Configuration:
!System Description "Dell EMC Networking N1108P-ON, 6.4.1.4, Linux 3.6.5"
!System Software Version 6.4.1.4
!
configure
vlan 2-3
exit
vlan 2
name "Vlan2"
exit
vlan 3
name "Vlan3"
exit
slot 1/0 2 ! Dell EMC Networking N1108P-ON
stack
member 1 2 ! N1108P-ON
exit
interface vlan 1
ip address 192.168.99.58 255.255.255.0
exit
username "admin" password dce0dd972055a72af7c14fd7310c5a98 privilege 15 encrypted
application install SupportAssist auto-restart start-on-boot
snmp-server engineid local 800002a203e4f0044c8eec
exit

 <<

I have a PC plugged into 57/1

If i plug a link cable from 57/8 (client) to 58/8 (client) i am able to ping 57 and 58 thru the network

If i move that link cable to 57/9 (uplink) to 58/9 (uplink) i am able to ping 57, but not 58 

It would appear that the uplink ports are not forwarding VLAN1 traffic, even though all ports are set the same.

Below is the SHOW INTERFACES and the SHOW SPANNING-TREE DETAIL  (reduced due to size limits)

This is most annoying, as this fault makes absolutely no sense, and i have to deploy these switches asap.

>>>>>>

console#show interfaces status

Port Description Duplex Speed Neg Link Flow M VLAN
State Ctrl
--------- --------------- ------ ------- ---- ------ ----- -- -------------------
Gi1/0/1 Full 1000 Auto Up On A 1
Gi1/0/2 N/A Unknown Auto Down Off A 1
Gi1/0/3 N/A Unknown Auto Down Off A 1
Gi1/0/4 N/A Unknown Auto Down Off A 1
Gi1/0/5 N/A Unknown Auto Down Off A 1
Gi1/0/6 N/A Unknown Auto Down Off A 1
Gi1/0/7 N/A Unknown Auto Down Off A 1
Gi1/0/8 N/A Unknown Auto Down Off A 1
Gi1/0/9 N/A Unknown Auto Down Off A 1
Gi1/0/10 Full 1000 Auto Up On A 1
Gi1/0/11 N/A Unknown Auto Down Off A 1
Gi1/0/12 N/A Unknown Auto Down Off A 1


Port Description Link M VLAN
Channel State
------- ------------------------------ ------- -- -------------------

console#show spanning-tree detail

Spanning Tree: Enabled (BPDU Flooding: Disabled)
Mode: rstp Portfast BPDU Filtering: Disabled
CST Regional Root: 80:00:E4:F0:04:4C:8E:EC
Regional Root Path Cost: 0
ROOT ID
Address 80:00:E4:F0:04:4C:8E:EC
This Switch is the Root.
Hello Time: 2s Max Age: 20s Forward Delay: 15s Transmit Hold Count: 6s
Bridge Max Hops: 20

Number of topology changes: 3 Last Change Occurred: 0d0h10m15s ago
Times: Hold: 6, Hello: 2, Max Age: 20, Forward Delay: 15

Port: Gi1/0/1 Enabled
State: Forwarding Role: Designated
Port ID: 128.1 Port Cost: 20000
Root Protection: No
Designated Bridge Priority: 32768 Address: E4F0.044C.8EEC
Designated Port ID: 128.1 Designated Path Cost: 0
CST Regional Root: 80:00:E4:F0:04:4C:8E:EC CST Port Cost: 0
BPDUs: Sent: 190, Received: 0

Port: Gi1/0/2 Enabled
State: Disabled Role: Disabled
Port ID: 128.2 Port Cost: 0
Root Protection: No
Designated Bridge Priority: 32768 Address: E4F0.044C.8EEC
Designated Port ID: 0.0 Designated Path Cost: 0
CST Regional Root: 80:00:E4:F0:04:4C:8E:EC CST Port Cost: 0
BPDUs: Sent: 0, Received: 0

...

Port: Gi1/0/9 Enabled
State: Disabled Role: Disabled
Port ID: 128.9 Port Cost: 0
Root Protection: No
Designated Bridge Priority: 32768 Address: E4F0.044C.8EEC
Designated Port ID: 128.9 Designated Path Cost: 0
CST Regional Root: 80:00:E4:F0:04:4C:8E:EC CST Port Cost: 0
BPDUs: Sent: 313, Received: 4

Port: Gi1/0/10 Enabled
State: Forwarding Role: Designated
Port ID: 128.10 Port Cost: 20000
Root Protection: No
Designated Bridge Priority: 32768 Address: E4F0.044C.8EEC
Designated Port ID: 128.10 Designated Path Cost: 0
CST Regional Root: 80:00:E4:F0:04:4C:8E:EC CST Port Cost: 0
BPDUs: Sent: 484, Received: 2

......

Port: Po64 Enabled
State: Disabled Role: Disabled
Port ID: 96.273 Port Cost: 0
Root Protection: No
Designated Bridge Priority: 32768 Address: E4F0.044C.8EEC
Designated Port ID: 0.0 Designated Path Cost: 0
CST Regional Root: 80:00:E4:F0:04:4C:8E:EC CST Port Cost: 0
BPDUs: Sent: 0, Received: 0


console#

5 Practitioner

 • 

274.2K Posts

March 26th, 2018 06:00

Great job tracking down the cause of the issue, that was not something I would have initially checked. Doing some digging on the N1100 and green mode, I found that there is a fix for this in the works and should be included in the next firmware release. 

1 Message

May 3rd, 2018 12:00

I know this post has been answered. I had the same problem with the latest firmware available today, on the uplink ports of a N1108P.

BUT I also had the problem on the regular ports of a N1124P today (same FW version). As I migrated a shop with the addition of a N1124P I lost a printer (a Ricoh scanner+printer) and a wifi access point. The thing is I had another access point (same model) and two other Ricoh printer which worked just fine.

When I say "I lost", I'd rather say that the switch saw the devices (sh mac-add tab + sh int stat OK) but level 3 was never really UP, the printer used to be able to ping once in a while, whereas the AP wasn't able to ping anything after having received an address. 

Then I remembered this post, disabled the greenmode on all interfaces and everything went back to the expected behavior.

6 Posts

May 23rd, 2019 08:00

I'd like to expand upon the issues discussed thus far.

We have the same switch and are trying to use it as our PoE source for 8 SonicWALL SonicWave access points.

 

Our configuration for the Wireless is :

X2WLAN 192.168.50.1255.255.255.0Static1 Gbps Full Duplex SonicPoint InterfaceEdit this entry
 X2:V100VAP-Secure-G 192.168.100.1255.255.255.0StaticVLAN Sub-Interface Secure SP-GEdit this entry Delete this entry
 X2:V101VAP-Secure-N 192.168.101.1255.255.255.0StaticVLAN Sub-Interface Secure SP-NEdit this entry Delete this entry
 X2:V200VAP-Open-G 192.168.200.1255.255.255.0StaticVLAN Sub-Interface Open SP-GEdit this entry Delete this entry
 X2:V201VAP-Open-N 192.168.201.1255.255.255.0StaticVLAN Sub-Interface Open SP-N

 

The problem we  are facing is that with the N1108 connected to the X2 port, it seems that it won't pass all the VLANS. We checked the green settings for the ports and disabled it for all of them. We are using port 10 as uplink back to the SonicWALL.  

 

While I've configured this identical scenario with another manufacture's PoE+ switch and it works perfectly out of the box, we continued to be stymied as to how to configure the Dell EMC switch to function properly.

Any help would be appreciated!

No Events found!

Top