Telecommunication Room guidelines and audit response

Project objectives

Implement policies and processes to ensure network diagrams are updated to reflect the actual state of the network whenever changes occur, including periodic review to ensure these diagrams remain accurate.

  • It is not possible to enforce any of the following, however, hopefully it will be followed with buy-in from support groups.
  • It is not feasible to review whether or not the procedures are being followed. It would most likely require a FTE to solely audit over 500 TRs on a continuous basis.
  • The objectives could be possible and maintainable if access to TRs was restricted to Information Systems & Technology (IST) only and possibly Engineering Computing (for cabling purposes only).

Create baseline of:

  1. Core Network
  2. Wireless Network
  3. Computer Room Network
  4. Building Network

[1-4] are located on smb://$/ISTNS/Network Diagrams/ (will likely need to move to provide campus access).

[4] Contains detailed drawings of all TRs as of December 2012. In the guture, they may be a 'generic' drawing of a typical building. ONAs mapping tool and LLDP neighbours will be used for additional detailed connections. As a general principle, building routers will be connected to both dist-rt-mc and dist-rt-phy. From there a direct connection to each switch exists. Switches will be named following the campus naming convention indicating the building and room number that the switch is in as described at Network device naming standards.

Photos of TRs are located at smb://$/ISTNS/TR-photos/.

Create signage to be installed in all TRs


  • Meet with staff and managers to review terms and conditions of TR access.
  • Remove unneeded access to TRs.
  • Review the number of staff with physical and logical access to network equipment, and restrict to those who need access on an ongoing basis.
  • Ensure those who retain access are aware of the conditions and terms of access.

    A short presentation will be made at CTSC.

    All groups will be emailed a link to the TR documentation for commenting/clarification. Offers will be extended to meet to discuss any concerns and changes will be made accordingly.

    A request to all groups to provide a list of people with access to the TRs will be sent and compared to IST's list. Discussion will occur on the necessity of the access.

    Create guidelines outlining parties access and responsibilities while operating in a TR

    See patching guidelines

    Review possibility of patch cable documentation and document process if so.

    A web based/online Cabling Database is being created in conjunction with the fibre database. Database will be searchable and will include Room, patch panel and switchport information. The possibility of linking it to ONA will be examined.

    Database will be planned and started, but won't be completed [data populated] during this project. It will rely on existing cabling information and does not include verification of this data.

    Is it feasible for IST to complete all patching and what turnaround time

    Possibly, provided turnaround was less than an hour for simple patching.

    Chemical Engineering indicates they mostly require patching only at beginning of terms.

    It would require an IST staff member whose main priority was this and could leave all other duties to do so in order to have buy-in and provide fast turnaround times.

    It is recommended that this be the responsibility of a helpdesk/front line support and be part of basic service provisioning. SLA's will need to be defined and monitored to ensure adequate support is being maintained.


    IST is investigating the possibility for IST to perform and maintain all patching and configuration, including documentation within TRs. In order to meet this recommendation however, SLAs will need to be designed to ensure client needs are met in a timely manner (proposed 1hr turnaround). In order for this to be successful it would need to be understood that access to TRs would not be available and/or access that does exist does not permit changes to patch cables or connections. Additionally, it is recommended that patching and VLAN configuration be a 1st level support incident in conjunction with basic service provisioning. This will require additional training and access to the helpdesk, but would provide increased turnaround and client satisfaction. Alternatively, an additional staff member may be required by Network Services to perform this task (and other duties where fit).

    The amount of work should be minimal with the implementation of the Patch Cable Database allowing the majority of work being travelling to the TR and physically patching the cable.

    For additional information, please see: