Skip to main content

ipoTrunkOOS Trunk Out of Service Alarm

Jeremy Boilard

Problem Statement

A Major ipoTrunkOOS alarm may be raised on an S-Edition Expansion (V2) device when a trunk component transitions from operational to failed state. The alarm description is ipoGenTrunkFailureSvcEvent, and the equipment detail identifies the affected trunk by line, slot, and port, for example: "Trunk out of Service. Line: 2 Slot: 1 Port: 10."

Impact

The affected trunk may be unavailable while the alarm is active. Calls or services using that trunk can be disrupted until the trunk returns to service or is repaired.

Alarm

ipoTrunkOOS / ipoGenTrunkFailureSvcEvent / Alarm Code ACT

Troubleshooting Steps

  1. Review the alarm dashboard and confirm whether the ipoTrunkOOS alarm is still active or has cleared.
  2. Record the affected equipment location from the alarm details, including line, slot, and port values.
  3. Check the alarm history for a clearing event and note the active duration.
  4. If the alarm cleared quickly and the trunk currently shows normal status, continue monitoring for recurrence.
  5. If the alarm remains active or repeatedly reoccurs, verify the trunk component status on the device management interface.
  6. Inspect the affected line, slot, and port for administrative shutdown, configuration mismatch, disconnected cabling, failed module/port, or upstream service-provider issue as applicable to the trunk type.
  7. After any corrective action, confirm that the trunk returns to service and that the ipoTrunkOOS alarm clears from the dashboard.

Resolution

In the observed case, the Major ipoTrunkOOS alarm cleared automatically after a subsequent clearing event and was active for only 8 seconds. No further corrective action was documented after the alarm cleared. For recurring or persistent alarms, investigate the affected trunk component identified by the line, slot, and port details.