363-206-285
Administration and Provisioning
8-76 Issue 3 June 2001
Identifiers 8
The following IDs are used for the shelf, target, CO/RT, NSAP address, GNE and
AGNE (for R15.0). See also the
Lucent Technologies 2000 Product Family Multi-
Vendor Operations Interworking Guide
, 824-102-144 and the
DDM-2000
Operations Systems Engineering Guide
, 824-102-151.
■ Shelf ID: The shelf ID is a parameter with values of from 1 to 8. The shelf
ID provides a convenient way to log into a selected shelf in a bay using the
CIT. Therefore, each shelf (OC-3 or OC-12) in a bay must be assigned a
unique shelf ID. The recommended numbering is to start at the bottom of
the bay and assign the bottom shelf with a shelf ID of 1 and work up to the
top of the bay.
■ TID: The TID is a 20-character parameter that is set through the CIT using
the set-ne command. The TID is used in the rlgn command to identify
an NE to which a CIT remote login session is being established. The TID is
also used by OSs to identify NEs using the TL1 message-based
communications protocol.
After the init-sys:all command is entered, the system sets the TID to
a default value of LT-DDM-2000. The TID must be unique among all NEs.
The default TID may be changed using the set-ne command to a unique
user-assigned value recognized by the OS.
■ CO/RT: The CO/RT parameter for CO or RT identifies the system as
having the characteristics of a CO or RT. The default is RT. The parameter
controls the operation of the miscellaneous discretes and the external fan
control.
■ NSAP: The NSAP is a multiple part address that uniquely identifies each
NE. The NSAP is used for subnetwork DCC communications using the OSI
protocol. The NSAP is set to unique values assigned to control hardware at
the factory and does not have to be modified by the user unless
subnetwork partitioning is necessary. Subnetwork partitioning is
accomplished by assigning NEs to different areas. An NE’s area address is
one of the subfields within its NSAP. The ent-ulsdcc-l3 command is
used to modify an NE’s NSAP.
■ GNE: An NE that has an active TL1/X.25 link to an OS is automatically an
GNE. Subnetworks can have multiple GNEs.
■ AGNE: In an alarm group, an NE must be designed as a AGNE by setting
its AGNE parameter to “yes” using the set-ne command. An AGNE is an
NE alarm group, through which members of an alarm group exchange
alarm and status information. By default, all NEs are in the same alarm
goup (255). For subnetworks having more than 16 NEs, the AGNE and
GNE should be separate NEs. The AGNE is a “collection point” and does
not have to be an NE in a CO, for example.
To Next Page
Loading...
Need help?
General
