Very Short Network Outage Early Monday, 9/1

Very brief planned outage required to activate a new version of the central router’s operating system. This is needed to correct a flaw that prevents use of a new component added in July 2003 that provides gigabit connectivity for various servers.

It is possible that no outage will be perceived. If there is an outage all network services would be affected (i.e. email, Internet, Novell, Blackboard, Sirsi/Sadie (Library), AS400, Calendar).

This outage moved us from IOS 7.6(1) to 7.6(3). This did not take care of the problem with the 6148 Gig blade. Cisco states there is a hardwaree/software flaw where packets are being dropped. There is no resolution for this as of now They will be sending us a 6516 blade to use as a loaner till this problem is resolved.

TOTAL NETWORK EMERGENCY DIAGNOSTIC OUTAGE

A key component of the central network router is not performing correctly. Info Systems will be taking the router down for at least an hour beginning at 6:30am, Wednesday, August 27.

SYSTEMS AFFECTED: IMPACT: ALL network services will be down.

NO email access (but no mail will be lost)
NO Internet access
NO access to Blackboard
NO access to the AS400 (administrative system)
NO access to Campus Web
NO access to the library system (Sadie)
NO access to the EMU web server

This is the FIRST of possibly TWO procedures to correct the problem. If this fails to correct the problem a new part will be ordered and an additional outage in the near future will be required to install the new part.

This notice will be updated with details as they become available. Check back for more details.

Swapped out the 6148 gig blade from slot 9 and installed into slot 8. Modified the config so the gig blade works in slot 8. Ran tests to verify connectivity using ping, telnet and www. Both showed latency. Called Cisco to reevaluate the case. Moved all Novell servers from the Gig blade back to the 10/100 blade.

FS server gig card added

Added the gig card driver to the FS server. The server had parameters set out of range. These were modified and the server rebooted. Yet after the reboot they were still the old values. Found these to be set in autoexec.ncf and startup.ncf. Removed them from those fiels and rebooted server. Again modified the values and now was able to install the driver. Changed the drivers bind parameters to be that of the old card. Old 10/100 card is still in server but the card is disabled in INETCFG. Checked connection and it is now at gig full duplex