View IAD status

You must complete any earlier mandatory steps before you can complete this step.

The following IAD status information is displayed in the Details panel. The fields prefixed by (*) are present only if the parent IAD supports a LES EOC channel.

When you have finished viewing the IAD status, click on Run IAD tests to test the IAD's operation, or Finish to return to the beginning of the task.


Parameter

Description
Requested status Specifies whether an administrator has attempted to activate the IAD. Values:
  • Active
    The object has been activated.
  • Inactive
    The object has not been activated or has been deactivated.
  • Disabled
    The object has been disabled.
Actual status Specifies the current status of the IAD. Values:
  • Active
    The object is active.
  • Going Active
    Activation is in progress.
  • Going Inactive
    Deactivation is in progress.
  • Inactive
    The object is inactive.
  • Disabled
    The object has been disabled.
  • Activation Failed
    The object is inactive because an activation attempt has failed.
  • Failed
    The object was active but has failed.
  • Quiescing
    The object is preparing for normal deactivation. It is operating normally but will not accept any new users.
  • Waiting For Parent
    The object cannot be used because its parent object is not yet active.
  • Parent Failed
    The object cannot be used because its parent object has failed.
Alarm state Specifies whether any alarms are currently raised for this object. Values:
  • Clear
    No alarms are currently raised.
  • Attention Required
    Attention Required - the object is not operating normally, and needs operator intervention.
  • Attend to Dependent
    Attention Required elsewhere - another object on which this object depends is not operating normally.
Required sustained cell rate The sustained cell rate required to support calls on this IAD.
(*) Vendor Name of the vendor that produced the IAD.
(*) Model Vendor's designated model number for the IAD.
(*) Hardware version The vendor's designated hardware version for the IAD.
(*) Software version The vendor's designated software version for the IAD.
(*) Time since last re-initialization The time, in hundredths of a second since the IAD was last re-initialized.
(*) Number of CPCS packets received Number of CPCS packets received.
(*) Number of CPCS packets transmitted Number of CPCS packets transmitted.
(*) Number of CPS parity errors Number of errors encountered where the start field indicates a transmission error (as specified in I.363.2).
(*) Number of sequence number errors Number of errors encountered where the sequence number of the start field is wrong (as specified in I.363.2).
(*) Number of CPS OSF mismatch errors Number of errors encountered where the number of octets expected for the CPS packet header overlapping into the protocol data unit does not match the information contained in the start field (as specified in I.363.2).
(*) Number of CPS OSF errors Number of errors encountered where the offset field of the start field contains a value of 48 or greater (as specified in I.363.2).
(*) Number of CPS HEC errors Number of errors encountered where the HEC code of the CPS packet header indicates transmission errors in the packet header (as specified in I.363.2).
(*) Number of oversized CPCS packets Number of errors encountered where the length of the received CPS SDU exceeds the maximum length (as specified in I.363.2).
(*) Number of CPS reassembly errors Number of errors encountered where a partial CPS packet has been received but is discarded due to errors detected before reassembly of the CPS packet could be completed (as specified in I.363.2).
(*) Number of CPS HEC overlap errors Number of errors encountered where the HEC code of a CPS packet header that was overlapping a protocol data unit boundary indicates transmission errors in the CPS packet header (as specified in I.363.2).
(*) Number of CPS UUI errors Number of errors encountered where the UUI field of the received CPS packet header contains a value that is reserved for future standardization (as specified in I.363.2).
(*) Number of CPS CID errors Number of errors encountered where the channel ID in the received CPS packet header is not associated with a service access point (as specified in I.363.2).
(*) Number of oversized SSSAR packets Number of errors encountered where the maximum allowed size for a reassembled SSSAR service data unit has been exceeded (as specified in I.366.1).
(*) Number of reassembly timer expiry errors Number of errors encountered where the reassembly timer has expired (as specified in I.366.1).
(*) Number of undersized SSTED packets Number of errors encountered where a SSTED protocol data unit of length 8 or less has been received (as specified in I.366.1).
(*) Number of SSCS length errors Number of errors encountered where the value of the length field in an SSTED protocol data unit does not match the length of the received SSTED protocol data unit (as specified in I.366.1).
(*) Number of CRC mismatch errors Number of errors encountered where the value of the CRC field is not equal to the CRC calculated over the received information (as specified in I.366.1).