Standing Conditions
MEA-SWREV (Software Mismatch)
The corresponding SNMP name for this condition is “meaSwRevision”.
AIDTYPE Default
Severity
Probable Cause Suggested Corrective
Action
MOD MJ
1
The software revision of the
backup (standby) controller
within the duplex protection
group does not match that of
the primary (active) controller.
Reload the software
generic, to get the backup
module updated with the
desired generic.
Table 290: MEA-SWREV (Standing Condition)
MEPANR (MEP not Assigned)
The corresponding SNMP name for this condition is “mepNotPresentL2”.
AIDTYPE Default
Severity
Probable Cause Suggested Corrective Action
ELAN,
ELINE
NR The facility has
been configured
as a member of a
flow based
protection group,
but the
associated MEP
has not yet been
provisioned.
An appropriate MEP instance must be
associated with a flow configured as a
member within a protection group if full
functionality of the protection group is to
be realized. Provision the appropriate
MEP instance associated with the facility
to ensure full support of all protection
switching trigger conditions.
Table 291: MEPANR (Standing Condition)
1
For NCU-II-P modules, the default severity is MN.
902 FSP 3000R7 Maintenance and Troubleshooting Manual - Product Release 16.2 - Document Issue A
To Next Page
Loading...