In one office I worked in all the glass office and meeting room walls were white boards.
It was excellent for meetings and planning. It also meant that if anyone was out of their office they just had to write on the wall that they were out and what time they were expected back.
I work on a network where we deployed cisco 3550 layer 3 switches as routers to all our 2000+ sites. Each site only had a 2mb link, and they were all rate limited to ensure the router didn't try to go over that speed.
Part of the process for implementing each router was to configure, and test each unit before we sent shipped them to site. Bad thing about this was the way that did it left the default route out the WAN interface, and not to the next-hop IP.
Once blaster hit it took down more routers than I want to think about. We had CEF do the same thing as the parents GSRs. Also any new routers put on the network would die within 2 minutes of being connected to the network.
The only way to fix the problem was to go through all the sites, have the LAN disconnected from the router and then fix the default route to the next-hop IP and add ACLs to block all blaster related traffic.
We love CEF here, it introduces the MS fix to Cisco gear - a reboot will fix it!
Slashdot Mirror
In one office I worked in all the glass office and meeting room walls were white boards.
It was excellent for meetings and planning. It also meant that if anyone was out of their office they just had to write on the wall that they were out and what time they were expected back.
I work on a network where we deployed cisco 3550 layer 3 switches as routers to all our 2000+ sites. Each site only had a 2mb link, and they were all rate limited to ensure the router didn't try to go over that speed.
Part of the process for implementing each router was to configure, and test each unit before we sent shipped them to site. Bad thing about this was the way that did it left the default route out the WAN interface, and not to the next-hop IP.
Once blaster hit it took down more routers than I want to think about. We had CEF do the same thing as the parents GSRs. Also any new routers put on the network would die within 2 minutes of being connected to the network.
The only way to fix the problem was to go through all the sites, have the LAN disconnected from the router and then fix the default route to the next-hop IP and add ACLs to block all blaster related traffic.
We love CEF here, it introduces the MS fix to Cisco gear - a reboot will fix it!