Powerconnect 6248 not routing with other vlan

[Buddha Anand]

Sponsored Links

I am having PC6248 running with 4 vlans. Routing is enabled globally on the switch and on the vlan interfaces. All ports are access ports.
vlan 2 ip 192.192.168.3.2 /24
vlan 3 ip 192.192.168.4.1 /24
vlan 4 ip 192.192.168.5.1 /24
vlan 5 ip 172.16.22.2 /24
All vlans are connected to each other and they are able to talk to each other. In vlan 5 I have connected too a router which is connected to a foreign network ip 172.16.33.0/24. I am unable to access the other vlan to the network 172.16.33.0/24 The PC6248 routes the client only residing in vlan 5. Any solution for this problem?

[ErikaGeek]

I had the same problem. I think that you should check for the statics to be visible as when I checked in my router it was disable.
For the static routes to be visible, you must:
• Enable ip routing globally.
• Enable ip routing for the interface.
• Confirm that the associated link is also up.

[TABLITA]

VLAN 5 is able to communicate because of the direct connection you have made with the static route. The static route is just for VLAN 5, and is not going to carry any other VLAN traffic across it. It will carry all the clients connected to VLAN 5. Any client connected to VLAN 2,3,4, sends out a request for the 172 network, and due to no Trunk or Static route set for these VLANs, you will not be able to access that network, because the VLAN does not know where to send the request. When the clients on VLAN 5 send a request for the 172 network, and if VLAN 5 doesn’t find it, then it then looks at its default route and sends the unknown traffic to that pre set route, which gets the connection you need. Connect the VLAN 2, 3, 4 to access the VLAN 5 network. You will be able to connect the clients of the VLAN 2, 3, 4 to access the foreign network.

[AmaF]

I think that the VLAN 2, 3, 4 are not able to communicate with the 172 network. You will have to setup a trunk link between the switch and VLAN 5. Set the trunk on the physical port connecting two devices. I fport 5 is physically connected to PC6248 then connect the other network devices by setting the other devices port to trunk mode and allow all the VLAN 2,3,4,5 across the link. Set all the other devices to the trunk mode. When you set the devices to trunk mode any client on VALN request to access a location and the PC6248 is not able to resolve it, then it will forward the packets across the trunk to other devices and that device will know where the request should go as it has the destinations of the location.

[Bhuvana21]

I had the same problem and I didn’t know the trunk mode and all. I don’t know much about the networking and especially regarding the settings of the network switches.If you do not want to do the Trunk, then you need to enter the Static routes for each of the VLANs. Once the static routes are set each VLAN will know where to forward unresolved requests and the client will be able to access the location where he wants to.

[AmaF]

After seeing the whole problem I think that I have found the problem it is not in the switch. The PC6248 is forwarding the destination address of 172.16.33.0 to its default gateway which is none other than the router, and the router is not able to forward the request to the right destination or location. The problem is that the ping requests went all the way to the destination or location but they couldn't find their way back giving ping timeouts or host unreachable. Add static routes to the router, all other vlans start to connect with the 33.0 network. As you mentioned your ip’s here are the ip route for you. Change it to this ip and you will be able to access the network.
ip route 192.168.3.0 255.255.255.0 172.16.22.2
ip route 192.168.4.0 255.255.255.0 172.16.22.2
ip route 192.168.5.0 255.255.255.0 172.16.22.2