The emergency code update has now completed and we are running a newer
version of code on m20-1.mpls.iphouse.net.
Part of the 'outage' when this router has gone down affecting other
items on the network could be from the core switch that the routers
connect through.
Some services are operating off of this switch in layer 3 mode
(think of this switch as both a switch and a router, layer 2 is
normal ethernet framing but not much smarter, layer 3 is actual
routing of packets based on IP addressing)
and when m20-1.mpls was rebooting, this switch was trying to route
traffic through the now defunct router. Of course, while the router
is rebooting, this switch is trying to route IP packets to the
rebooting router, which does *not* work. Until that router is back
online, it continues to fail in moving those packets to the upstream
routers. While this switch has been configured to use both of our
core routers as its upstream devices, for some reason, it is not
switching from one unit to the other.
Work will need to be done to move off the services operating on this
switch in layer 3 mode. Once completed, this switch will be a pure
layer 2 device, operating as a very high speed gigabit switch for our
routers to connect through for passing of traffic between themselves.
The other routers that connect to/through the switch itself are doing
full dynamic routing and are not affected in the same way when one of
the core routers reboots and are able to recover much quicker.
I am sorry this has been happening.
We will work internally to schedule the chnages required to help
remove this potential issue from the network once and for all.
Support can be reached Monday thru Friday from 8:00am until 8:00pm,
Saturdays from 11:00am until 4:00pm via phone at 612-337-6340, or via
email at [log in to unmask]
--
Mike Horwath [log in to unmask]
ipHouse - Welcome home!
