cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
334
Views
1
Helpful
2
Replies

4507 windows 2000 server routing problems

todh
Level 1
Level 1

We have a catalyst 4507 L3 switch at the core of the network. Attached to VLAN 1 is a Watchguard FW, various users, and a handful of servers. VLAN 1 is 192.168.2.24 and the FW is 192.168.2.254. 90% of the devices point to the VLAN 1 interface as their D.G. and that directs them to 192.168.2.254 if they want to go to the Internet. This works fine for everything except 2 windows servers running 2000 server, sp4. When their D.G. points to the 4507 VLAN 1 interface, they see a 50% packet loss when going to the internet. LAN traffic (local and to the other VLANs) is fine. If we change the D.G to point to the FW or even an old bay router (192.168.2.1) they work fine. I cannot figure this out. No changes were made to the switch. It could be an issue with a hotfix on the server, but I cannot find anything on this. I was wondering if this is a possible issue with route-cache on that interface? I have run this scenario before and never had problems like this. Thanks.

2 Replies 2

thomas.chen
Level 6
Level 6

The performance of any application is dependent on how much it gets or experiences in the way of bandwidth, delay, jitter and packet loss. Therefore, in QoS, the goal is to manage each of these conditions and proactively allocate them to each application (or session) based on its priority. The priority, of course, will be based on the application's importance to the company's business. Presumably, a mission-critical application is more important than Web surfing, and therefore must be allocated higher priority, just as VoIP traffic must be guaranteed bandwidth because a voice connection can be annoyingly poor or even completely incomprehensible if it is subjected to too much delay, jitter, or packet loss

todh
Level 1
Level 1

I found the problem. There is an issue with several versions of IOS and the 4507 with ICMP redirects. It is fixed by upgrading code or by using the command "no ip redirect" on the interface.