yes, the firmware is the newest version for that switch. We also updated the firmware on our Cisco Catalyst 4500e Core Switch to exclude that der is a problem between Dell & Cisco.
actually the problem is not resolved... and I don't have any idea what I can do.
But I don't think it's a Radius problem. I think that the N Series and our Cisco Catalyst speak a different Rapid-PVST language and that cause the problems.
What I figured out:
It's maybe not a firmware bug, we tested N3000Advv6.5.3.37, N3000Advv6.5.3.36 and N3000AdvLitev6.5.3.3
N3000AdvLitev6.5.3.3 is working on other DELL Stacks without that problem
We connected the not working DELL Stack to the same CORE-Switch like the working DELL-Stack --> Does not resolve the problem
We removed the Portchannel config from the Stack
If I change the Uplink port from TE2/0/1 to any other TE Port on that switch, Spanning-Tree put that port into discarded mode and says that he is the root-bridge... If I disable Spanning Tree everything is working fine and all devices are reachable. We also disabled all other ports to exclude that the issue is caused by a connected device --> Issue persists
If I plug back into TE2/0/1 the port is back in forwarding state (root role and the root ID is correct)
The TE Ports have the same configuration (also on the cisco side)
If I connect a CISCO Access Switch to the Dell Stack (trunk), configure a port in the same vlan and connect a device to that port, the device is reachable immediately. The interessting point: In that case, the devices on the Dell STACK are reachable without any problems too !
The problem exists on VLAN Interfaces on that switch too !
If I start a ping from that vlan interface to any device which is not connected to the Stack (for example the gateway or just google.de) the IP is also reachable remote... after stopping the ping the device isn't reachable anymore.
The problem exists only on vlans with low traffic on that switch. For Example vlan 100 has many clients like Notebooks and PCs and that is working well, also a configured VLAN Interface IP is reachable remotely. The VLAN 150 has only a few clients active on that switch and if I configure a vlan interface on that switch I do have the same issue.
DELL-Josh Cr
Moderator
•
9.5K Posts
0
April 18th, 2019 16:00
Hi,
Is the firmware up to date? If you private message me the service request or the service tag I can take a look.
Bias89
1 Rookie
•
20 Posts
0
April 19th, 2019 03:00
Hi,
yes, the firmware is the newest version for that switch.
We also updated the firmware on our Cisco Catalyst 4500e Core Switch to exclude that der is a problem between Dell & Cisco.
But without success.
Greetings
Tobias
Bias89
1 Rookie
•
20 Posts
0
May 10th, 2019 05:00
Hi,
actually the problem is not resolved... and I don't have any idea what I can do.
But I don't think it's a Radius problem. I think that the N Series and our Cisco Catalyst speak a different Rapid-PVST language and that cause the problems.
What I figured out:
The VLAN 150 has only a few clients active on that switch and if I configure a vlan interface on that switch I do have the same issue.
Maybe someone have any idea?
Tobias
Bias89
1 Rookie
•
20 Posts
0
May 10th, 2019 08:00
Hi,
I made a small overview about our network topology
RJCMpcr
2 Posts
0
October 13th, 2022 13:00
Hi Tobias.
Did you manage to solve this problem?
RJCMpcr
2 Posts
0
November 9th, 2022 10:00
Hi Tobias.
Did you manage to solve this problem?