Specifications
HighWire MTP-2 - 1.2, September 4, 2002 CBI Messages: Detailed Description 87
cong_level
cong_levelcong_level
cong_level
The current congestion level. For single congestion thresholds, 0 means Not
Congested, and 1 means Congested. For multiple congestion levels, this field
can take values 0 - num_cong_levels
num_cong_levels num_cong_levels
num_cong_levels (from M2_UPDATE_PARMS) inclusive.
Constants for the congestion level in use by L2. This field can take the
following values:
• CBI_M2_CONG_LEVEL_1
• CBI_M2_CONG_LEVEL_2
• CBI_M2_CONG_LEVEL_3
• CBI_M2_CONG_NONE
link_status
link_statuslink_status
link_status
The link status. This field can take the following values:
• CBI_M2_LINK_ALIGNED
• CBI_M2_LINK_ALIGNING
• CBI_M2_LINK_IN_SERVICE
• CBI_M2_LINK_OUT_OF_SERVICE
• CBI_M2_LINK_PROVING
ups
upsups
ups
This is the User Proving Status (proving mode requested by L3). This field can
take the following values:
•CBI_M2_UPS_NORMAL
• CBI_M2_UPS_EMERGENCY
lpo
lpolpo
lpo
The status of a Local Processor Outage. This field can take the following
values:
•CBI_M2_LPO_RECOVERED
• CBI_M2_LPO_OUTAGE
retrieval_pending
retrieval_pendingretrieval_pending
retrieval_pending
Message retrieval status. This indicates whether L2 has a pending Message
Retrieval request outstanding. If so, then L2 will send these messages to the
L3 process which issued the CBI_M2_MGMT_REGISTER signal. This field can
take the following values:
CBI_YES L2 has a pending retrieval request outstanding.
CBI_NO L2 does not have a pending retrieval request outstanding.










