363-206-285
Maintenance Description
9-8 Issue 3 June 2001
â– Know the alarm/status of all members of the same Alarm Group and, if the
NE is at the CO, activate the audible office alarms for the Alarm Group.
â– List a report of the alarm or status condition of other NEs in the group.
■Display composites of other members’ user panel information.
â– Send/Receive ACO requests to and from members of the same Alarm
Group or same Level 1 area.
â– Send/Receive miscellaneous discrete alarm/status closure states to and
from alarm group members at a CO.
Each Level 1 Area will be mapped to an Alarm Group with a designated Alarm
Gateway Network Element (AGNE). The maximum number of NEs in an Alarm
Group is 50. The position of an NE in a subnetwork determines whether an NE
should be defined as AGNE.
For performance considerations, an NE defined as AGNE should not be defined
as GNE.
If a Network Element cannot establish communication with the Alarm Gateway
NE, or the AGNE cannot establish communication with a Network Element in the
same Alarm Group, the alarm message "AGNE communication failure" will be
created. Alarm Groups without an AGNE have "AGNE communication failure"
alarms.
An NE is provisioned to be and AGNE through the CIT
set-ne
or equivalent TL1
ENT-SYS
command. The AGNE broadcasts NE status information to members of
its Alarm Group. Considerations for choosing an NE as AGNE include being
central to the group to minimize communications links and being easily accessible
for maintenance purposes. A backup AGNE can be provisioned to "shadow" the
primary AGNE by sending duplicate status reports to members of the group. The
disadvantage of a backup AGNE is in the cost associated with increased
message traffic within the same Alarm Group.
To Next Page
Loading...
Need help?
General
