The UNC at Chapel Hill Communications Network interconnects departmental local area networks on and off-campus. The UNC at Chapel Hill Network itself is then connected to NCREN (administered through MCNC in Research Triangle Park) and, through NCREN, to Internet backbone service providers. In addition, the campus network is part of the NCNI (North Carolina Network Initiative), which connects to Internet2.

The policies stated herein are directed to the managers of those hosts, workstations, switches/bridges, routers, servers, etc. that are capable of sending and receiving network packets.

Local departmental system administrators must realize that their local systems are just as much a part of the Internet as any other system in the world. What appears on a local ethernet can and may be transmitted across the country and may do damage along the way. When an offending node or network is identified, various Network/Systems Operations Centers (NOCs), including that of UNC at Chapel Hill's ITS organization, start a defined procedure to solve the problem. A wide range of procedures may be invoked aimed at working with the local network administrator to fix the problem. In no cases are problems ignored for longer than 15 minutes, usually sooner. Because we all must be responsible participants in the Internet, it is necessary that we develop and enforce policies and procedures in the operation of our network.

It is the responsibility of ITS Telecommunications to coordinate, monitor, and manage the UNC at Chapel Hill Communications Network traffic and activities. ITS must ensure that our campus facilities do not disrupt the statewide or national networks and that we maintain good connectivity to the network for all campus users.

Local departmental system administrators must be cooperative and responsive to our requests. When problems arise, we will advise and work with the local/departmental administrator. However, if the local administrator or their designated representative/alternate cannot be contacted in an appropriate amount of time, ITS will take whatever steps are necessary to restore the proper functioning of the UNC at Chapel Hill Communications Network for the majority of campus users. This will include disconnecting a department or building from the campus network if necessary. For this reason, and to ensure reliability, security and high performance, network electronics (switches and routers) connected to the campus backbone must be managed and maintained by ITS. In all cases, ITS will notify the local administrators of any actions that have been taken and will work with the local administrators to correct any problems.

Every department connected to the UNC at Chapel Hill Communications Network MUST have a designated system administrator who is registered with ITS. Furthermore, this administrator MUST have and use electronic mail. In those instances where a department chooses to contract with an outside vendor to provide local support and management, that outside vendor MUST be accessible via e-mail from the Internet.

The local administrator will be the person contacted when problems arise with that particular segment of the network. The administrator will be expected to respond with appropriate priority and act with appropriate authority. This person should be reachable during normal business hours. Departmental contact procedures for nights and weekends should be made availabe to the [ http://control-center.unc.edu/ ] ITS Control Center at 962-6503.

Any network device desiring Internet connectivity must have a registered IP address within the 152.2.0.0, 152.19.0.0 or 152.23.0.0 Class B Internet networks assigned to UNC at Chapel Hill. Subnet number ranges are assigned by ITS. Send requests for new assignments to <host-reg@unc.edu> or submit via [ https://www.unc.edu/ar-bin/websub/index.pl ] Remedy. ITS is prepared to provide whatever level of addressing is required to meet legitimate departmental needs. Please request subnet ranges of an appropriate size to meet anticipated growth as well as current need; however, departments are encouraged to use campus DHCP whenever possible.

Related to the issue of IP subnets is the role of routers in a campus network environment. Due to the increased complexity of routers over switches, and the impact that improperly configured IP routers can have on campus network access, any routers that need to deployed for either broadcast/multicast containment or security reasons that cannot be met by virtual LAN configurations must be authorized by ITS. Furthermore, due to the management issues of routing protocols and the problems that misconfigured routers can produce on a large network, in order to ensure compatibility and reliability, ITS must manage all routers on the UNC at Chapel Hill network.

Although IP subnets are assigned by ITS, individual IP addresses for departmental network devices are assigned within that department by the department's system administrator. However, assigned addresses and corresponding hostnames MUST be appropriately registered with ITS or with an appropriately configured departmental DNS (domain name server) that is recognized by ITS. Send host registration information to <host-reg@unc.edu>

Failure to appropriately register host names and addresses could result in those devices being blocked at the nearest network switch.

Data port activations for all locations other than the School of Medicine are done via the [ https://www.unc.edu/ar-bin/websub/index.pl ] Remedy System. Please be sure to include both the building and the data jack location in your request. Remedy tickets can be created online by submitting an online help request or by contacting the ITS Response Center at 962-HELP.

In order to ensure reliable, fair and consistent network services to the campus, ITS is charged with operating all mechanisms controlling the allocation of network resources, including access to the network, bandwidth available to users and applications, and bounded latency performance. ITS will operate all such mechanisms, including policy servers, bandwidth brokers, H.323 gatekeepers, and quality-of-service controllers, on behalf of the campus. Campus units and end users may not place these policy-controlling mechanisms on the network. All policy-based services, including QoS applications and H.323 terminal end stations, must be registered with ITS Networking via Remedy ticket.

Failure to appropriately register policy-based systems on the network will result in those devices being disconnected from the network.

To report problems with network operation or other abnormal network events, call the ITS Response Center at 962-HELP. Please be sure to give a description of the problem/emergency, including IP addresses of source and destination systems when appropriate, and the appropriate networking staff will be contacted immediately.

The UNC at Chapel Hill Communications Network supports [ http://www.unc.edu/policy/aupol.html ] use policies in accordance with its suppliers of Internet connectivity and will enforce those policies to the best of its ability. ITS supports those elements of Internet policy that demand network etiquette and due consideration for user's rights to privacy. In addition, the UNC at Chapel Hill Communications Network also endorses the policies and responsibilities for host and network managers contained in Internet RFC 1173; in particular, the policy that "Internet sites SHOULD NOT have 'general use' accounts, or 'open' (without password) terminal servers that can access the rest of the Internet."

[ http://help.unc.edu/?id=2163 ] Campus Wireless Networking Policy