Alarms Reference: Nortel Multiservice Data Manager

Nortel Multiservice Data Manager
Alarms Reference
NN10470-501
Document status: Standard
Document issue: 01.02
Document date: May 2007
Product release: 16.2
Job function: Fault and Performance Management
Type: NTP
Language type: U.S. English
Sourced in Canada and the United States of America.
Copyright 2007 Nortel Networks. All Rights Reserved
NORTEL, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
Contents
New in this release 4
Features 4
Other changes 4
Proxy alarms 5
Generic SNMP alarms 172

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
Copyright 2007, Nortel Networks Nortel Confidential
New in this release
The following sections detail what is new in the Nortel Multiservice Data
Manager Alarms Reference (NN10470-501) NTP for 16.2:
Features (page 4)
Other changes (page 4)
Features
The following sections detail whats new in Alarms Reference for 16.2:
updated Details description for 3010 0801 (page 22) and 3010 0823
(page 28)
new alarm, 3010 0823 (page 28)
new alarm, 7042 0004 (page 168)
Other changes
See the following sections for information about changes that are not feature-
related:
References to Nortel Multiservice Data Manager technical publications
were updated with new document numbers.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
Proxy alarms
Nortel Multiservice Data Manager proxy alarms are generated by various
Multiservice Data Manager servers and proxy agents. A proxy alarm is an
alarm that is generated by a server or agent and not from a network element
trap.
The Multiservice Data Manager generates proxy alarms and injects them into
the main alarm stream with the network element-generated alarms. Proxy
alarms are received from the following sources:
FMIP Management Data Router (FMDR)
Nortel Multiservice Provider Edge Data Translation (NDTR)
Inbound Management Data Router (IMDR)
Inbound Application Programming Interface (IAPI)
SNMP Management Data Router (SMDR)
DPN Management Data Router (DMDR)
Multiservice Data Manager Server Manager (SVM)
Management Data Provider (MDP)
Disabling the generation of proxy alarms

To disable the generation of proxy alarms, refer to applicable documentation
about configuring the file /op/MagellanNMS/cfg/DMDRAlarmExcep.cfg and
configuring alarm exception handling in Nortel Multiservice Data Manager
AdministrationServer Management (NN10470-310).

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
-6-
Proxy alarms
0999 0001
Component Severity Status
<deviceType>/<deviceName> critical/cleared set/clear
Legend
Details When the status is set, the Multiservice Data Manager (MDM)
workstation has lost its IP connection to the indicated network
element. The cause of the failure is a problem with the
communications links connecting the workstation and the
network element or a failure on the network element itself.
When the status is clear, connectivity has been restored.
This alarm is generated by MDM on behalf of the network
element. The time-stamp of the alarm is based on the
workstation time.
For Multiservice Switch (MSS) network elements, MDM tries to
emulate the network element time-frame by tagging these
alarms with a GMT time adjusted with a configured offset
(FDTM servers command line, see the section on FDTM in
Nortel Multiservice Data Manager AdministrationServer
Management (NN10470-310). If no offset is configured on
FDTM, the alarms time frame is therefore GMT.
For Multiservice Provider Edge (MPE) network elements, MDM
tries to emulate the network element time-frame by
remembering the offset specified in the last message received
from the network element and use it when generating this
alarm.
Probable cause equipment failure
Type equipment
Remedial action Check the communication link connecting the workstation and
the network element. Also ensure that the network element has
not failed. If you cannot detect a problem in the communication
link, the physical link, or the network element itself, and the
problem persists, contact Nortel Customer Support.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
-7-
Proxy alarms
0999 0002
<deviceType>/<deviceName> critical/cleared set/clear
Legend <deviceType> is the type of network element

<deviceName> is the name assigned to this network element in
your network
Details When status is set, the system object ID (sysOID) polled from
the network element does not have the value expected. This
situation can be caused by IP address duplication or incorrect
information given to IP discovery.
When status is clear, the expected network element type (or
sysOID) has been found when polled from the network element.
Probable cause unexpected information
Type operator
Remedial action Determine if the IP address specified in the alarm comment text
is duplicated in the network and verify the information given to
IP discovery.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
-8-
Proxy alarms
0999 0003
<deviceType>/<deviceName> critical/warning/ set/clear
cleared

your network
Details When status is set, the polled hardware identification
<hardware ID> has changed. IP address duplication or a
network element replacement can cause this state. If the
network element name has not changed, it is assumed that a
faulty network element has been replaced by a new one. The
new hardware identification is accepted, and the Warning
severity is used. If the network element name has also
changed, it is assumed that is it due to IP address duplication.
The Critical severity is used and subsequent polling results are
ignored until the problem is resolved.
When status is clear, the expected hardware identification
<hardware ID> has been found when polled from the network
element.
Probable cause unexpected information
Type operator
Remedial action For the CRITICAL SET alarm, determine if the IP address
specified in the alarm comment text is duplicated in the
network. For the WARNING SET alarm, no action is required.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
-9-
Proxy alarms
0999 0004
<deviceType>/<deviceName> major/cleared set/clear

your network
Details When the status is set, a new name assigned to a network
element duplicates a name already assigned to another
network element of the same type; the name change is rejected
and the alarm is raised against the old name.
When the status is clear, the problem has been resolved.
Probable cause duplicate information
Type operator
Remedial action Change the name of the network element so that it does not
duplicate the name of any other network element of the same
type.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 10 -
Proxy alarms
0999 0010
PM/<component id> major/cleared set/clear
Legend <component id> is the name of any DPN component that

generates status records
Details The state of the component has been changed due to a status
record received from the network. When the status of the alarm
is a set, it means that the status record indicated that the
component is down, and there are no corresponding active
alarms (generated by the network element) on that component
to indicate that it is down. Therefore Nortel Multiservice Data
Manager created a proxy alarm to replace the missing alarm,
and will mark the component Out of service.
When the status of the alarm is a clear, it means that the status
record indicated that the component is up, and there were
active alarms on that component to indicate that it is down.
Therefore Multiservice Data Manager generates a proxy alarm
to replace the missing clear, and will mark the component
Inservice.
The comment text of this alarm contains information on the
status record that was received that triggered the proxy alarm.
Probable cause
Type
Remedial action This alarm is issued either because the status record was
received before the alarm issued by the network element, which
would put the component in the proper state (and the proxy
alarm would be cleared when the real alarm is received) or
because the alarm issued by the network element has been
lost.
Treat proxy alarms as you would treat regular alarms and use
them in debugging network problems.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 11 -
Proxy alarms
0999 0011
<deviceType>/<component id> major/cleared set/clear
Legend <deviceType> is the network element type managed by IMDR

<component id> is the name of a component managed by
IMDR
Details The alarm generated by IMDR for an SNMP component is
inconsistent with traps received from the network. This can
happen, for example, if an SNMP poll produces a state change
notification without receiving a corresponding trap from the
network.
When the status of the alarm produced by IMDR is a set, it
means that the Poll response indicates that the component is
down, but there are no corresponding active alarms (generated
by the network element) on that component to indicate that it is
down. Therefore, Nortel Multiservice Data Manager created a
proxy alarm to replace the missing alarm, and will mark the
component Out of service.
When the status of the alarm is a clear, it means that the Poll
response indicates that the component is up, but there are
Therefore, Multiservice Data Manager generates a proxy alarm
to replace the missing clear, and marks the component
Inservice.
The comment text of this alarm contains information on the
state notification that was received and triggered the proxy
alarm.
Probable cause
Type
Remedial action This alarm is issued either because the state notification was
received before the trap was issued by the network element,
which would put the component in the proper state (and the
proxy alarm would be cleared when the real trap is received) or
because the trap issued by the network element has been lost
or the network element never generated a trap.
Treat proxy alarms as you would treat regular alarms and use
them in debugging network problems.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 12 -
Proxy alarms
0999 0012
EM/<component id> major/cleared set/clear
Legend <component id> is the name of any MSS component

Details When the status of the alarm is set, the state of the component
has been changed to Out-Of-Service due to one of the
following:
- A state change notification (SCN) was received from the MSS
network element indicating that the component is down
- A state walk, performed by the Multiservice Data Manager
(MDM) fault collector server, found the component to be down
and no Major or Critical alarm were already present for the
component
- A clear alarm was received for the last Major or Critical alarm
against the component but the state of the component reported
in the clear alarm is still showing the component to be down
When the status of the alarm is clear, the state of the
component has been changed to In-Service due to one of the
following:
- A state change notification (SCN) was received from the MSS
network element indicating that the component is up
- A state walk, performed by the MDM fault collector server
(FMDR), found the component to be up and a proxy set alarm
exists for the component
- A clear alarm was received for the component showing the
component to be up and a proxy set alarm exists for the
component
The comment text of this alarm describes which of these
conditions caused the alarm to be generated.
This alarm is generated by the MDM fault collector server on
behalf of the MSS network element. The time-stamp of the
alarm is taken from the triggering notification received from the
network element (SCN, state walk response or clear alarm). In
the case of state walk alarms, two proxy alarms generated by
two MDMs for the same problem will have different time-stamps
because the state walk is likely to run at different times.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 13 -
Proxy alarms
Details (continued) If two fault collector servers (FMDRs) generate two active proxy
alarms on the same component, only one is kept. Also, it is
possible for one FMDR server to generate a proxy alarm
against a component (e.g. due to a state-walk resulting from a
loss of connection) while an actual alarm still exists on that
same component from another FMDR server that has not lost
connection. This doubling up is temporary and the proxy alarm
will automatically be cleared when the real problem is solved on
the network element.
Probable cause unknown
Type unknown
Remedial action Treat proxy alarms as you would treat regular alarms and use
them to troubleshoot network problems.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 14 -
Proxy alarms
0999 0013
<deviceType>/<deviceName> major/warning/ set/clear
cleared
[<component type>/<component instance>]

your network
Details The alarm generated by the Nortel Multiservice Data Manager
SNMP Management Data Router (SMDR) for an SNMP
component is inconsistent with traps received from the network.
When the status of the alarm produced by SMDR is a set, it
means that the Poll response indicates that the component is
down, but there are no corresponding active alarms on that
component to indicate that it is down. Therefore, Multiservice
Data Manager creates a proxy alarm to replace the missing
alarm, and marks the component Out of Service (OOS) or In-
service Trouble (ISTB).
When the status of the alarm is a clear, it means that the Poll
response indicates that the component is up, but there are
Therefore, Multiservice Data Manager generates a proxy alarm
to replace the missing clear, and marks the component
Inservice.
The severity of the alarm is major when the component is OOS
and the severity of the alarm is warning when the component is
ISTB.
Type unknown
Remedial action This alarm is issued either because the poll response was
received before the trap was issued by the network element,
which would put the component in the proper state (and the
proxy alarm would be cleared when the trap is received) or
because the trap issued by the network element has been lost
or the network element never generated a trap.
Treat proxy alarms as you would treat regular alarms. Use them
to debug network problems.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 15 -
Proxy alarms
0999 0014
<deviceType>/<deviceName> major/warning/ set/clear
cleared
[<component type>/<component instance>]

your network
Details This alarm is generated by the Nortel Multiservice Data
Manager SNMP Management Data Router (SMDR) for a
component whose administrative state is changed or
inconsistent with traps received from the network.
This alarm is labeled ACKed. The ACK userID is SMDR.
When the status of the alarm produced by SMDR is a SET, it
means that a polled response will indicate that the component
is administratively-down, and that there are no corresponding
active SET alarms with sufficient severity on that component.
Multiservice Data Manager creates a proxy alarm to record this
inconsistency.
When the status of the alarm is a CLEAR, it means that a polled
response will indicate that the component is not in an
administrative-down state, or that a SET alarm has been
received with sufficient severity.
When the severity of the alarm is major, the component is
administratively-down and completely disabled. When the
severity of the alarm is warning, the component is
administratively-down but only partially disabled.
Type unknown
Remedial action This alarm is issued to allow the operators to continue to
monitor alarms on administratively-down components. No other
action is required for this alarm.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 16 -
Proxy alarms
0999 0100
<deviceType>/<deviceName> warning message

your network
Details The specified access server/workstation has lost its IP
connection to the indicated network element. There are still
other connections to this network element. The cause of the
failure is a problem with the communications links connecting
the Multiservice Data Manager (MDM) workstation and the
network element.
This alarm is generated by MDM on behalf of the network
element. The time-stamp of the alarm is based on the
workstation time.
For Multiservice Switch (MSS) network elements, MDM tries to
emulate the network element time-frame by tagging these
alarms with a GMT time adjusted with a configured offset
(FDTM servers command line, see the section on FDTM in
Nortel Multiservice Data Manager AdministrationServer
Management (NN10470-310). If no offset is configured on
FDTM, the alarms time frame is therefore GMT.
For Multiservice Provider Edge (MPE) network elements, MDM
tries to emulate the network element time-frame by
remembering the offset specified in the last message received
from the network element and use it when generating this
alarm.
Probable cause equipment failure
Type equipment
Remedial action Check the communication link connecting the workstation and
the network element. Also ensure that the network element has
not failed. If you cannot detect a problem in the communication
link, the physical link, or the network element itself, and the
problem persists, contact your Nortel Customer Support.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 17 -
Proxy alarms
3010 0000
NMS/<w/s name> APP <application name> major/cleared set/clear
Legend <w/s name> is the name of the workstation generating the error
<application name> is the server on the Nortel Multiservice
Data Manager workstation that has stopped or restarted
Details This alarm is generated by the Server Manager (SVM). It is
issued when the key Nortel Multiservice Data Manager server
application is stopped and restarted.
This alarm contains COMMENT text information that describes
the name of the server application. In the SET alarm, the
COMMENT text contains the signal # that caused the
application to stop. In the CLEAR alarm, the COMMENT text
contains the current number of restart times, out of the total
restarted times allowed for this application.
Probable cause
Type
Remedial action Verify that no one on the workstation terminated the application.
If the application restarts on its own (as it is supposed to do)
there is no problem. However, if the application cannot restart,
review the failure code and refer to Multiservice Data Manager
documentation for more information.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 18 -
Proxy alarms
3010 0700
NMS/<w/s name> GROUP <MSS group name> warning msg
<MSS group name> is the name of the unreachable network
element group
Details This alarm is issued when the Nortel Multiservice Data
Manager host cannot reach the indicated group to perform a
TODchangeover command.
Probable cause
Type
Remedial action Verify that the group is included in the HGDS.cfg file and that
this group name was specified using capital letters. Verify that
the user ID and password for this group are valid. Execute the
command again using the correct parameters.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 19 -
Proxy alarms
3010 0701
NMS/<w/s name> PP <MSS warning msg
nodeID/nodename>
<MSS nodeID/nodename> is the nodeID or nodename of the
unreachable node
Details This alarm is issued when Nortel Multiservice Data Manager
host cannot reach the indicated node to query the current time
offset.
Probable cause
Type
Remedial action Verify that the specified node is active and accessible. Verify
that the userID and password for this node are valid. If the
userID or password are different than those used by the other
nodes in the group, have the userID and password added or
changed on the affected node. If the node was unavailable
during the execution of the TODchangeover, execute the
command again after the node has returned to service.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 20 -
Proxy alarms
3010 0702
NMS/<w/s name> PP <MSS warning msg
nodeID/nodename>
<MSS nodeID/nodename> is the nodeID or nodename of the
unreachable node
This alarm is issued when Nortel Multiservice Data Manager
host cannot reach the indicated node to set the current time
offset.
Details
Probable cause
Type
Remedial action Verify that the specified node is active and accessible. Verify
that the userID and password are valid. If the userID or
password is different than those used by the other nodes in the
group, have the userID and password added or changed on the
affected node. If the node was unavailable during the execution
of the TODchangeover, execute the command again after the
node has returned to service.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 21 -
Proxy alarms
3010 0703
NMS/<w/s name> APPL TODCHANGEOVER warning msg
Details This alarm is issued when the TODchangeover command failed
due to incorrectly specified parameters.
Probable cause
Type
Remedial action Check the log file associated with this application to determine
which parameter was incorrectly specified. Execute the
command again with the correct parameters.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 22 -
Proxy alarms
3010 0801
NMS/<w/s name> APP/PPAUTOPATCH minor set
cleared clear
Legend <w/s name> is the name of the workstation generating the

alarm.
Details If the status is set, an instance of the auto-patch process
(identified by the -nodes parameter in the comment text) was
scheduled to execute but terminated due to the detection of the
file /opt/MagellanNMS/cfg/private/noppautopatchrun.
A clear alarm is issued the next time that the process starts and
the noppautopatchrun file is not detected. The clear alarm is not
immediately issued when the noppautopatchrun file is
removed.
Probable cause Operational condition
Type Operator
Remedial action The noppautopatchrun file is typically created due to another
maintenance activity where a concurrent auto-patching activity
would not be desirable (for example, a software migration on
the network element). To restore the auto-patching behaviour,
remove the noppautopatchrun file after first ensuring that the
maintenance activity that generated the noppautopatchrun file
has successfully completed.
If the missed patches are required before the process is
scheduled to run again, the missed patches can be manually
downloaded and then manually applied. If the missed patches
are not required immediately, allow the process to complete the
task on the next scheduled attempt.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 23 -
Proxy alarms
3010 0802
NMS/<w/s name> APP/PPAUTOPATCH minor set
NODES/<nodes>
cleared clear

alarm
<nodes> is the value of the MDM auto-patch process command
line option -nodes. This is usually the name of an HGDS group,
a network element name, or the name of a file that contains a
list of network elements.
(identified by the value of <nodes>) did not run to full
completion due to the expiry of a timer set using the auto-patch
process -max_duration command line option.
A clear is issued the next time that the process starts.
Type Processing
Remedial action Check the log files to determine which aspects of the execution
have succeeded and which have failed to complete.
If the full execution of the process regularly fails to complete,
one possibility may be that the maximum duration setting is too
short. If so, edit the crontab entries and lengthen the amount of
time specified by the -max_duration option assuming that it fits
into the maintenance window for patch application.
There may be too many network elements in the list specified
by the -nodes command line option. This set of network
elements can be split into smaller groups and an auto-patch
process instance created for each new group.
This may be the initial attempt for a set of network elements
being made patch current. In this case, there may be more
patches than usual to download. Depending on the nature of
the patches, it may take longer than usual for execution to
complete (if the patched files are very large).
downloaded and manually applied. If the missed patches are
not required immediately, allow the process to complete the

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 24 -
Proxy alarms
3010 0803
NMS/<w/s name> APP/PPAUTOPATCH major set
NODES/<nodes> cleared
clear

alarm
<nodes> is the value of the MDM auto-patch process command
line option -nodes. This is usually the name of an HGDS group,
a network element name, or the name of a file that contains a
list of network elements.
(identified by the value of <nodes>) did not run to full
completion due to a failure of at least one of the network
elements to access the SDS site. No further downloads are
attempted to other network elements as the current problem is
expected to be encountered by all of the network elements.
A clear is issued the next time that the process starts.
Type Processing
If the auto-patch command line options related to SDS access
are incorrect, edit the crontab entries and correct the options.
If the SDS is unavailable, restore the SDS to service.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 25 -
Proxy alarms
3010 0820
NMS_APP/PPAUTOPATCH major set
EM/<node name> cleared clear
Legend <node name> is the name of the network element for which
automatic patch downloading tasks failed to complete.
Details If the status is set, an instance of the auto-patch process did not
complete the auto-patch downloading tasks for the network
element identified by <node name>. The MDM server name is
included in the comment text of the alarm.
A clear is issued each time that the process successfully
completes the auto-patch downloading tasks for the network
element identified by <node name>. The MDM server name is
included in the comment text of the alarm.
After performing the remedial action below, manually clear the
alarm before attempting to perform the auto-patch process a
second time. If the download fails again, a new alarm is
propagated and the MDM captures the cause of the new failure
in the comment text. If you do not manually clear the previous
alarm, the new alarm is treated as a duplicate and is dropped.
Probable cause Unknown

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 26 -
Proxy alarms
Type Processing
If the network element could not be identified by the MDM,
ensure that the MDM server processes are configured properly.
If the MDM does not have IP connectivity to the network
element, this problem is independent of the auto-patch process.
There should be other alarms in the MDM Alarm Display to
indicate this problem.
If the MDM has IP connectivity to the network element but
cannot authenticate with the network element, ensure that the
access userID and password on the network element are valid.
If the access userID and password are invalid, restart the auto-
patch process with the correct authentication parameters.
If the MDM has IP connectivity to the network element and can
authenticate the network element but cannot access or
authenticate with the SDS, restart the auto-patch process using
the correct SDS access/authentication parameters.
Another administrator or engineer may be performing a
mutually exclusive task that has caused the download to fail.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 27 -
Proxy alarms
3010 0821
automatic patch application tasks failed to complete.
Details If the status is set, an instance of the auto-patch process did not
complete the patch application tasks for the network element
identified by <node name>. The MDM server name is included
in the comment text of the alarm.
A clear is issued each time that the process successfully
completes the patch application tasks for the network element
identified by <node name>. The MDM server name is included
in the comment text of the alarm.
After performing the remedial action below, manually clear the
alarm before attempting to perform the auto-patch process a
second time. If the download fails again, a new alarm is
propagated and the MDM captures the cause of the new failure
in the comment text. If you do not manually clear the previous
alarm, the new alarm is treated as a duplicate and is dropped.
Type Processing
If the log files provide the required information, logon to the
indicated MSS node to resolve the issue.
If the auto-patch process specifies -apply without the -download
command parameter, perform the Remedial action described
for alarm 3010 0820 before taking the remedial action below.
You may also run the auto-patch process again and specify the
-log_verbose command line parameter to collect query patch
information. If -log_verbose is specified, view the patch query
output file /opt/MagellanNMS/data/log/ppautopatch/
<YYYYMMDDThhmmss>.status. Then logon to the MSS node
to resolve the issue.
You can also directly perform MSS commands to diagnose and
resolve the issue. When the patch download has completed
successfully, you can manually apply the patches at anytime.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 28 -
Proxy alarms
3010 0823
automatic untar tasks fail to complete.
Details If the status is set, an instance of the auto-patch process failed
complete the auto-patch untar tasks for the network element
identified by <node name>.
A clear alarm is issued each time the ppautopatch process
starts to perform the auto-patch untar task.
Type Processing
Remedial action Check the log file in /opt/MagellanNMS/data/log/ppautopatch/
directory to determine which aspects of the execution have
succeeded and which have failed to complete.
If the network element could not be identified by the MDM,
ensure that the MDM server processes are configured properly.
If the MDM does not have IP connectivity to the network
element, this problem is independent of the auto-patch process.
There should be other alarms in the MDM Alarm Display to
indicate this problem.
If the MDM has IP connectivity to the network element but
cannot authenticate with the network element, ensure that the
access userID and password on the network element are valid.
If the access userID and password are invalid, restart the auto-
patch process with the correct authentication parameters.
Make sure /bin/tar command is installed correctly.
Check SDS hosts are mounted onto correct mount point.
Check proper permission is assigned to current user if any
access error occurs.
Check the required patch tar files are stored in the correct
directory.
Check the integrity of patch tar files using tar command
manually.
Log in to MSS to check its shelf type. Only 7k, 9k, or 15k is
supported in release 16.2 .

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 29 -
Proxy alarms
3011 0100
NMS/<w/s name> DISK <id> critical/major/ set/clear
minor/cleared

error.
<id> is the disk volume identifier.
Details This alarm is generated by workstation surveillance. It is issued
when disk resource usage exceeds pre-defined thresholds.
This alarm contains COMMENT text information that identifies
the percentage of resources used. When the alarm clears, the
COMMENT text information indicates that resource usage is
normal.
The default threshold values are:
80% of resource used: MINOR
90% of resource used: MAJOR
95% of resource used: CRITICAL
Threshold values can be redefined through the sfm_config
script.
Probable cause
Type
Remedial action Contact the Nortel Multiservice Data Manager administrator
and the workstation administrator and apprise them of the
resource alarm.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 30 -
Proxy alarms
3011 01FF
NMS/<w/s name> cleared cleared
at startup to clear outstanding alarms against disk components.
Probable cause
Type
Remedial action none

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 31 -
Proxy alarms
3011 0200
NMS/<w/s name> CPU critical/major/ set/clear
minor/cleared

error.
when CPU resource usage exceeds pre-defined thresholds.
normal.
script.
Probable cause
Type
resource alarm.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 32 -
Proxy alarms
3011 0210
NMS/<w/s name> CPU/<id> critical/cleared set/clear

error.
<id> is the CPU identifier.
when a CPU is not currently online.
Use the command psr info to get more information on the status
of all CPUs or on a specific CPU.
Probable cause
Type
resource alarm.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 33 -
Proxy alarms
3011 02FF
NMS/<w/s name> cleared clear
at startup to clear outstanding alarms against CPU
components.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 34 -
Proxy alarms
3011 0300
NMS/<w/s name> MEMORY critical/major/ set/clear
minor/cleared

error.
when memory resource usage exceeds pre-defined thresholds.
normal.
script.
Probable cause
Type
resource alarm.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 35 -
Proxy alarms
3011 03FF
at startup to clear outstanding alarms against the MEMORY
component.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 36 -
Proxy alarms
3011 0401
NMS/<w/s name> PORT <ip_addr> major/cleared set/clear
<ip_addr> is the IP address assigned to the Ethernet port.
when the port at the indicated IP address is out of service. This
alarm contains COMMENT text information that identifies the
component. When the alarm clears, the COMMENT text
information indicates that the component is back in service.
There are no threshold values that trigger this alarm.
Probable cause
Type
resource alarm.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 37 -
Proxy alarms
3011 04FF
at startup to clear outstanding alarms against PORT
components.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 38 -
Proxy alarms
3011 0501
NMS/<w/s name> CONNECTION <ip_addr> critical/cleared set/clear
<ip_addr> is the IP address of the remote workstation.
when the connection to either a remote peer Nortel Multiservice
Data Manager workstation or a common device is lost. This
alarm contains COMMENT text information that identifies the
remote peer workstation or the device. When the alarm clears,
the COMMENT text indicates that the connection to the peer
workstation or the device has been re-established and
redundancy is restored.
There are no threshold values that trigger this alarm.
Probable cause
Type
Remedial action Contact the Multiservice Data Manager administrator and the
workstation administrator and apprise them of the resource
alarm.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 39 -
Proxy alarms
3011 05FF
at startup to clear outstanding alarms against CONNECTION
components.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 40 -
Proxy alarms
3011 0600
NMS/<w/s name> SDS <logical disk name> critical/cleared set/clear
<logical disk name> is the logical disk name used by Solstice
Disk Suite (SDS).
when the redundancy of the SDS disk mirroring system fails.
This alarm contains comment text that identifies the file system
that is jeopardized. When the alarm clears, the comment text
indicates that the redundancy of the file system is restored.
There are no threshold values that trigger this alarm. This alarm
is generated only by the machine that has SDS installed.
Probable cause
Type
resource alarm.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 41 -
Proxy alarms
3011 06FF
at startup to clear outstanding alarms against SDS
components.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 42 -
Proxy alarms
3012 0001
NMS_APP/CFGAUDIT EM/<node name> major set
Legend <node name> is the name of the affected MSS

Details During a Node Configuration Audit, activated from the Audit
Scheduler or from the command-line utility pcfgaudit, the on-
switch configuration data did not match the templates data.
The comment text of the alarm includes the location of the
report and the MDM server name.
Type Processing
Remedial action Inspect the report associated with the MSS, correct the on-
switch configuration, and manually clear the alarm using MDM
tools.
The MDM does not clear this alarm automatically. This alarm
must be manually cleared by an operator.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 43 -
Proxy alarms
3012 0002
NMS_APP/CFGAUDIT EM/<node name> major set
Legend <node name> is the name of the affected MSS

Details A Node Configuration Audit, activated from the Audit Scheduler
or from the command-line utility pcfgaudit, has failed.
The comment text of the alarm indicates Audit failed and the
specific error condition.
Type Processing
Remedial action Review the error condition described in the comment text and
correct the indicated problem.
Clear the alarm using one of the MDM fault tools before
attempting to rerun a Node Configuration Audit. The MDM does
not clear this alarm automatically. This alarm must be manually
cleared by an operator.
Some typical errors and remedial actions are listed below as
examples:
Example#1
The MDM has lost connectivity to the MSS node.
Re-establish the network connection.
Ensure that the MDM MSS Access and Configuration servers
have been started, including: fmdr, fdtm, pcserver and
configman.
Ensure that the FMDR is connected to the GMDR.
Ensure that the MSS node reporting the error is a member of an
MSS group specified in the HGDS configuration file HGDS.cfg.
Example#2
If the authentication failed, ensure that the MSS authentication
user name and password are correctly specified in the Audit
Scheduler or in the pcfgaudit command parameters.
Example#3
If the NP template log is not stored on the MSS node, or if the
log is corrupted (failed checksum), regenerate the log using the
procedure Generating an initial template log from Nodal
Provisioning procedure in Nortel Multiservice Data Manager
ConfigurationTools (NN10470-023).

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 44 -
Proxy alarms
3013 0001
NMS/<ws name> APP/BACKUP EM/<node warning msg
name>
Legend <ws name> is the name of the workstation generating the

alarm.
<node name> is the name of the network element on which the
backup on alarm failed.
Details A backup on alarm failed for the specified node. The alarm
indicates the reason for the failure. There are various reasons
for failure, some of which include invalid user ID, invalid
password, lost connection, and disk full.
Probable cause
Type
Remedial action The remedial action required depends on the reason for failure.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 45 -
Proxy alarms
50XX 00XX
<xx> /<component id> major/cleared set/clear
Legend <xx> is the device class that you are managing

<component id> is the name of the component
Details For customers who decide to use the SNMP integrator, they are
recommended to use a range of alarms to indicate an alarm
arriving from their system.
This range is from 50xx 0000 to 50xx 0200. Since we have no
control over what the customers use therefore we suggest that
customer build their own alarms document and include it into
the document so that their alarms can be found. We suggest
that customers choose a different value for each type of device.
Probable cause
Type
Remedial action Not applicable

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 46 -
Proxy alarms
50XX 01XX

Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 47 -
Proxy alarms
50XX 02XX

Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 48 -
Proxy alarms
5004 0001
Network major set
Legend none
Details The SNMP Integrator has received an invalid SNMP poll
response. Operator data contains in the first 4-bytes, the source
code location, and in the next 4-bytes, further information to be
used for debugging.
Comment text contains the IP address of where the poll
response is originated.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 49 -
Proxy alarms
5004 0002
Network major set
Legend none
Details The SNMP Integrator has received an invalid SNMP trap
message.
Operator data contains in the first 4-bytes, the source code
location, and in the next 4-bytes, further information to be used
for debugging.
Comment text contains the Internet address of where the poll
response is originated.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 50 -
Proxy alarms
5004 0003
Software major set
Legend none
Details A software error has occurred.
location, and in the next 4-bytes, further information to be used
for debugging.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 51 -
Proxy alarms
5004 0004
Engineering major set
Legend none
Details An overrun condition is encountered during polling. It occurs
when the actual poll interval device exceeds the poll interval
defined in the network element configuration file. The probable
cause is due to improper engineering of the polling parameters:
time-out, number of retry, and poll interval.
location, and in the next 4-bytes, the actual poll interval.
Comment text contains: Polling frequency overrun.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 52 -
Proxy alarms
5004 0005
Legend none
Details The SNMP GET response message indicates that there is an
error for the requested MIB variable.
location, and in the next 4-bytes, the error code as follows:
1. tooBig
2. noSuchName
3. badValue
4. readOnly
5. genErr
Consult Internet Standard RFC 1157, Simple Network
Management Protocol (SNMP) for more meanings of this error
status.
Comment text contains the Internet address of where the poll
response message is originated and the symbolic name of the
MIB variable.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 53 -
Proxy alarms
5004 0006
Legend none
Details An overrun condition is encountered during PING polling. It
occurs when the actual poll interval device exceeds the poll
interval defined in the network element configuration file. The
probable cause is due to improper engineering of the polling
parameters: timeout, number of retry, and poll interval.
location, and in the next 4-bytes, the actual poll interval.
Comment text contains: Polling frequency overrun.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 54 -
Proxy alarms
5004 0007
Network major set
Legend none
Details The SNMP trap message received contains a MIB variable that
the SNMP Integrator cannot translate into a symbolic form.
Operator data contains the MIB variable in a numeric format.
For example, the MIB variable 1.2.3.4 will be shown as
01020304.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 55 -
Proxy alarms
5004 0100
Software major set
Legend none
Details The RTR X25 link named in this alarm has gone down. Check
whether the device has been shut down on purpose. If not,
check the physical connection first, then the network path to this
device.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 56 -
Proxy alarms
5004 0101
Software major set
Legend none
Details The RTR X25 link named in this alarm has gone into testing
mode. The interface should be considered unavailable for
operational data.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 57 -
Proxy alarms
5004 0102
Software major set
Legend none
Details The RTR FR link named in this alarm has gone down. Check
device.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 58 -
Proxy alarms
5004 0103
Software major set
Legend none
Details The RTR FR link named in this alarm has gone into testing
operational data.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 59 -
Proxy alarms
5004 0104
Software major set
Legend none
Details The RTR EPO link named in this alarm has gone down. Check
device.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 60 -
Proxy alarms
5004 0105
Software major set
Legend none
Details The RTR EPO link named in this alarm has gone into testing
operational data.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 61 -
Proxy alarms
5004 0106
Software major set
Legend none
Details The HUB EPO link named in this alarm has gone down. Check
device.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 62 -
Proxy alarms
5004 0107
Software major set
Legend none
Details The HUB EPO link named in this alarm has gone into testing
operational data.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 63 -
Proxy alarms
5004 0108
Software major set
Legend none
Details The BR EPO link named in this alarm has gone down. Check
device.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 64 -
Proxy alarms
5004 0109
Software major set
Legend none
Details The BR EPO link named in this alarm has gone into testing
operational data.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 65 -
Proxy alarms
5004 0110
Software major set
Legend none
Details The SLAN SBR B_EPO link named in this alarm has gone
down. Check whether the device has been shut down on
purpose. If not, check the physical connection first, then the
network path to this device.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 66 -
Proxy alarms
5004 0111
Software major set
Legend none
Details The SLAN SBR B_EPO link named in this alarm has gone into
testing mode. The interface should be considered unavailable
for operational data.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 67 -
Proxy alarms
5004 0112
Software major set
Legend none
Details The SLAN SHUB H_EPO link named in this alarm has gone
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 68 -
Proxy alarms
5004 0113
Software major set
Legend none
Details The SLAN SHUB H_EPO link named in this alarm has gone into
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 69 -
Proxy alarms
5004 0114
Software major set
Legend none
Details The SLAN PRT P_EPO link named in this alarm has gone
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 70 -
Proxy alarms
5004 0115
Software major set
Legend none
Details The SLAN PRT P_EPO link named in this alarm has gone into
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 71 -
Proxy alarms
5004 0116
Software major set
Legend none
Details The SLAN FS F_EPO link named in this alarm has gone down.
Check whether the device has been shut down on purpose. If
not, check the physical connection first, then the network path
to this device.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 72 -
Proxy alarms
5004 0117
Software major set
Legend none
Details The SLAN FS F_EPO link named in this alarm has gone into
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 73 -
Proxy alarms
5004 0118
Software major set
Legend none
Details The SLAN WS W_EPO link named in this alarm has gone
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 74 -
Proxy alarms
5004 0119
Software major set
Legend none
Details The SLAN WS W_EPO link named in this alarm has gone into
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 75 -
Proxy alarms
5004 0120
Software major set
Legend none
Details The SLAN SRTR R_X25 link named in this alarm has gone
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 76 -
Proxy alarms
5004 0121
Software major set
Legend none
Details The SLAN SRTR R_X25 link named in this alarm has gone into
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 77 -
Proxy alarms
5004 0122
Software major set
Legend none
Details The SLAN SRTR R_EPO link named in this alarm has gone
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 78 -
Proxy alarms
5004 0123
Software major set
Legend none
Details The SLAN SRTR R_EPO link named in this alarm has gone into
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 79 -
Proxy alarms
5004 0124
Software major set
Legend none
Details The SLAN SRTR R_FR link named in this alarm has gone
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 80 -
Proxy alarms
5004 0125
Software major set
Legend none
Details The SLAN SRTR R_FR link named in this alarm has gone into
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 81 -
Proxy alarms
5004 0126
Software major set
Legend none
Details The ERTR S_X25 link named in this alarm has gone down.
to this device.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 82 -
Proxy alarms
5004 0127
Software major set
Legend none
Details The ERTR S_X25 link named in this alarm has gone into testing
operational data.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 83 -
Proxy alarms
5004 0128
Software major set
Legend none
Details The ERTR S_FR link named in this alarm has gone down.
to this device.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 84 -
Proxy alarms
5004 0129
Software major set
Legend none
Details The ERTR S_FR link named in this alarm has gone into testing
operational data.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 85 -
Proxy alarms
5004 0130
Software major set
Legend none
Details The ERTR EPO link named in this alarm has gone down. Check
device.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 86 -
Proxy alarms
5004 0131
Software major set
Legend none
Details The ERTR EPO link named in this alarm has gone into testing
operational data.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 87 -
Proxy alarms
5004 8888
<deviceType>/<deviceName> major set
Legend <deviceType> is the device type in ASCII (e.g. RTR)

<deviceName> is the device name in ASCII
Details The device is not responding to a PING command by the SNMP
Integrator within the specified time period.
Probable cause
Type
Remedial action Verify that the device is UP and/or reachable from the
workstation that is running the SNMP Integrator. If the device is
UP and reachable, verify that the TIMEOUT value for this
device, as defined in the network element file, is large enough
to allow the device to respond.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 88 -
Proxy alarms
5004 FFFF
<deviceType>/<deviceName> cleared clear
Legend <deviceType> is the device type in ASCII (e.g. RTR)

<deviceName> is the device name in ASCII
Details The device has responded to an initial PING command by the
SNMP Integrator, or a sysReset trap has been received by the
SNMP Integrator.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 89 -
Proxy alarms
6000 0001
NMS/<w/s name> MDP<application name> critical message
Legend <w/s name> is the name of the MDP workstation that generated
the error
<application name> is the name of the MDP process that
generated the error
Details The indicated process cannot open an input file.
Probable cause
Type
Remedial action Ensure that the indicated file exists and has adequate
permissions.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 90 -
Proxy alarms
6000 0005
the error
generated the error
Details The indicated process cannot open an output file.
Probable cause
Type
Remedial action Ensure that the parent directory of the output file has adequate
permissions and that sufficient disk space is available.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 91 -
Proxy alarms
6000 0010
the error
generated the error
Details The indicated process cannot open a configuration file.
Probable cause
Type
Remedial action Ensure that the indicated file exists and has adequate
permissions. If the indicated file does not exist, refer to Nortel
Multiservice Data Manager FundamentalsMDP Data
Collection (NN10470-309) for information about configuring the
indicated process.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 92 -
Proxy alarms
6000 0015
the error
generated the error
Details The indicated process is providing critical information.
Probable cause
Type
Remedial action No action is required.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 93 -
Proxy alarms
6000 0020
the error
generated the error
Details The indicated process cannot access the indicated directory.
Probable cause
Type
Remedial action Ensure that the indicated directory exists and has adequate
permissions. If the indicated directory does not exist and should
be under /opt/MagellanMDP, use the MDP Flexible Directory
Installation application gmdpinst to re-install the missing
directory.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 94 -
Proxy alarms
6000 0025
the error
generated the error
Details The indicated process cannot access the indicated directory.
Probable cause
Type
Remedial action Ensure that the indicated directory exists and has adequate
permissions. If the indicated directory does not exist and should
be under /opt/MagellanMDP, use the MDP Flexible Directory
Installation application gmdpinst to re-install the missing
directory.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 95 -
Proxy alarms
6000 0030
the error
generated the error
Details The indicated process expected to find a directory but instead
found a file.
Probable cause
Type
Remedial action If this is as a result of a command line parameter, re-run the
command and specify the correct directory. If the indicated
directory should be under /opt/MagellanMDP, use the MDP
Flexible Directory Installation application gmdpinst to re-install
the directory.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 96 -
Proxy alarms
6000 0035
the error
generated the error
Details The indicated process cannot close the indicated file.
Probable cause
Type
Remedial action Ensure that sufficient disk space is available.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 97 -
Proxy alarms
6000 0040
the error
generated the error
Details The indicated process has encountered an invalid file name
format.
Probable cause
Type
Remedial action To determine the correct file name format, refer to Nortel
Multiservice Data Manager FundamentalsMDP Data
Collection (NN10470-309).

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 98 -
Proxy alarms
6000 0045
the error
generated the error
Details The indicated process has made a system call to the operating
system and the system call has failed.
Probable cause
Type
Remedial action Refer to the message details.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 99 -
Proxy alarms
6000 0100
the error
generated the error
Details The userID used to run this process was not a valid MDP user.
Probable cause
Type
Remedial action Run the process using a valid userID.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 100 -
Proxy alarms
6000 0105
the error
generated the error
Details The process cannot determine the userID of the current user.
Probable cause
Type
Remedial action Run the process using a valid userID.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 101 -
Proxy alarms
6000 0106
the error
generated the error
Details The process cannot determine the identity of the MDP
administrator.
Probable cause
Type
Remedial action The MDP administrator is assumed to be the owner of the
directory
/opt/MagellanMDP/cfg/mdp. Ensure that this directory is
accessible and is owned by the MDP administrator.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 102 -
Proxy alarms
6000 0110
the error
generated the error
Details The process cannot use the MDP administrator userID or
group.
Probable cause
Type
Remedial action Ensure that a valid MDP administrator userID and group have
been created.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 103 -
Proxy alarms
6000 0120
the error
generated the error
Details Another instance of this process is running. Some MDP
processes can have only one instance running, to preserve file
integrity.
Probable cause
Type
Remedial action Stop the first instance of a process before starting another.
Issue the command 'ps -ef | grep <process name>' to check the
running processes.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 104 -
Proxy alarms
6000 0121
the error
generated the error
Details The MDP Disk Manager is not running. The MDP Disk Manager
must be running before the MDP File Managers can start.
Probable cause
Type
Remedial action Configure the MDP Disk Manager using the MDP configuration
application gmdpconfig.
If the MDP Disk Manager is configured but not started, start the
MDP Disk Manager using the MDM Server Administration
system. For more information about the MDM Server
Administration system, see Nortel Multiservice Data Manager
Administration (NN10470-303).

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 105 -
Proxy alarms
6000 0150
the error
generated the error
Details A valid MDP software license cannot be found. The license may
have expired or the license file may be corrupt.
Probable cause
Type
Remedial action Contact your Nortel Customer Support to get a new license.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 106 -
Proxy alarms
6000 0200
the error
generated the error
Details The indicated process has aborted due to a received signal.
Probable cause
Type
Remedial action Restart the process.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 107 -
Proxy alarms
6000 0220
the error
generated the error
Details The indicated process has a command line error.
Probable cause
Type
Remedial action Use the option -help to determine the correct command line
syntax.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 108 -
Proxy alarms
6000 0300
the error
generated the error
Details The indicated process has encountered a configuration error.
The configuration file for this process is corrupt or contains an
invalid value.
Probable cause
Type
Remedial action Configure the process using the MDP configuration application
gmdpconfig.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 109 -
Proxy alarms
6000 0320
the error
generated the error
Details A module file is corrupt.
Probable cause
Type
Remedial action Re-run the MDP Topology Generator.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 110 -
Proxy alarms
6000 0325
the error
generated the error
Details The indicated record description file (RDF) is corrupt.
Probable cause
Type
Remedial action If this is a user-defined RDF, inspect the RDF for errors.
If this is a default Nortel-supplied RDF, contact your Nortel
Customer Support.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 111 -
Proxy alarms
6000 0350
the error
generated the error
Details An error was encountered while decoding a record. The data
file is not compatible with the RDF.
Probable cause
Type
Remedial action Determine if the data file or the RDF are corrupt.
Ensure that the correct RDF is being used with the data file.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 112 -
Proxy alarms
6000 0400
the error
generated the error
Details An invalid group name has been specified.
Probable cause
Type
Remedial action Specify a valid group name.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 113 -
Proxy alarms
6000 1000
the error
generated the error
Details The indicated process cannot open the schema file database.
Probable cause
Type
Remedial action Ensure that the following directories have permissions of 755
and are owned by the MDP administrator: /opt/MagellanMDP/
data/mdp/db/<switch>/<datatype>.
Ensure that the schema files /opt/MagellanMDP/lib/mdp/
schema/<switch>/<datatype>/* are readable by the MDP
administrator userID.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 114 -
Proxy alarms
6000 1100
the error
generated the error
Details A raw input data file, received from a network element, is
corrupt.
Probable cause
Type
Remedial action Contact your Nortel Customer Support.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 115 -
Proxy alarms
6000 2000
the error
generated the error
Details The data model being parsed is corrupt.
Probable cause
Type
Remedial action Re-run the process that produced this error using a new data
model (or run using a different Multiservice Switch). If the error
persists, contact your Nortel Customer Support.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 116 -
Proxy alarms
6000 2010
the error
generated the error
Details The indicated process could not determine the version of the
latest data model.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 117 -
Proxy alarms
6000 2015
the error
generated the error
Details A data model could not be found on the network element.
Probable cause
Type
Remedial action Attempt to run the Schema Generator using another data
model. If the error persists, contact your Nortel Customer
Support.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 118 -
Proxy alarms
6000 2030
the error
generated the error
Details The indicated record content file (RCF) is corrupt.
Probable cause
Type
Remedial action Update the indicated RCF with corrected content.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 119 -
Proxy alarms
6000 2050
the error
generated the error
Details The specified directory already exists.
Probable cause
Type
Remedial action Re-run the process using a different directory or remove the
specified directory.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 120 -
Proxy alarms
6000 2100
the error
generated the error
Details Errors have occurred while downloading a data model from the
Multiservice Switch.
Probable cause
Type
Remedial action Ensure connectivity to the network element and ensure that the
Multiservice Switch userID and password have the necessary
permissions.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 121 -
Proxy alarms
6000 2110
the error
generated the error
Details The indicated process cannot uncompress/untar the indicated
file.
Probable cause
Type
Remedial action Ensure that the permissions of the indicated file and the parent
directory are sufficient. Ensure that sufficient disk space is
available.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 122 -
Proxy alarms
6000 2120
the error
generated the error
Details An invalid loadname was specified.
Probable cause
Type
Remedial action Specify a valid loadname.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 123 -
Proxy alarms
6000 2150
the error
generated the error
Details Fields specified in the RDF are missing in the corresponding
schema file.
Probable cause
Type
Remedial action Run /opt/MagellanMDP/bin/schemagen on the MSS data
model.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 124 -
Proxy alarms
6000 2500
the error
generated the error
Details The Multiservice Data Manager (MDM) software is not installed
correctly.
Probable cause
Type
Remedial action Re-install and configure the MDM software.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 125 -
Proxy alarms
6000 3000
the error
generated the error
Details The MDP Data Model Manager (mdpdmm) could not be
started.
Probable cause
Type
Remedial action Ensure that the port configured for use by the mdpdmm does
not conflict with other services.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 126 -
Proxy alarms
6000 3500
the error
generated the error
Details A problem has occurred while manipulating the MDP File Mover
.todo files.
Probable cause
Type
Remedial action Ensure that the file permissions of the .todo file in the directory
/opt/MagellanMDP/data/mdp/dump/<datatype> are sufficient.
Check for the retransmission of data files.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 127 -
Proxy alarms
6000 9000
the error
generated the error
Details The MDP software is not installed correctly.
Probable cause
Type
Remedial action Re-install the MDP software and run gmdpinst. If the error

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 128 -
Proxy alarms
6000 9010
the error
generated the error
Details The MDP workstation is out of memory.
Probable cause
Type
Remedial action Re-evaluate the engineering requirements for this workstation.
Temporarily, you can stop other processes and restart the
failed process.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 129 -
Proxy alarms
6000 9100
the error
generated the error
Details The indicated process has terminated with errors.
Probable cause
Type
Remedial action Refer to the log file for details.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 130 -
Proxy alarms
6000 9110
the error
generated the error
Details The schema database is corrupt.
Probable cause
Type
Remedial action If you are running the BDF Converter from the command line,
re-run the BDF Converter using the option -force. If the error

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 131 -
Proxy alarms
6000 9999
the error
generated the error
Details An internal error has occurred.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 132 -
Proxy alarms
6001 0000
NMS/<w/s name> MDP<application name> major message
the error
generated the error
Details An error has occurred.
Probable cause
Type
Remedial action This message is for information purposes, only. No action is
required.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 133 -
Proxy alarms
6001 0001
the error
generated the error
Details The indicated process cannot access the indicated file.
Probable cause
Type
Remedial action Ensure that the permissions of the indicated file are sufficient.
Ensure that sufficient disk space is available.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 134 -
Proxy alarms
6001 0045
the error
generated the error
Details A system call to the operating system has failed.
Probable cause
Type
Remedial action Refer to the log file for details.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 135 -
Proxy alarms
6001 0070
the error
generated the error
Details The File Prober failed to connect to the File Prober host.
Probable cause
Type
Remedial action Check the connectivity of the File Prober host and ensure that
the File Prober userID and password are correct.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 136 -
Proxy alarms
6001 0090
the error
generated the error
Details A file transfer failed to complete.
Probable cause
Type
Remedial action Retry the FTP transfer.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 137 -
Proxy alarms
6001 0100
the error
generated the error
Details The workstation failed to connect to the network element.
Probable cause
Type
Remedial action Ensure connectivity to the network element and ensure that the
Multiservice Switch userID and password have the necessary
permissions.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 138 -
Proxy alarms
6001 0174
the error
generated the error
Details Connectivity to the IMDR workstation has been lost.
Probable cause
Type
Remedial action Check connectivity to the IMDR host. Ensure that the IMDR is
active on either the local MDP workstation or the Multiservice
Data Manager workstation specified in the MDP Surveillance
window.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 139 -
Proxy alarms
6001 0320
the error
generated the error
Details A module file is corrupt.
Probable cause
Type
Remedial action Re-run the MDP Topology Generator.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 140 -
Proxy alarms
6001 0500
the error
generated the error
Details A data conversion has failed.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 141 -
Proxy alarms
6001 0550
the error
generated the error
Details This message provides a summary of the number of error
records in a raw data file.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 142 -
Proxy alarms
6001 0700
the error
generated the error
Details A duplicate raw data file has been received from the network
element.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 143 -
Proxy alarms
6001 0900
NMS/<w/s name> MDP<application name> major set
Dir<directory name>
cleared clear
the error
generated the error
<directory name> is the name of the directory
Details Available disk space for the indicated directory is insufficient to
continue processing.
Probable cause
Type
Temporarily, you can remove files on the disk to increase
available disk space.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 144 -
Proxy alarms
6001 1000
the error
generated the error
Details The BDF file format is invalid.
Probable cause
Type
Remedial action If the BDF file was updated or corrupted after conversion,
recreate the BDF file from the raw data file. If the BDF file was
not manually updated, contact your Nortel Customer Support.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 145 -
Proxy alarms
6001 1500
the error
generated the error
Details A field exists in the original RDF but not in the data model being
parsed.
Probable cause
Type
Remedial action Ensure that the data model is the latest available data model.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 146 -
Proxy alarms
6001 2000
the error
generated the error
Details There was a problem with FMIP communication between the
MDP workstation and a network element.
Probable cause
Type
Remedial action If the problem persists, contact your Nortel Customer Support.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 147 -
Proxy alarms
6001 2500
the error
generated the error
Details The specified component does not exist.
Probable cause
Type
Remedial action Either the component name is incorrect or the component is not
provisioned on the network element.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 148 -
Proxy alarms
6001 3000
the error
generated the error
Details Due to traffic congestion, the network element is too busy to
send polled information.
Probable cause
Type
Remedial action Increase the polling interval or reduce the number of
components polled.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 149 -
Proxy alarms
6001 4000
the error
generated the error
Details A record in a raw data file is corrupt.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 150 -
Proxy alarms
6001 4100
the error
generated the error
Details The schema database is corrupt.
Probable cause
Type
Remedial action Stop and re-start the File Manager. If you are running the BDF
Converter from the command line, re-run using the option -
force. If the problem persists, contact your Nortel Customer
Support.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 151 -
Proxy alarms
6001 9011
the error
generated the error
Details A cronjob error has occurred.
Probable cause
Type
Remedial action Ensure that the MDP administrator userID is able to create/
delete a cronjob.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 152 -
Proxy alarms
6001 9098
the error
generated the error
Details The indicated process has made a system call to the operating
system and the system call has failed.
Probable cause
Type
Remedial action Refer to the message details.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 153 -
Proxy alarms
6001 9099
the error
generated the error
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 154 -
Proxy alarms
6001 9999
the error
generated the error
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 155 -
Proxy alarms
6002 0000
NMS/<w/s name> MDP<application name> warning message
the error
generated the error
Details This message is for information purposes, only.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 156 -
Proxy alarms
6002 0900
the error
generated the error
Details The available disk space will soon be insufficient to continue
processing.
Probable cause
Type
Temporarily, you can remove files on the disk to increase
available disk space.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 157 -
Proxy alarms
6002 1000
the error
generated the error
Details An unknown attribute was encountered in a raw data file.
Probable cause
Type
Remedial action Run schemagen.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 158 -
Proxy alarms
6002 1020
the error
generated the error
Details Corrupt records were encountered during processing.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 159 -
Proxy alarms
6002 2000
the error
generated the error
Details The current MDP configuration does not enable processing of
the indicated file types.
Probable cause
Type
Remedial action If you do not require processing of the indicated file types,
ignore this message. If you require processing of the indicated
file types, reconfigure the MDP software to perform this
processing.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 160 -
Proxy alarms
6002 2030
the error
generated the error
Details The indicated record content file (RCF) is corrupt.
Probable cause
Type
Remedial action Update the indicated RCF with corrected content.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 161 -
Proxy alarms
6002 3000
the error
generated the error
Details Due to traffic congestion, the network element is too busy to
send polled information.
Probable cause
Type
Remedial action Increase the polling interval or reduce the number of
components polled.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 162 -
Proxy alarms
6003 0000
the error
generated the error
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 163 -
Proxy alarms
6003 0001
the error
generated the error
Details The MDP has begun processing of the indicated raw data file.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 164 -
Proxy alarms
6003 0002
the error
generated the error
Details The MDP has successfully completed processing of the
indicated raw data file.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 165 -
Proxy alarms
6003 0010
the error
generated the error
Details The MDP has completed processing of the indicated raw data
file. Errors were encountered. This message indicates the
number of errors encountered.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 166 -
Proxy alarms
6003 0020
the error
generated the error
Details This message indicates the number of: records, unsupported
records, and error records found in a file.
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 167 -
Proxy alarms
6004 0000
the error
generated the error
Probable cause
Type

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 168 -
Proxy alarms
7042 0004
Lp/<num1> <type>/<num2> major/cleared set/clear
Legends <num1> = 0 - 15
<type> = DS3, E1, DS1, SONET, and SDH
<num2> = 0 - n, where n is 1 less than the number of
ports supported on the card type
Details When one CES connection is failed, the set alarm will
be raised against the CES interface that the CES
connection relates to.
The alarm is cleared when all connections associated
with the CES interface are back in service.
Probable cause VC inactive
Type Communications
Remedial action Check the connectionStatus of CES connection that is
associated with the physical port. If the
connectionStatus is atmNotReady, check the ATM
network.
If the connectionStatus is channelNotReady, check
the physical port or logical port associated with
Aal1Ces.
If the connectionStatus is atmNotConfigured, check
the configuration of aal1Ces subcomponent.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 169 -
Proxy alarms
A0XX XXXX

Details For customers who decide to use the Inbound alarm and status
Application Programming Interface (IAPI) or Injected
Management Data Router (IMDR) to inject alarms into Nortel
Multiservice Data Manager, they are recommended to use this
range of alarms to indicate an alarm arriving from their system.
This range is from A000 0000 to A0FF FFFF. Customers can
build their own alarms document and include it into this
document so that their alarms can be found.
We recommend that the xx of A0xx 0000 be used to signify the
device type to which the alarm refers. This will allow for better
identification of the device type that failed.
In addition the xxxx of A000 xxxx be used to signify the specific
failure.
Please refer to the specific documentation for details on the
alarm.
Probable cause
Type
Remedial action Refer to the product-specific documentation for fault correction
steps.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 170 -
Proxy alarms
B000 BXXX

Details For custom development, for example, for Meridian view.
Please refer to the specific documentation for details on the
alarm.
Probable cause
Type
Remedial action Refer to the product-specific documentation for fault correction
steps.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 171 -
Proxy alarms
CDXX XXXX
Legend CD means customer-defined

XX XXXX is the value that you assign to an alarm fault code
The first two numbers (<xx>) should match the device type
value for the device being managed.
Details This alarm code is a template for the customer to use to define
alarms. The SNMP Surveillance Adapter allows you to create
alarm codes and descriptions in the Nortel Multiservice Data
Manager. See the section on adding a description for a new
alarm code in the Nortel Multiservice Data Manager Fault
ManagementTools (NN10470-011).
Probable cause
Type
Remedial action

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
Generic SNMP alarms
This chapter describes the generic SNMP device alarms supported by the
Nortel Multiservice Data Manager.
Generic alarm codes

The following table describes the generic alarm code prefixes:
Generic alarm code prefixes
Code range Supported device

C000 Generic SNMP devices
CDXX XXXX Customer-defined alarms. For more information
about customer-defined alarms, see Nortel
Multiservice Data Manager Fault Management
Tools (NN10470-011).

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 173 -
Generic SNMP alarms
C000 0000
<device type>/<device name> warning set
minor set
major set
critical set
cleared clear
Legend <device type> is the type of device.

<device name> is the name of the device that has issued the
corresponding SNMP trap.
Details The trap ColdStart indicates that the system has restarted after
a power shutdown.
Some, but not all, SNMP devices use trap accumulation
strategies for raising this trap severity level. If the device is
using a trap accumulation strategy, a message indicating the
number of traps generated during the previous polling interval
is displayed. For example,
Received, count = cc repeated cold start traps in the last mm
minutes.
where:
cc = the number of traps received
mm = the number of minutes in the polling interval
For those SNMP devices that use a trap accumulation strategy,
if repeated cold start traps occur within a components SNMP
state polling interval, the alarm severity may be raised
accordingly. The number of repeated trap instances and the
alarm severity are indicated in the Alarm Display using Normal
or Full alarm format. The accumulation strategies may vary for
different SNMP devices.
For those SNMP devices that do not use a trap accumulation
strategy, multiple cold start trap instances are indicated in the
Alarm Log and the alarm severity remains as warning.
Probable cause operational condition
Type operator
Remedial action No remedial action is necessary.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 174 -
Generic SNMP alarms
C000 0001
<device type>/<device name> warning set
minor set
major set
critical set
cleared clear

Details The trap WarmStart indicates that the system has started
without a power shutdown.
Received, count = cc repeated warm start traps in the last mm
minutes.
where:
if repeated warm start traps occur within a components SNMP
state polling interval, the alarm severity may be raised
accordingly. The number of repeated trap instances and the
alarm severity are indicated in the Alarm Display using Normal
or Full alarm format. The accumulation strategies may vary for
different SNMP devices.
strategy, multiple warm start trap instances are indicated in the
Alarm Log and the alarm severity remains as warning.
Probable cause operational condition
Type operator
Remedial action If the trap is caused by administrative action, no remedial action
is necessary. Otherwise, contact your Nortel representative.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 175 -
Generic SNMP alarms
C000 0002
<device type>/<device name> IF/<IF name> major set
critical set
cleared clear

<IF name> is the interface port.
Details This trap indicates that a link is down. This trap is probably
caused by a local transmission error.
For devices monitored by Nortel Multiservice Data Manager
generic DCD (GENDCD), the Link Down trap is reported as a
critical or major set alarm depending on the cartridge
implementation.
When Multiservice Data Manager receives the Link Up trap, this
is reported as a clear alarm.
Probable cause loss of signal
Type communications
Remedial action Check the link status to determine the cause of the problem.
There can be multiple causes for this trap. Analyze the statistics
to determine if this is a physical connection problem such as a
disconnected or broken cable or a configuration problem such
as unmatched far-end and near-end parameters.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 176 -
Generic SNMP alarms
C000 0004
<device type>/<device name> SECURITY warning message
warning set
minor set
major set
critical set
cleared clear

Details Trap Authentication indicates that an attempt was made to
access the device with the wrong SNMP community name.
Received, count = cc repeated authentication failure traps in
the last mm minutes.
where:
if repeated authentication failure traps occur within a
components SNMP state polling interval, the alarm severity
may be raised accordingly. The number of repeated trap
instances and the alarm severity are indicated in the Alarm
Display using Normal or Full alarm format. The accumulation
strategies may vary for different SNMP devices.
strategy, multiple authentication failure trap instances are
indicated in the Alarm Log and the alarm severity/status
remains as warning/message.
Probable cause authentication failure
Type security
Remedial action Take appropriate security actions.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
- 177 -
Generic SNMP alarms
C001 9999
GEN/<device name> indeterminate message
Legend <device name> is the name of the device that has issued the
Details A device specific trap has been received for which the generic
SNMP device driver has no translation.
Type unknown
Remedial action Take appropriate action for the specific trap received.

Alarms Reference
NN10470-501 01.02 Standard
16.2 May 2007
Alarms Reference
Copyright 2007 Nortel Networks, All Rights Reserved
Sourced in Canada and the United States of America.
Publication: NN10470-501
Document status: Standard
Document issue: 01.02
Document date: May 2007
Product release: 16.2
Job function: Fault and Performance Management
Type: NTP
Language type: U.S. English
Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback.

Alarms Reference: Nortel Multiservice Data Manager

Uploaded by

Document Informationclick to expand document informationldfkdfl

Document Informationclick to expand document information

Copyright:

Available Formats

Alarms Reference: Nortel Multiservice Data Manager

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alarms Reference: Nortel Multiservice Data Manager

Uploaded by

Copyright:

Available Formats

Nortel Multiservice Data Manager

Sourced in Canada and the United States of America.

Copyright 2007 Nortel Networks. All Rights Reserved

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Disabling the generation of proxy alarms

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Legend <deviceType> is the type of network element

Nortel Multiservice Data Manager

Legend <deviceType> is the type of network element

Nortel Multiservice Data Manager

Legend <deviceType> is the type of network element

Nortel Multiservice Data Manager

Legend <component id> is the name of any DPN component that

Nortel Multiservice Data Manager

Legend <deviceType> is the network element type managed by IMDR

Nortel Multiservice Data Manager

Legend <component id> is the name of any MSS component

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Legend <deviceType> is the type of network element

Nortel Multiservice Data Manager

Legend <deviceType> is the type of network element

Nortel Multiservice Data Manager

Legend <deviceType> is the type of network element

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Legend <w/s name> is the name of the workstation generating the

Nortel Multiservice Data Manager

Legend <w/s name> is the name of the workstation generating the

Nortel Multiservice Data Manager

Legend <w/s name> is the name of the workstation generating the

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Legend <w/s name> is the name of the workstation generating the

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Legend <w/s name> is the name of the workstation generating the

Nortel Multiservice Data Manager

Legend <w/s name> is the name of the workstation generating the

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Legend <w/s name> is the name of the workstation generating the

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager

Nortel Multiservice Data Manager