Vlan and ip default-gateway vs ip route

Unanswered Question
Feb 1st, 2007

i have 2 3560's. one is setup as the vtp server and the other is a client. the one that is setup as the server has ip routing enabled and point it's last resort gateway to my firewall. the vtp cleint when set to no ip routing, has a default-gateway set to the ip of the vtp server. however, when i do this, i begin to have internet connectivity issues. when the client is set ip routing, and ip route x.x.x.x, then internet connectivity is fine. currently, everything is running on vlan 1. i am working on getting everything ready to move everything onto vlans.

Thanks in advance for help!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
sundar.palaniappan Thu, 02/01/2007 - 13:35

IP default-gateway only affects traffic originated to/from the switch itself and it doesn't affect traffic that's passing through the switch. It's OK to leave routing turned off on the switch that's acting as VTP client but in this case, all the hosts connected to this switch would have to use VTP server's IP as their default gateway.



scott.hawks Thu, 02/01/2007 - 13:43

once i get everything moved over to my vlan's, then i will need to change the gateway on the pc's to the vlan ip, correct?

sundar.palaniappan Thu, 02/01/2007 - 13:54

If all the users connected to the switch configured as vtp client are on vlan 1 then the PCs connected to that switch would use vlan 1 interface IP of the vtp server switch as their gateway. Instead, if the switchports on the vtp client switch are assigned to different vlans then the PCs would have to be configured with a default gateway address of the respective vlan int IPs. I am sure you are aware that you need to trunk the connection between the two switches if switchports on the client switch exist in more than one vlan.



scott.hawks Thu, 02/01/2007 - 14:02

Yes, i already have the ports connecting the 2 vlans trunked with dot1q. while i have someone so knowledgable, let me pick you about a connection problem i have. one of my users when he starts his computer it takes literally 3 minutes to logon. no other users have this problem. i have checked the cabling. i have also set the port he is on to spanning-tree portfast. anything else i need to look for. there didn't appear to be any errors on the interface.


sundar.palaniappan Thu, 02/01/2007 - 14:08

If it's just one user then it very likely is a issue with that users PC. From the network standpoint, duplex/speed, portfast are some of the things that could cause this behavior but if you already checked all that then network mayn't be contributing to that delay. Try moving the user to another known working port and if the problem follows that's one way to eliminate network being the issue here.




This Discussion