Alcatel-Lucent 5620 Troubleshooting Manual page 123

Alarm name, ID, type, and probable
cause(s)
Alarm name: TopologyMisconfigured
Alarm ID: 95
Type: configurationAlarm (11)
Probable cause: topologyMisconfigured (81)
Alarm name: TypeMismatch
Alarm ID: 96
Type: configurationAlarm (11)
Probable cause:
serviceSiteTypeMisconfigured (82)
(3 of 3)
Alarm name, ID, type, and probable
cause(s)
Alarm name:
ManagementAccessFilterMisconfigured
Alarm ID: 76
Type: configurationAlarm (11)
Probable cause: invalidSourcePortIdentifier
(61)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Critical
Object Type (class): Service
Domain: service
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): Service
Domain: service
Self-clearing alarm raised: Yes
Table 3-52 Domain: sitesec
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class): MacMafEntry
Domain: sitesec
Self-clearing alarm raised: Yes
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
The service type for the same service
ID is different on another device.
Check the service SDP bindings. If
the required SDP bindings are missing
from the service, the alarm is raised.
Because VPLSs can use spoke
bindings (service sites with the save
VPLS ID can have spoke bindings), the
alarm does not apply.
A service ID is created on the router
using CLI that duplicates a service ID
created using the 5620 SAM.
Use the 5620 SAM topology map to
view the affected object. You can
delete the new and invalid service,
which also deletes the service from
the managed device.
When 7250 SAS and Telco VLANs are
configured but the port Mode
parameters of the uplink ports are
not set to Network, the alarm is
raised. Configure the ports correctly
from the 5620 SAM navigation tree.
The same service id used by the
5620 SAM is used for a different
service on another device.
Additional information
Management access filters are used
to restrict management of the device
by other nodes outside specific
networks or subnetworks, or through
designated ports. The filters must be
configured locally. The default
action denies or permits
management access in the absence
of a more specific management
access filter match. Each entry
represents a collection of filter mass
criteria
November 2008 3-85