>Plus routing of packets is done more quickly when done at the Switch level >rather than having to go through the router for every packet. What's wrong with "going through the router," and how does routing through a switch differ from routing through a router? Under what circumstances does going through a router, in an appropriate forwarding path, cause problems? Hint: the GSR is called the Gigabit Switch Router for marketing reasons of "switch good, router bad." Making forwarding decisions on layer 3 information is routing. Period. There are more and less hardware intensive ways to make routing decisions. But the actual lookup time is rarely a limiting factor. _________________________________ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
- But isn't that the routers job??? jenny . mcleod
- RE: But isn't that the routers job??? [EMAIL PROTECTED]
- RE: But isn't that the routers job??? Timothy Metz
- RE: But isn't that the routers job??? Brian Lodwick
- RE: But isn't that the routers job??? Brian Lodwick
- RE: But isn't that the routers job??? Howard C. Berkowitz
- Re: But isn't that the routers job??? Flem
- Re: But isn't that the routers job??? NeoLink2000
- RE: But isn't that the routers job??? Bolton, Travis
- Re: But isn't that the routers job??? Howard C. Berkowitz
- Re: But isn't that the routers job??? Guy Tal
- Re: But isn't that the routers job??? Howard C. Berkowitz
- Multiple Central Site Routers Tim Lovelace
- Re: But isn't that the routers job?... Guy Tal
- Re: But isn't that the routers... Howard C. Berkowitz
- RE: But isn't that the routers job??? Peter Van Oene
- RE: But isn't that the routers job??? Priscilla Oppenheimer
- RE: But isn't that the routers job??? Howard C. Berkowitz
- RE: But isn't that the routers job??? Erick B.

