Network Problems on FASnet Related to Campus Network

FASnet is based in the Applied Sciences Building (ASB), but has been extended to include locations in TASC1, the MTF, the Link, and Math/Stats. FASnet within the ASB is controlled and managed by the Faculty of Applied Sciences Network Support Group (FAS NSG). However, the extensions of FASnet into other buildings goes through campus equipment not under NSG control. This means that when the campus network has problems, the FASnet extensions, unfortunately, will also be impacted.

How can one tell if a FASnet network problem originates within NSG equipment or within campus equipment? What we do is monitor data transfers from one of our servers in the ASB to other selected machines on FASnet within the ASB and within TASC1, the MTF, the Link, and Math/Stats. When there is a serious degradation of performance that shows up between all the buildings but not within the ASB, then the evidence points to problems on the campus network.

Our live network monitoring data is on a secure password-protected site. However, when there are events of significance, I save the data to an unprotected location for general viewing. Here are the links to it:

Why should campus network problems affect FASnet? That's a good question. Most of the FASnet extensions into the Link, the MTF, and Math/Stats are carried by VLAN on the same physical fiber that carries general campus network traffic. Thus, if the campus network is overloaded, then the VLAN is also affected. TASC1 is an exception, in that FASnet traffic is carried on a separate fiber connection from ASB. However, this fibre is not direct, but instead takes the scenic route through a campus switch in Strand Hall. Thus, if the switch in Strand Hall is overloaded, then the connection to TASC1 is impacted.

We hope that steps can be taken to insulate FASnet from campus network problems. OTS has assured us that they are working on it.


Created December 2005 by John Hebron,   NSG,   FAS,   SFU.
Last modified 22 December 2005.