I am trying to replace a old DLink switch with a PC 6224. I have configured 6 VLan’s, 68,69,70,71,210,206. The 210 & 206 (I know, it’s a public IP range. We use NAT and it isn’t an issue right now) will be removed shortly, but my first goal is getting this switch working. I am basically trying to mirror the config of the old switch for now, then I will tweak once it’s working.
I configured the switch off line with 2 laptops. Everything appeared to be working so I plugged it in today and swung over hubs and servers on to it. Everything on the LAN seems to be working, I can ping, tracert follows the expected paths, grab IP from DHCP server, etc. But I am unable to access the internet.
Our firewall sits on the 210 VLAN, it’s ip is 10.1.210.1. So I add a default route to point to the firewall. I can ping Google now, but 90% of the packets time out.
After an hour of troubleshooting and changes, I decide to remove the default route pointing to the firewall and change it to another router on the other side of the building. Its default route is pointing to the firewall and has other routes pointing to the VLAN IP Interfaces. It works, but it is slow. This makes no sense to me and I finally gave up after 6 hours and put the old switch back in.
Sorry for the long story. Below is my running config of the 6224. Can anyone see anything that may cause this? Any other hints?
Thanks!
!Current Configuration:
!System Description "Dell PowerConnect"
!System Software Version 1.0.0.27
!
configure
gvrp enable
vlan database
vlan 68-71,206,210
exit
stack
member 1 1
exit
ip address 192.168.70.254 255.255.255.0
interface vlan 68
name "10 244 68 x"
routing
ip address 10.244.68.4 255.255.255.0
ip local-proxy-arp
exit
interface vlan 69
name "10 244 69 x"
--More-- or (q)uit
routing
ip address 10.244.69.1 255.255.255.0
ip local-proxy-arp
exit
interface vlan 70
name "10 244 70 x"
routing
ip address 10.244.70.1 255.255.255.0
ip local-proxy-arp
exit
interface vlan 71
name "10 244 71 x"
routing
ip address 10.244.71.1 255.255.255.0
ip local-proxy-arp
exit
interface vlan 206
name "206 152 208 x"
routing
ip address 206.152.208.7 255.255.255.0
ip local-proxy-arp
I had a similar experience. What resolved my issue was that I had to create static routes on my firewall that points to the different vlan subnets. I created a route for each network and used the gateway of the vlan that my firewall sat on.
Well just an update. After putting back the orginial switch i found a Printer with a Static IP was plugged into the wrong VLAN port. It was causing our internal network to CRAWL and very sporadic ping responses. Would a PC plugged into a wrong subnet casue this much disruption?
Try adding a route on your firewall pointing 10.1.210.4 to your firewall's external interace ip address. This would be a "host to host" route instead of a network route.
nlspears
52 Posts
305
0
Posted April 15th, 2007 03:00