Networking will be upgrading hardware in every building on the
Springfield Campus this summer. Users of static IP addresses, AppleTalk, and Novell's IPX may need to reboot or obtain new useable addresses from Networking.
AppleTalk zones should not change.
Please check back periodically for new outages.
Summer & Fall Semester, 2003
The Missouri State University Networking staff will be replacing older, slower networking hardware
all over the Springfield Campus with newer, faster equipment.
Some needed maintenance is also being scheduled. Much of this equipment
will position Missouri State University for the transition from 100Mb infrastructure circuits to
1000Mb (or 1Gb) circuits. Most buildings will also receive redundant
network feeds from multiple core sites. This redundancy will allow for
sub-second failover in the event of numerous types of network failures.
Obviously, not all failures can be circumvented automatically, but these updates
will increase the speed and reliability of the networks.
Please note, electrical power, telephone service, and email addresses are
not affected by this network outage. However, the computer data
networks, Zip Card devices, and Simplex Card Access systems will be down or
operating disconnected from the rest of campus or even within the same building.
See Phase I
below for more information. All areas have or will ultimately be affected,
but the current scheduled list is as follows:
Bldg.
Code |
Conversion
Time |
Outage
Duration |
New
Network |
Phase I
(Router) |
Phase II
(1GB link) |
Phase III
(Redundancy) |
| AC01 |
July 14
8:30 a.m. |
8 hours |
208/23 |
Complete
From NAPS |
Merged |
N/A |
| AC02 |
July 14
8:30 a.m. |
8 hours |
208/23 |
Complete
From NAPS |
Merged |
N/A |
| ALUM |
July 3
8:30 a.m. |
4 hours |
180/23 same |
Complete |
Pending |
Pending |
| ARTX |
June 19
3:30 p.m. |
90 min. |
86/24 |
Complete |
Complete |
Complete |
| BANK |
July 3
9:00 a.m. |
4 hours |
135/24 same |
Complete |
Pending |
Pending |
| BLAR |
July 30
8:30 a.m. |
8 hours |
192/23 |
Complete |
Pending |
Pending |
| BLSH |
July 30
8:30 a.m. |
4 hours |
139/24
192/23 |
Complete
From BLAR |
Pending |
Pending |
| BURG |
June 19
2:00 p.m. |
90 min. |
74/24 |
Complete |
Complete |
Pending |
| CARR |
June 13
1:00 p.m. |
4 hours |
92/23 same |
Complete |
Complete |
Pending |
| CHEK |
June 5
1:30 p.m. |
4 hours |
40/23 same
42/24
44/23 same |
Complete |
Complete |
Pending |
Bldg.
Code |
Conversion
Time |
Outage
Duration |
New
Network |
Phase I
(Router) |
Phase II
(1GB link) |
Phase III
(Redundancy) |
| CRAG |
|
|
|
On Hold |
On Hold |
On Hold |
| ELLS |
June 20
1:30 p.m. |
4 hours |
82/24 |
Complete |
Complete |
Complete |
| ELMA |
July 8
8:30 a.m. |
2 hours |
196/23
no change |
Postponed
From SUNV |
Merged |
N/A |
| FLRH |
March 25
8:00 a.m. |
1 hour |
136/23
no change |
Scheduled
From UNVH |
N/A |
N/A |
| FORA |
June 25
1:30 p.m. |
4 hours |
106/24 |
Complete |
Pending |
Pending |
| FRUH |
June 9
8:00 a.m. |
5 days |
200/23
202/23
148-9/24 |
Wiring
Partial |
Pending |
Pending |
| GLAB |
June 16
8:30 a.m. |
4 hours |
142/23 same |
Complete |
Pending |
Pending |
| GLAS |
July 22
1:30 p.m. |
4 hours |
116/23 same
120/23 same |
Complete |
Wiring |
Pending |
| HAMC |
June 17
8:00 a.m. |
4 hours |
126/24 |
Complete |
Complete |
Complete |
| HAMH |
June 10
4:30 p.m. |
2 days |
204/23
206/23
147/24 |
Complete |
Pending |
Pending |
Bldg.
Code |
Conversion
Time |
Outage
Duration |
New
Network |
Phase I
(Router) |
Phase II
(1GB link) |
Phase III
(Redundancy) |
| HHPA |
June 19
8:00 a.m. |
4 hours |
127/24 |
Complete |
Complete |
Complete |
| HILL |
Sept 5
1:30 p.m. |
1 hour |
80/23 same |
Partial |
Complete |
Complete |
| HOLB |
June 3
9:00 a.m. |
4 hours |
134/24 |
Complete
From ALUM |
N/A |
N/A |
| KAPT |
|
|
215/24 |
From KENT
Partial |
Merged |
N/A |
| KARL |
June 18
1:30 p.m. |
4 hours |
79/24 |
Complete |
Complete |
Complete |
| KEMP |
June 30
1:30 p.m. |
3 hours |
88/23 same |
Complete |
Complete |
Pending |
| KENT |
|
|
215/24 |
Complete |
Complete |
Complete |
| KGSX |
June 25
1:30 p.m. |
4 hours |
107/24 |
Complete |
Pending |
Pending |
| KIMB |
December 18
1:30 p.m. |
2 hours |
153/24 |
Complete
From PROF |
Pending |
N/A |
| LEVY |
July 3
9:00 a.m. |
4 hours |
135/24 |
Complete
From BANK |
Merged |
N/A |
Bldg.
Code |
Conversion
Time |
Outage
Duration |
New
Network |
Phase I
(Router) |
Phase II
(1GB link) |
Phase III
(Redundancy) |
| LIBR |
July 11
8:30 a.m. |
4 hours |
112/23 same
114/23 same |
Complete |
Complete |
Pending |
| MADH |
|
|
136/23 same |
From UNVH |
N/A |
N/A |
| MCCE |
June 24
8:30 a.m. |
4 hours |
124/23 |
Complete |
Complete |
Complete |
| MCDA |
June 12
8:00 a.m. |
4 hours
(no power) |
78/24 |
Complete |
Complete |
Pending |
| MONH |
March 25
8:00 a.m. |
1 hour |
136/23 same |
Scheduled
From UNVH |
N/A |
N/A |
| MORH |
July 1
5:00 p.m. |
4 hours |
70/24
71/24 |
Complete |
Pending |
Pending |
| NAPS |
July 14
8:30 a.m. |
8 hours |
208/23
210/23 |
Complete |
Pending |
Pending |
| PLAS |
August 15
8:30 a.m. |
4 hours |
76/24 |
Complete |
Complete |
Complete |
| PLSU |
June 27
8:30 a.m. |
4 hours |
144/23 same |
Complete |
Pending |
Pending |
| POST |
|
|
157/24 |
Wiring
From PROF |
Pending |
N/A |
Bldg.
Code |
Conversion
Time |
Outage
Duration |
New
Network |
Phase I
(Router) |
Phase II
(1GB link) |
Phase III
(Redundancy) |
| POWR |
|
|
92/23 same |
On Hold
From CARR |
N/A |
N/A |
| PROF |
June 13
8:00 a.m. |
4 hours |
150/23 |
Complete |
Complete |
Complete |
| PROJ |
|
|
152/24 |
N/A |
N/A |
N/A |
| PTPA |
June 26
8:30 a.m. |
4 hours |
128/24 |
Completed |
Complete |
Complete |
| PTPL |
|
|
50/24 same |
N/A |
N/A |
N/A |
| PUMM |
July 11
8:30 a.m. |
1 day |
64/24 |
Complete |
Complete |
Pending |
| SCHL |
July 2
8:30 a.m. |
7 hours |
214/24 |
Complete |
Pending |
Pending |
| SHAN |
July 18
10:00 a.m. |
4 hours |
194/23 |
Complete |
Pending |
Pending |
| SICL |
|
|
62/24 |
On Hold |
On Hold |
On Hold |
| STMA |
|
|
75/24 |
Complete |
Complete |
Pending |
Bldg.
Code |
Conversion
Time |
Outage
Duration |
New
Network |
Phase I
(Router) |
Phase II
(1GB link) |
Phase III
(Redundancy) |
| STRO |
July 10
1:30 p.m. |
4 hours |
100/23 same
104/23 same |
Complete |
Complete |
Pending |
| SUBS |
December 17
1:30 p.m. |
2 hours |
154/24 |
Complete
From PROF |
Complete |
N/A |
| SUNV |
July 8
8:30 a.m. |
8 hours |
196/23 |
Complete |
Pending |
Pending |
| TEMP |
July 1
1:30 p.m. |
|
96/23 same |
Complete |
Complete |
Pending |
| TROP |
December 17
3:00 p.m. |
|
155/24 |
Complete
From PROF |
Complete |
N/A |
| UNVH |
|
|
138/24 |
Complete |
Complete |
Complete |
| WEHR |
|
|
156/24 |
Complete
From PROF |
Complete |
N/A |
| WELL |
July 15
8:30 a.m. |
8 hours |
216/23
218/23 |
Complete |
Pending |
Pending |
| WOOD |
June 23
8:00 a.m. |
2 weeks
(no power) |
220/23
222/23 |
Complete |
Pending |
Pending |
Column and code meanings
Bldg. Code
|
The University standard 4-character
building code.
|
Conversion Time
|
The date and time the conversion will be or has been done.
|
Outage Duration
|
The estimated time network services will be down.
|
This is the maximum amount of time we expect the outage to last, even
if difficulties occur with the conversion. So far, we've not run
over! Strange and interesting things can happen such as a perfectly
good and working fiber optic connection turned off for a minute to move it
to the new electronics takes three hours to get back up again. This
actually happened to us once (so far), but most fiber links come right up
and most facilities are completed in far less time than indicated.
We do, however, reserve the whole time posted for those pesky issues that
one doesn't expect. Also, the larger the building, the more likely
we'll need more time... but not always. Residence Halls take much
longer because, unlike the other buildings on campus that already have
100Mb switched service, we have to replace all of the electronics in the
building and reconnect them to all of the user's jacks.
|
New Network
|
The new network number / bits in the network portion.
|
This indicates the new IP (Internet Protocol), Novell, and AppleTalk
network numbers for your network. The portion after the slash
indicates how many bits are used in the network portion of the 32 bit IP
address. Therefore, network 40/23 would mean your IP address would
be of the form 146.7.40.x or 146.7.41.x which appear, on the surface, to
be two different networks but are actually only one. The Novell
network would be 40 and the Appletalk "cable-range" would be 40-41. Network 42/24,
however, consists only of 146.7.42.x for IP, 42 for Novell, and 42 for Appletalk.
This process of renaming networks is necessary because networks
"originate" from the router that supports them. These routers are
being placed in most buildings instead of just core locations, therefore
changes have to be made. This is like renaming the street where you
live and expecting the postman to find you. See details outlined in
"Phase I" below.
"same" after the network number indicates that this is not a change
from the currently used network. We have kept network numbers the
same where we could to lessen the impact on our users and to lessen our
workload.
|
Phase Codes
|
The codes for all of the phases are: |
Complete
|
This phase of the work has been completed and no additional outages
are expected for this phase.
|
From XXXX
|
This feature is supplied from the building indicated by XXXX
by a 100% logical merging (no speed loss) or by a partial piggyback solution
(slower, but still fast). An outage will still occur for Phase I for
this building at the time building XXXX is scheduled to be down.
|
In Progress
|
The building is actively being upgraded.
This status is usually only used when the upgrade spans multiple days and can do so
because there is no electrical power in the building due to renovations.
We wear head lamps and literally change out the equipment and rewire in the
dark. When power is restored, we turn on all of the equipment and
verify that everything is working as designed.
|
Merged
|
The service indicated by the specific phase will be provided for the
building, but through another building. Logically this building is
100% merged with the other building indicated with no speed loss.
|
N/A
|
Not Applicable - the facility will not receive the
upgrade indicated by the specific phase.
|
On Hold
|
Upgrades are planned, but physical circumstances
prevent any progress towards our goals. The upgrade is therefore
on hold until the physical problems can be overcome.
|
Outage
|
Due to topology interdependencies, the facility
will experience a network outage as indicated, but it will not be upgraded
at that time. If "Phase I" is not "Complete" for this facility, it
will experience another outage in the future.
|
Partial
|
The work has been partially completed, but not yet
finished. An outage
will still occur for Phase I.
|
Pending
|
The work is planned, but not yet scheduled and an outage will occur
for Phase I.
|
Postponed
|
The work was planned on the date and time
indicated, but problems arose with the upgrade and it will be delayed.
The facility will still experience an outage at the indicated time if a
"From XXXX" building is also listed.
|
Proposed
|
A tentative time for the outage has been
selected. Once confirmed, the status will change to "Scheduled".
|
Scheduled
|
A time for the conversion has been scheduled
and confirmed. For Phase I, this will cause an outage at the specified
time.
|
Wiring
|
This flag indicates that the conversion is
waiting on a work order to be completed for some new wiring that we need
before we can start.
|
|
This phase will cause a network
outage!
|
This portion of the upgrade will, unfortunately, result in a service
outage for the affected facility. Only the computer networks that
carry data around campus will directly be affected. This means that
you can't send or receive email, print to network printers, browse the
internet, use peer-to-peer file sharing, and more.
Also, since Zip Card and Simplex Card Access systems rely on the data
network, they will also be down or operating in "stand alone" mode meaning
they have lost touch with the central controller for their function.
This means different things based on the device in question. For
information, please contact the Zip Card office at 6-8409 for time clock
and other Zip Card implications and Residence Life for implications for
the Simplex Card Access system used exclusively in residence halls.
Please note that addressing changes refer to TCP/IP, Novell's IPX,
and AppleTalk network protocol address changes. They have nothing to
do with email and your email address will not change due to these
upgrades.
During this phase, we will replace distribution equipment in the building
with new layer-3 switches. These have the speed of switches, but
perform the functions of routers. They are also capable of running at
gigabit speeds. Imagine the speed of I-44 to St. Louis being raised
from 100 mph to 1000 mph and you get a feel for gigaspeed. (Ok, it's
just an analogy!) Most, but not all, facilities receive this device, but
all distribution will be upgraded. These "1000 mph" links will
be used to provide up to two different paths into the facility as
indicated by the codes for Phase II and Phase III.
In addition, residence halls are
being upgraded from ten megabits, shared (a 10 mph speed limit on a
one-lane road) to one hundred megabits, switched
networking (a 100 mph speed limit on an Interstate highway). This will dramatically improve on-campus communications
for the halls. Residents will not, however, experience improvements
in Internet access due to this upgrade. Some buildings that already have this new equipment
will still experience a Phase I outage due to necessary large-scale
software changes.
Because routers are being installed all over campus, the campus networks
must be readdressed. This is kind of like renaming a street and having
to notify everyone of your new U.S. Postal address. Fortunately, the
network itself does most of the work for you. If your building is
being readdresses, when the time comes, simply shutdown your computer and
restart it. Almost all computer will then function on the new network.
The few users of "Special Addresses" must contact
Networking Services to receive a new
address before the device will function.
Printers normally must be cold-started twice before they will function
correctly. Often, User Support
must reset the print queue before the printer functions normally again.
If you encounter this, please contact User Support with the name of the
printer and the name of the print queue you are using. If you don't
have this information, they can assist you in collecting it.
|
Phase II
|
No outages should occur during this phase.
|
New single-mode
fiber optics are being installed to almost every building on the Springfield
Campus. Phase II will activate one gigabit link (that Interstate with
a 1000 mph speed limit discussed in Phase I) from one of three core
sites to the facility. This point to point routed link will
dynamically take over the traffic load and the old one hundred megabit link
will be removed.
|
Phase III
|
No outages are anticipated during this phase.
|
Most
facilities receiving the new fiber optics will also get redundant links back
to different core sites. During this phase, the second gigabit link
will be activated from the building to a different core site that was used
in phase II. This way, a core site can totally fail and the facility
will retain uninterrupted network services. Service will automatically
switch to avoid the failed equipment usually in less than a second!
Unfortunately, not all destinations are redundant, so email servers, web
pages, and even the Internet itself may not be accessible depending on the
exact location of the failure. However, the network will be more
reliable and much faster once this phase is completed.
|
Scheduling Outages
Almost everyone uses the networks for something in today's
world. So how do we arrange the outages and why do we do them during
normal business hours?
The last question comes down to time, money, and efficiency in
getting everyone working again. We are trying to get the upgrades
completed before the fall semester starts, we don't have the money to pay anyone
overtime to work after-hours, and we need the building occupants around to test
the new systems to verify that all workstations, servers, and printers function
before we leave the building. We have teams of people that walk around
each facility after it has been converted to be sure that all users are back up
and working. A day, or even an afternoon later, those people will actively
be converting another building and will be unavailable to assist users with
problems. Therefore, after we leave a building, users should contact the
Missouri State University Help Desk for assistance with problems.
We pick the time for the outage by calling every department head
and dean that we have listed as occupying that building. We specify when
we'd like to perform the conversion and then let them decide, within a few-day
period, which days would be less disruptive to all of the occupants. Once
a consensus is reached, email is sent out to every occupant of record indicating
what is being done and what they should due once the network comes back up.
We try to present information in non-technical terms, but feel free to contact
us if you have any questions at all.
Questions?
For more information on these upgrades, please contact
Mark Harsen in Networking Services. |