status bri-port

Last Updated : Dec 09, 2021 |
Use status bri-port to see the service state, maintenance state, and layer 1 state of an ISDN-BRI port. There is also information about the point-to-point signaling links carried over the port. For more information, see the 'BRI-PORT (ISDN-BRI Port)' section in the Maintenance Alarms for Avaya Aura® Communication Manager, Branch Gateways Servers.
Prolog information
Metadata
Keywords:

Syntax

status bri-port  location  
location
Location of the BRI port

status bri-port field descriptions

Field
Description
Port
The location of the ISDN-BRI port.
Service State
Whether the ISDN-BRI port is in-service or out-of-service.
Maintenance Busy
Whether maintenance testing is currently being performed on the port.
Layer 1 State
The operational state of the physical connection (Layer 1) of the ISDN link carried over the port:
  • activated — Layer 1 frames are being passed between the port and BRI endpoints
  • pend-activation — The port is in service, the layer 1 interface device is turned on and layer 1 frames are being sent from the port, but the BRI endpoints are not responding
  • deactivated — The layer 1 interface device on the BRI has been turned off due to the port being out of service.
TEI Value
The Terminal Endpoint Identifier (TEI) is a layer 2 addressing parameter used by the switch to exchange information with BRI endpoints over the point-to-point signaling link. The TEI is a number from 1 to 127.
The operational state of the point-to-point signaling link (Layer 2):
  • assigned — The link is currently in the AWAIT_EST (Await Establish) state at layer 2. If the BRI endpoint supports TEI allocation procedures, those procedures have been successfully executed and a TEI has been assigned to the endpoint by the switch.
  • established — The link is in the MF_EST_NORM (Multi-Frame Established Normal) state at layer 2. The switch has successfully started the link and is now capable of exchanging layer 3 frames with the endpoint. If the endpoint does not support SPID initialization procedures, the voice extension of the endpoint associated with the link is also displayed. This is the normal state for a link in a point-to-point wiring configuration.
  • L3-established — The link is in the MF_EST_NORM state at layer 2 and SPID initialization procedures have been successfully completed. The voice extension of the endpoint associated with the link is also displayed. This is the normal state for a link in a multipoint wiring configuration.
  • hyperactive — Traffic on this link has exceeded the threshold and the link has been suspended.
Endpt Extension
The extension of the voice/data endpoint associated with the link. This field is blank if the link is not in the established or L3-established state.
Endpt SPID
The SPID (Service Profile Identifier) administered for the voice/data endpoint. This field is blank if the link is not in the established or L3-established state.
Service SPID
If the link is associated with the Service SPID this field displays yes and the Endpoint Extension field is blank. Otherwise this field is blank. Service SPID is a feature used by service technicians to check building wiring between the switch and the BRI endpoint.

Interpreting results of status bri-port

The following table helps interpret the results of status bri-port. Find the combination of the output field values in your report and follow the actions for the type of endpoint connected to the port.
Error Type
Aux Data
Associated Test
Alarm Level
On/Off Board
Test to Clear Value
BRI, ASAI
0-126
Assigned
blank
blank
This is a transitory state for BRI endpoints and ASAI adjuncts. The switch is attempting to establish the link.
  1. Check the endpoint and wiring by following the SPID Facility test’s procedure described in BRI-SET, Various Adjuncts in the Maintenance Alarms for Maintenance Commands for Avaya Aura® Communication Manager, Branch Gateways and Servers.
  2. Repeat status bri-port to determine that the Layer 2 state of the signaling link is either L3-established (for ASAI adjuncts and BRI endpoints supporting MIM initialization) or established (for fixed TEI BRI endpoints and automatic TEI BRI endpoints not supporting MIM initialization). If it is not, follow normal escalation procedures. (A MIM or management information message is a level-3 message that conveys management and maintenance information between a communications system and a BRI terminal.)
ASAI
0-63
Established
blank
blank
This is a transitory state for ASAI adjuncts. ASAI signaling is connected at Layer 2 but the Layer 3 Restart procedure has not been completed between switch and adjunct.
  1. Check the adjunct by following the recommended repair procedures of the manufacturer.
  2. Repeat status bri-port and determine whether the L2 state of the signaling link is L3-established. If it is not, follow normal escalation procedures.
BRI
0-126
Established
ext#
blank
This is the normal state for non-MIM initializing, fixed, and automatic TEI BRI endpoints.
BRI, ASAI
64-126
Established
blank
blank
This is a transitory state for automatic TEI BRI endpoints that support MIM initialization.
  1. Verify that SPID administration on the switch and the endpoint are consistent. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established.
  2. Try replacing the endpoint. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, follow normal escalation procedures.
BRI-
64–126
L3–Established
ext#
blank
This is the normal state for automatic TEI BRI endpoints that support MIM initialization.
BRI
0–126
L3–Established
blank
blank
An invalid SPID is assigned to link.
Change the SPID value in the BRI endpoint to match the SPID administered to the BRI endpoint on the port. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, follow normal escalation procedures.
BRI
0–126
L3–Assigned
ext#
blank
This is a transitory state for BRI endpoints that support MIM initialization.
  1. Wait 5 seconds and repeat the command. If the state has not changed, continue with Step 2.
  2. Make sure SPID administration on the switch and endpoint are consistent. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, go to Step 3.
  3. Try replacing the endpoint. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, follow normal escalation procedures.
BRI
0–126
L3–Assigned
ext#
yes
This is a transitory state for BRI endpoints that support MIM initialization when a SPID Facility test has been used to initialize the station.
  1. Wait 5 seconds and repeat the command. If the state has not changed continue with Step 2.
  2. Make sure SPID administration on the switch and endpoints are consistent. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, go to Step 3.
  3. Try replacing the endpoint. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, follow normal escalation procedures.
ASAI BRI
0-126
Hyperactive
ignore
ignore
Link has sent too many messages per unit time. Signaling has been suspended. After 60 seconds, the system attempts to put the link into service. If a link remains in this state while there is no activity at the BRI endpoint, take the following steps:
  1. Make sure SPID administration on the switch and endpoints are consistent. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, go to Step 2.
  2. Try replacing the endpoint. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, follow normal escalation procedures.
ASAI
0-126
L3-Restarting
ext#
The switch has sent a Restart message to the adjunct but has not yet received a Restart Acknowledgment message from the adjunct.
ASAI
0-126
L3-Restarted
ext#
After receiving a Restart Acknowledgment message, the switch has sent a Heartbeat message to the adjunct and is waiting for a response.
ASAI
0-126
L3-Established
ext#
This is the normal state for ASAI adjunct.
BRI-
64–126
L3–Established
ext#
blank
This is the normal state for automatic TEI BRI endpoints that support MIM initialization.
BRI
0–126
L3–Established
blank
blank
An invalid SPID is assigned to link.
Change the SPID value in the BRI endpoint to match the SPID administered to the BRI endpoint on the port. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, follow normal escalation procedures.
BRI
0–126
L3–Assigned
ext#
blank
This is a transitory state for BRI endpoints that support MIM initialization.
  1. Wait 5 seconds and repeat the command. If the state has not changed, continue with Step 2.
  2. Make sure SPID administration on the switch and endpoint are consistent. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, go to Step 3.
  3. Try replacing the endpoint. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, follow normal escalation procedures.
BRI
0–126
L3–Assigned
ext#
yes
This is a transitory state for BRI endpoints that support MIM initialization when a SPID Facility test has been used to initialize the station.
  1. Wait 5 seconds and repeat the command. If the state has not changed continue with Step 2.
  2. Make sure SPID administration on the switch and endpoints are consistent. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, go to Step 3.
  3. Try replacing the endpoint. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, follow normal escalation procedures.
ASAI BRI
0-126
Hyperactive
ignore
ignore
Link has sent too many messages per unit time. Signaling has been suspended. After 60 seconds, the system attempts to put the link into service. If a link remains in this state while there is no activity at the BRI endpoint, take the following steps:
  1. Make sure SPID administration on the switch and endpoints are consistent. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, go to Step 2.
  2. Try replacing the endpoint. Repeat status bri-port to determine whether the Layer 2 state of the signaling link is L3-established. If it is not, follow normal escalation procedures.
ASAI
0-126
L3-Restarting
ext#
The switch has sent a Restart message to the adjunct but has not yet received a Restart Acknowledgment message from the adjunct.
ASAI
0-126
L3-Restarted
ext#
After receiving a Restart Acknowledgment message, the switch has sent a Heartbeat message to the adjunct and is waiting for a response.
ASAI
0-126
L3-Established
ext#
This is the normal state for ASAI adjunct.