Unsolved
This post is more than 5 years old
7 Posts
0
7840
April 10th, 2008 13:00
Routing issue with a PowerConnect 6248
Hi there board,
We have recently purchased a Dell 6248 switch to replace an aged 3Com 4900 layer 3 switch.
This switch is intented to route traffic between the diffent sub-nets we have.
I have manages to solve routing issues up to a point that traffic is routed between te different sub-nets/VLANs we have. Only problem remaining is that a workstation in one of the sub-nets can no longer reach a switch which has an IP in the default vlan.
This is not a problem for the the 6248 itself since it can be reached trough one of the IPs assigned to its VLANs, but it does make other switches who have IPs in the same subnet as the 6248 invisible.
Here is what I have done and tested:
I assigned the switch an IP: 10.0.0.5 /16 (no gateway)
I created some VLANs: 2 and 4 for testing purposes
I assigned IPs to the VLANs: 10.2.0.1/16 for VLAN 2 and 10.4.0.1/16 for VLAN 4
I placed an uplink port to another swich in general mode and added the VLANs 1, 2 and 4 tagged
I enabled global routing.
On the switch itself I can now ping all IPs: 10.0.0.5, 10.2.0.1 and 10.4.0.1
I can even ping the other switch on its IP 10.0.9.41 (same subnet as the 6248)
After I place a port in access mode, vlan 2, and connect a workstation to it with IP 10.2.0.6 I can even ping that address from the switch
From the workstation I can ping 10.2.0.1. I can even ping outside its sub-net to 10.4.0.1. But I cannot ping 10.0.0.5 (the 6248) nor can I ping 10.0.9.41 (the connected switch)
Pinging 10.0.0.5 results in time outs
Pinging 10.0.9.41 result in a reply from 10.2.0.1 that that network cannot be reached.
I fail to understand te reason for this.
Since the 6248 itself should function as a gateway (at least for this test) I did not give it a default gateway. For testing purposed I did give it a gw: 10.0.0.5. But without result
Summing the routes gives me 2 locally connected networks for VLANs 2 and 4. There is no route for VLAN 1
My local Dell guru could not resolf this issue.... his knowledge does not go beyond layer 2 capabilities... and I am currently waiting to be contacted by a third party contracter to enlighten me.
Hope you guys can help me resolve this issue... it has been bugging me for some time now.
If you need detail.... session transcipts or such... do not hesitate to as... only problem is that I cannot reach my laptop connected to that switch atm ;)
regards
Peter


Peter Kaagman
7 Posts
0
April 11th, 2008 18:00
Not able to route the management VLAN.... that is a drag :( But I presume it does add some security.
I think I wil put my workstation on a port which has both the "normal" and the management VLAN. That way it wil be able to reach both the other subnets as wel as the management VLAN.
BTW.... here is my config... not that it wil do me any good I presume...
!Current Configuration:
!System Description "Dell 48 Port Gigabit Ethernet, 2.0.0.12, VxWorks5.5.1"
!System Software Version 2.0.0.12
!
configure
vlan database
vlan 2,4-6,8-9,21,41,51,61,81,91,100
exit
stack
member 1 2
exit
ip address 10.0.0.5 255.255.0.0
ip routing
interface vlan 2
routing
ip address 10.2.0.1 255.255.0.0
exit
interface vlan 4
routing
ip address 10.4.0.1 255.255.0.0
exit
username "admin" password 16b3518c9ac8ebb1987345cb62982a2a level 15 encrypted
!
interface ethernet 1/g1
switchport access vlan 2
exit
!
interface ethernet 1/g43
channel-group 2 mode on
exit
!
interface ethernet 1/g44
channel-group 2 mode on
exit
!
interface port-channel 2
switchport mode general
no switchport general acceptable-frame-type tagged-only
switchport general allowed vlan add 2,4-6,8-9,21,41,51,61,81,91,100 tagged
switchport general allowed vlan add 1 tagged
exit
exit
bh1633
909 Posts
0
April 11th, 2008 18:00
Please post your configuration file.
On the 62xx switches, the management vlan can not be routed. This means that the management interface vlan can only be reached on the management vlan.
The routing interfaces can be routed (of course), and the switch can be managed via the routing interfaces.
So, I think what you need to do, is change your management vlan to 4095 or another vlan that has no member ports, and then assign the ip addess 10.0.0.5 to the vlan interface and enable routing on that vlan interface.
Once you post the config, we can tell you exactly what to do.