On Thu, May 13, 2010 at 3:42 PM, [email protected] <[email protected]> wrote: > The question is, which of the two methods would you use? Putting the > Fiber WAN link on it's own network or, not?
I would definitely assign a different IP subnet for the fiber network, and use routing between all sites. There's all sorts of reasons to do this. Minimize broadcast traffic. Minimize change vs your existing config. Diagnostics. Possibility of access control in the future. Makes it easy to change back to providers/technologies that don't give you an Ethernet interface. Etc. > Since my HP switches at the main/remote sites are able > to do IP Routing, would you also remove the routers ... and do all routing > at the switch level? That depends on the amount of traffic and the capabilities of the switches in question. The routing functionality in many switches is very limited, both in terms of features and performance. I don't know enough about HP's layer 3 stuff to comment on that. Just know that not all routers are created equal. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
