Welcome to CENIC






[NOC: Network Maps]
[NOC: Management Tools]
[NOC: Common Customer Requests]
[NOC: Frequently Asked Questions]
[General Questions]
[BGP Routing Protocol]
[NOC: Network Policies]
[NOC: Customer Survey]
[Sign Up for CENIC Today]


[RSS Feed]

dc-tac [info]

ops-announce [info]

ops-problem-detail [info]



[Network Operations Center] [CalREN Video Services] [Board Member Login]

[NOC: CalREN Backbone FAQs]

CalREN Backbone FAQs: General Information


Network Management

CENIC employs many automated network management tools to assist our Associates in the planning and management of their own networks, including Intermapper, Rancid, RT, and Cricket.


DC Router Naming Conventions

Function

Name

Example

Model

Notes

Core routing site-CORE or site-CORE{1,2} RIV-CORE Cisco CRS-1 Backbone circuits only, no customer-facing connections
High-speed aggregation site-AGG{1,2} FRG-AGG1 Cisco GSR
Low-speed aggregation site-AGG3 OAK-AGG3 Cisco 7200 T-1, some T-3 circuits
ISP transit site-ISP or site-ISP{1,2,...} SVL-ISP Cisco GSR ISP transit links and dedicated transit waves
Peering site-PX or site-PX{1,2,.} LAX-PX1 Cisco GSR older documentation referred to these as -PEER

Interface Description Conventions

In the following syntax:

	[remote-device | TID | "EGM"]
	

is used to denote that one of the above is used as the first term:

	remote-device
	TID
	EGM
	

Note that [ ] are used to group options for terms while | is used to indicate options. These symbols are not used in the actual descriptions that we apply to the equipment.


General Conventions

Device names are in lower case. Campus names are in mised case or upper case as appropriate. Only certain characters are permitted: alphanmeric, /, -


Campus-Facing

 [remote-device | TID | "EGM"] [Int | 15808-Int | CID] [Campus] [DF | EGM] [ISP | DC | HPR | DC/ISP]
	

Backbone-Facing

 [remote-device | TID | "EGM"] [Int | 15808-Int | CID] [layer-3 Device] [layer-3 Int]
	

Subinterfaces

For interfaces with subinterfaces, the information is split. The layer-2 information is listed on the main interface:

 [remote-device | TID | "EGM"] [Int | 15808-Int | CID]
	

Repeat the layer-2 information, and provide the remaining information in the subinterface:

Campus:

 [remote-device | TID | "EGM"] [Int | 15808-Int | CID] [Campus] [DF | EGM] [ISP | DC | HPR | DC/ISP]
	

Backbone:

 [remote-device | TID | "EGM"] [Int | 15808-Int | CID] [layer-3 Device] [layer-3 Int]
	

Expansion of Terms

Device DNS name: short DNS name:
e.g.: lax-15540-1

TID: 15808 TID
e.g.: LAXPL03

Int: interface:
e.g.: Gi1/1/0

15808-Int: rack/subrack/slot-[TT|BT] channel:
e.g.: 1/1/2-TT56

CID: last 4 digits of the EGM circuit ID

Campus: short name of campus:
e.g.: UCLA, San Diego CC, San Diego COE

Layer-2-device: backbone router at layer 3:
e.g.: svl-dc1

Layer-3-int: interface of remote layer-3 devices:
e.g.: Po1/0

Interface descriptions are revealed in many places:

  • sh ing description
  • Intermapper maps
  • Tools such as Cricket and Ciscoworks
  • Other SNMP tools, including end-user SNMP tools

Policy

Circuit IDs are sensitive information. Therefore, CENIC does not include them in terface descriptions, as they may be unintentionally revealed if they are available in description fields.








  CENIC Mailing Lists • webmaster@cenic.org Copyright 2006 © CENIC. All rights reserved.