See also FSU's Networking Equipment Guidelines for Construction and Renovation Projects (pdf format)
...formulated by the Network Subcommittee,
Faculty Senate Computer and Information Resource Committee,
Florida State University
Approved July 1, 1993
|
| 1. Introduction |
|
The FSU Network (FSUNET) is a vital resource for the entire University community. Because FSUNET is a shared resource, all machines and users must cooperate to ensure network operation. This document provides guidance to network managers, departmental level administrators, and other technical personnel. FSUNET is based on Ethernet and FDDI technology and currently supports TCP/IP, DECnet, Appletalk and IPX-Novell protocols. Protocols approved by the Networking Committee will be added as needed. |
| 2. User Participation |
|
A campus networking committee meets monthly to discuss topics relating to networking on campus. This committee is composed of selected representatives from campus units that use FSUNET. All network users should participate in the development of policies and procedures associated with network operations. All users are encouraged to attend these meetings which will be announced in the local FSU news group fsu.network. Time critical broadcasts should be sent to nolenet@lists.fsu.edu, which is a mail group of network managers, departmental level administrators, and technical personnel. You can subscribe to nolenet at: https://lists.fsu.edu/mailman/listinfo/nolenet |
|
The committee may also create study groups to make recommendations on issues of campus wide interest, such as LANs and equipment needed for connection to Ethernet and FDDI networks. |
| 3. Connection Procedures |
|
The primary point of contact for obtaining a network connection is the Office of Telecommunications. Departments are *strongly urged* to consult with OTC before making any network equipment or media purchases, regardless of network size, since their eventual connection to FSUNET is likely, and all protocols and media may not be supported.
UCS will gather necessary information and forms required for access to FSUNET. This information might include network addresses, hardware and software characteristics, location, contact persons and phone numbers. UCS will maintain this database and make it available as a public resource. |
|
UCS will coordinate with other service providers (e.g. Administrative OTC, Office of Telecommunications) or departments as needed. |
| 4. Access to Premises Wiring Rooms |
|
The Telecommunications Infra-structure Specification document approved by the campus networking committee called for adjacent telephone and data wiring rooms in new and remodeled buildings. Where it is not possible to provide this, free and unrestricted access to the common premises wiring rooms shall be given to responsible individuals from organizational units that have need for such access. The campus networking committee shall be the arbiter of such need. |
| 5. Requirements |
|
A campus network requires the cooperation of the users to operate smoothly.
The user/network manager will supply details for each system and request network node numbers from UCS for all protocols used before activating the system on the network. |
|
The user/network manager will notify the University networking community before any router, including any Novell NetWare server, is connected to FSUNET. Notification should be made to nolenet@lists.fsu.edu. |
|
When installing untested network software or non-standard configurations, it is the responsibility of the user/network Manager to inform the FSUNET community before the software/device is made active. It is also advisable, that before installing any unfamiliar hardware or software that the user/network manager consult with OTC Networking and/or User Services and other knowledgeable members of the FSUNET community. |
|
The user/network manager will employ only those numbers assigned by the coordinator.
OTC Networking, in cooperation with departmental units, is responsible for the operation of FSUNET. A unit (or group of units) that seriously interferes with the operation of FSUNET may be disconnected to allow continued operation of the remaining portion of the network. |
| 6. Problem Reporting |
|
Problem Reporting Please report any problems related to FSUNET to the OTC Help Desk at 644-HELP (4357). |
| 7. Future Directions |
|
FSUNET is not static; it is a growing and changing entity. The current configuration will not meet increased demands. Since applications in the future will be more bandwidth intensive, higher speed connections such as ATM, SONET and other gigabit technologies will be deployed. The network must move towards an entirely routed environment to conserve bandwidth and increase reliability. Network managers must be aware of these directions when planning for departmental networks. |
