Avaya BCM3.x User Manual

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

Revision History

Rev # Date Changes/Comments

0.1 2/18/2004 Changed to new numbering format. Carried over older 2.2.3k list.

0.5 3/9/2004

1.0 3/12/2004 Added comment to Modem 52 alarm

1.1 3/12/2004

1.2 3/15/2004

1.3 3/17/2004

1.4 3/22/2004

1.5 3/24/2004

2.0 5/17/2004

Added version history, removed BCM 3.5 top alarms tab as it can be sorted from BCM Alarms-Trap tab.

Initial issue for BCM 3.6. Included new mspqosmp, SRG, NetIQ, and voice software alarms Updated SRG alarms to correct descriptions, Added new comments to perctrs event Removed Microsoft References in Comments (Q00865725) and added Print formatting Updated UPS Alarms to actual alarms found during testing. Removed working red/green colors. Updated Summary tab.

This is the issued version for BCM 3.6. Updated test results with latest PV checklist information. Updated SSM Events 1007, 2008 and 3015 added comments around CR Q00880476 as well took them off the top alarm list. Added UPS 1300 and 1320 and removed 1016. Added TCPIP event ID

4198. Added 4 generic SNMP only traps to the list. Updated summary tab.

2.1 8/29/2005 Upissued to include BCM 3.7 (no new alarms comparing to BCM 3.6). Changed name to better reflect the scope of this document

11/14/2005

3.0e

("BCM35_Alarms_SNMPTraps…" changed to "BCM_3.x_Alarms_SNMPTraps…")

Revisions Page 1

Top Alarms

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

Summary and Definitions of Alarm Totals

BCM 3.0X 88 BCM 3.5 73 BCM 3.6 74 BCM 3.7 74

Current Release Top Alarm Total

SSM Alarms Voice Software T1 Alarms Voice Watchdog Alarms UPS Alarms Service Control Manager Alarms BRU Alarms NetLink Manager Alarms NGRPCI Alarms QoS Monitor Alarms VoiceCTI VoIP Gateway Alarm UTPS Alarms Tcpip Alarms SRG Alarms Security Alarms Save Dump Alarms

74 Comments 19 Platform, Hardware, Environmental alarms. (ie. Fan failure) 18 T1/PRI error condition alarms.

9 Nortel Networks services failure and status alarms. 5 Power outage alarms. 3 OS Related service failure and status alarms. 2 Backup and Restore Alarms. 2 Default IP route and dial backup alarms. 2 LAN Up/Down Alarms. 2 VoIP Fallback Alarms. 2 Voice Mail/ACD port busy and filesystem full alarms. 1 IP Trunk dropped call alarm. 1 Packet Loss to IP Set alarm. 1 Duplicate IP address alarm. 1 Loss of main office alarm. 1 Incorrect login alarm. 1 OS level diagnostic alarm.

Summary Page 2

1

e

2

3 4

5 6

7

8

9

10

11

12

13 14

15

16

17 18 19

20 21 22

23 24

25 26 27

28 29 30 31 32 33

34 35

36 37 38

39 40 41

ABCD E F G HIJKLM

Component ID (Alarm)

eventSource (Trap)

atapi

Autochk

BcmAmp BcmAmp BcmAmp

BcmAmp

BROWSER

BRU 300

BRU 301

BRU 302

BRU 303

BRU 304 BRU 305

BRU 306

BRU 307

BRU 308 BRU 309

BRU 310

BRU 311

BRU 312 BRU 313

BRU 314

BRU 315 CDRTransfer

CDRTransfer

CDRTransfer CDRTransfer CDRTransfer

CDRTransfer

CDRTransfer CDRTransfer

CDRTransfer

42

Event ID (Alarm)

eventId (Trap)

9

1001

257 258

771

772

773

774

775

8021

8033

2088

3087

3087 3088

3088 3088

3088

3088 3088 3088

3088

3090

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error The device, \Device\ScsiPort0, did not respond within the timeout

warning Information Checking file system on <drive>: The type of the file system is … No action required.

warning Information BcmAmp version %s has started. None warning Information Shutdown Complete None critical Error IP Music Error: Integrated MOH player -malformed songs.cfg file.

critical Error IP Music Error: Integrated MOH player - unable to initialize network

critical Error IP Music Error: Integrated MOH player - initialization error. Unable to

critical Error IP Music Error: Integrated MOH player - initialization failure. Service

critical Error IP Music Error: Integrated MOH player - unable to allocate resources.

minor Warning The browser was unable to retrieve a list of servers from the browser

warning Information The browser has forced an election on network

warning Information BRU Backup Starting No action required. warning Information Backup finished successfully No action required.

minor Warning Backup finished with warnings. Warnings were logged in

critical Error Backup finished with errors. Errors were logged in

warning Information BRU Restore Starting No action required. warning Information Restore finished successfully. No action required. minor Warning Restore finished with warnings. Warnings were logged in BRURest.log

critical Error Restore finished with errors. Errors were logged in BRURest.log and

critical Error An error has occurred when trying to access the UTPS pipe. During BRU activity, IP sets may reset. No action necessary.

warning Information BRU has increased set watchdog from 30 sec to 15 minutes. No action required. warning Information BRU has decreased set watchdog from 15 minutes to 30 sec. No action required. critical Error An error %RetV% has occurred when trying to start the voice services.Review voice services and restart if necessary through Unifi

warning Information All voice mail services have been started. No action required. warning Information All voice mail services have been stopped. No action required. critical Error Error: %DriveType% drive not connected. Ensure destination drive is visible on the network and that

critical Error Error: %DriveType% drive not connected. %MapPath% not found. Ensure destination drive is visible on the network and that

minor Warning Not Push Check if there are actual CDR data files under the CDR data

minor Warning No more CDR data files!!! Check if there are actual CDR data files under the CDR data

critical Error ZpInit() error!!! Check if Zip32.dll is installed properly under the CDRTransfer

critical Error ZpSetOpt() error!!! Check if Zip32.dll is installed properly under the CDRTransfer

critical Error Can't open reg key err = %1 Check if CDRTransfer registry entries are damaged. critical Error Can't get current dir err = %1 Check if you have permission to get current directory. critical Error Can't change to working dir err = %1 Check if you have permission to go to CDRTransfer working

critical Error Clip CDR data file error err = %1 Check if CDRClip.exe is installed properly under the CDR

critical Error Find CDR data file error err = %1 Check if there are CDR data files under CDR data file

critical Error Can't get FTP connection err = %1 Check if FTP configuration or network goes wrong. critical Error Can't go to remote dir on FTP server err = %1 Check if permission of destination directory on the client PC i

critical Error ZpArchive() err = %1 Check if Zip32.dll is installed properly under the CDRTransfer

critical Error Multiple instances are running, exit! Means multiple CDRTransfer instances are running

period.

Unable to proceed, service shutting down.

connection. Service shutting down.

proceed. Service shutting down.

shutting down.

Service shutting down.

master <PDC> on the network \device\<protocol_netcard>. The data is the error code.

\device\<protocol_netcard> because a master browser was stopped.

%DESTINATION_NAME%.rep on the destination.

and %~n0.rep.txt on the source.

%~n0.rep.txt on the source.

For the drives in question, these timeout message are not serious if they occur at system boot. However, if several of these messages appear in the system log during normal system operation, they should be investigated. Please then contact Nortel Networks support team.

Please disable the BcmAmp player by configuring your IP Music source as either: Audio Jack or Network Audio. Contact Customer Support for further assistance.

If stopping and starting the IP Music service via the Unified Manager fails to rectify the problem, please disable the IP Music service and contact Customer Support for further assistance.

Check the network setup.

No action required.

Review log files to determine FAILED component. Take corrective action if necessary and retry backup.

No action required.

Review log files to determine FAILED component. Take corrective action if necessary and retry restore.

Manager. See service specific logs for cause of failure.

correct permissions are set.

file directory.

directory.

granted to CDRTransfer.

directory.

simultaneously, but only one survives. No action is required.

Top Alarms

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No Yes Yes Yes Yes

No No No No No No

Yes No No No No No Yes No No No No No

Yes No No No No No

No No No No No No

No No No Yes Yes Yes

No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No No No No No No No

No No No No No No

Yes No No No No No

BCM Alarms-Traps Page 3

Component ID (Alarm)

A

E

h

2

43

CDRTransfer

44

CDRTransfer

45

CDRTransfer CDRTransfer

46

cfsServer

47

cfsServer

48

cfsServer

49

cfsServer

50

cfsServer

51

cfsServer

52

cfsServer

53

cfsServer

54

cfsServer

55

cfsServer

56

cfsServer

57

cfsServer

58

cfsServer

59

cfsServer

60

cfsServer

61

cfsServer

62

cfsServer

63

cfsServer

64

CTE

65

CTE

66 67

CTE DCOM

68

DCOM

69

DCOM

70

DCOM

71

DCOM

72 73

DECTAlarms DECTAlarms

74 75

DECTAlarms

76

DECTAlarms

77

DECTAlarms

78

DECTAlarms

79

DECTLoad

80

DECTLoad

81

DECTMtce

82

DECTMtce

83

DECTMtce

84

DECTMtce

85

DECTMtce

86

DECTMtce

87

DECTMtce

88

DECTMtce

89

DECTMtce

90

DECTMtce

91

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

3090 3090 3090

3090

100 101 105 108 109

110

111

113 114

115

116

117

118 119 122

123 125

126

257

258

10001

10002

10004

10005

10010

256 256 512

512 512 512 512 512 256

256

256 256 256

256 256

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error Can't Get the value of %1 err= %2 Check if CDRTransfer registry entries are damaged. critical Error Can't transfer file %1 err= %2 Check if FTP configuration or network goes wrong. critical Error Can't delete CDR data file transferred %1 err= %2 Check if you have permission to delete this file. critical Error Can't -A CDR data file transferred %1 err= %2 Check if you have permission to change the attribute of this

warning Information The service was installed. No action required. warning Information The service was removed. No action required. warning Information The service was started. No action required. warning Information The service was stopped. No action required. critical Error <error string provided by CFS> No action required. warning Information Duplicate keycode has been entered - this keycode has been previously

critical Error Keycode <keycode value> is invalid. Confirm that the keycode was entered correctly and that the

warning Information Verification of System Licensing in progress. No action required. warning Information Verification of System Licensing completed. No action required. critical Error Verification of system licensing failed due to error: <error Information> Specific to error Information.

warning Information Keycode <keycode value> applied. <Component-defined string>

critical Error Unable to apply keycode: <keycode value>. The service associated with the keycode is not running

warning Information Processing of keycode input file in progress. No action required. warning Information Processing of keycode input file completed. No action required. warning Information Trial has expired. No action required. critical Error Error applying keycode: <keycode value> <Information from

critical Error Error applying keycode: <keycode value>. No action required. warning Information <Trial functionality> expired. No action required. critical Error Changes have been detected in the KSU configuration. Restart all TAPI

minor Warning

minor Warning KSU connection is down all devices are disabled. No action required. critical Error Unable to start a DCOM Server: %3 as %4/%5.\r\nThe

critical Error Access denied attempting to launch a DCOM Server. The server is:

critical Error DCOM got error "Logon failure: unknown user name or bad password "

critical Error DCOM got error "The specified service is disabled and cannot be

critical Error The server {1338C620-888C-11D2-8F01-0080C79B65A2} did not

critical Error Run - Unexpected condition. Error Contact Customer Support warning Information 01:10:03.694 [DECT Alarm Monitor:4.]DECT Alarm Manager Started No action required.

critical Error OnInit - Failed to create alarm monitoring thread Contact Customer Support critical Error Run - Wait failed Contact Customer Support critical Error Failed to create CDectComPort object. Error Contact Customer Support critical Error Caught an exception creating CDectComPort Contact Customer Support critical Error Failed in DECT_StartDownload call Contact Customer Support critical Error Failed in DECT_StopDownload call Contact Customer Support critical Error MCService::OnInt: Bind socket to address failed. Error Contact Customer Support critical Error IOThread::ProcessEvent: Failed to set Release done API event. Error Contact Customer Support

critical Error MCService GetDectCfgKeyStr caught exception creating CDectCfg: Contact Customer Support

critical Error MCService CreateApiEvents: Create Release Event failed. API will fail.

critical Error MCServide CreateApiEvents: Create Release Done Event failed. API

critical Error MCService CreateApiEvents: Create Reconnect Event failed. API will

critical Error IOThread::InitComPort: Caught exception \"%s\" creating

critical Error MCService InitComPort: Error creating COM port Contact Customer Support critical Error MCService InitComPort caught exception creating CDectComPort: Contact Customer Support

critical Error MCService InitIOSocket failed to put socket into non-blocking mode.

critical Error MCService CloseSock failed with error Contact Customer Support

entered

activated.

component>

applications to use with the new configuration.

CTE application attempted to register with CTE before the Voice CT service had fully initialized ( error <error code> ). If the application is not behaving correctly restart it after the Voice CTE service has started. <RTR001>

error:%n"%%%2"%nHappened while starting this command:%n%1\r\n

{CF6B5196-5214-11D3-8A85-000000000000} The user is %2%3, SID=%4.

and was unable to logon <computer name>\ee_admin in order to run t server: {1338C614-888C-11D2-8F01-0080C79B65A2}

started. " attempting to start the service <Serive Name> with arguments "-Service" in order to run the server:

register with DCOM within the required timeout.

Error

will fail. Error

fail. Error

CDectComPort.

Error

file.

No action required. A duplicate core keycode causes this

applicable functionality is available on the BCM.

No action required.

properly. If it is stopped, then start it. If it is running, then stop it and restart it.

Specific to Information from component.

Restart all TAPI applications to use with the new configuration.

If the application is not behaving correctly restart it after the Voice CTE service has started.

Contact Support.

Contact Support. There is a possibility that user can

Verify if the service <Service Name> is disabled, and enable the service <Service Name> if needed.

The following actions should only be conducted by a Nortel Networks' personnel. (1) reboot, (2) if problem perssists, through VNC run miserver shutdown, and mspTrace -mutils d0xffffffff, (3) try again, collect the trace files in …\Unified Manager\log, and forward them to developers.

Contact Customer Support

information event.

change password for ee_admin either from VNC or UM. So to figure out what user did, we can get the recording logs from BCM.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No No No No No No No No No No No No No

No No No No No No No No No No No No

No No No No No No No No No No No No No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No No No No No No No

No No No No No No No No No No No No

No No No No No No

No No Yes No No No

No No No No No No

No No No No No No No No No No No No No No No No No No

No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No No No No No No No

No No No No No No No No No No No No

BCM Alarms-Traps Page 2

Component ID (Alarm)

e

h

2

DECTMtce

92

DECTOAM

93

DECTOAM

94

DECTOAM

95

DECTOAM

96

DECTOAM

97

DECTOAM

98

DECTOAM

99

DECTOAM

100

DECTOAM

101

DECTOAM

102

DECTOAM

103

DECTOAM

104

DECTOAM

105

DECTOAM

106

DECTOAM

107

DECTOAM

108

DECTOAM

109

DECTOAM

110 111

DECTOAM

112

DECTOAM

113

DECTOAM

114

DECTOAM

115

DECTOAM

116 117

DECTOAM

118

DECTOAM

119

DECTOAM

120

DECTOAM

121

DECTOAM

122

DECTOAM

123

DECTOAM

124

DECTOAM

125

DECTOAM

126

DECTOAM

127

DECTOAM

128

DECTOAM

129

DECTOAM

130

DECTOAM

131

DECTOAM

132

DECTOAM

133

DECTOAM

134

DECTOAM

135

DECTOAM

136

DECTOAM

137

DECTOAM

138

DECTOAM

139

DECTOAM

140

DECTOAM DhcpServer

141

disk

142

DNS

143 144

DNS

145

DNS DNS

146

DNS

147

DrWatson

148 149

EmsManager

150

EmsManager

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

256

1 1 1 1 1 1 1 1 1 1 1

1 1

1 1 1

1

1 1

1 1 1

1

1 1

1

1 1

1 1 1 1

1 1

1 1 1

1011

41

1 2

3

708

4097

1000 1001

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

warning Information The description for Event ID ( 256 ) in Source ( DECTMtce ) could not

critical Error Invalid MBM name in request. Contact Customer Support critical Error Failed writing response to pipe Contact Customer Support critical Error Failed to open a signaling channel Contact Customer Support critical Error Failed to obtain a client LAD Contact Customer Support critical Error Failed to send NUS monitor request Contact Customer Support critical Error S_CHANNEL_DATA_SEND failed Contact Customer Support critical Error Failed to open a Media Channel Contact Customer Support critical Error EmsMediaChannelConfigure call failed Contact Customer Support critical Error EmsMediaChannelConfigure response: failure Contact Customer Support critical Error EmsMediaChannelQuery response: failure Contact Customer Support critical Error EmsMediaChannelQuery response: bad requestId Contact Customer Support critical Error EMS_RESP_M_CHANNEL_QUERY mismatched channel capabilities Contact Customer Support

critical Error SendNUSCommand call failed Contact Customer Support critical Error EmsClientAddressAssign call failed Contact Customer Support critical Error Invalid connection type Contact Customer Support critical Error NAIL_UP_FAILURE: type=%d, channel=%d, location=(%d, %d),

critical Error CreateOamChannels call failed Contact Customer Support critical Error MTC_SESSION_ACCEPT error in slot number Contact Customer Support critical Error EmsSignalingChannelDataSend call failed Contact Customer Support critical Error SendMaintenanceSessionEnd call failed Contact Customer Support critical Error MTC_MODULE_DISABLED: SendMaintenanceSessionEnd call failed Contact Customer Support

critical Error MTC_DISABLE_DENIED: SendMaintenanceSessionEnd call failed Contact Customer Support

critical Error Packet handler failed size check. Discarding message Contact Customer Support critical Error Received bad packet from MediaServicesManager Contact Customer Support critical Error EmsConnectionOpen failed. Contact Customer Support critical Error EmsSignalingChannelOpen failed. Contact Customer Support critical Error EmsSignalingChannelDataSend failed twice in SendMonitorRequest. Contact Customer Support

critical Error ShutdownMediaChannels call to EmsSignalingChannelDataSend failed

critical Error EmsMediaChannelOpen failed twice in CreateOamChannels. Contact Customer Support critical Error SendNUSCommand: index out of range. Contact Customer Support critical Error EmsSignalingChannelDataSend failed twice in SendNUSCommand. Contact Customer Support

critical Error EmsSignalingChannelDataSend failed twice in SendNUSCommand. Contact Customer Support

critical Error SendMaintenanceSessionEnd: disable or enable are currently active. Contact Customer Support

critical Error SendMaintenanceSessionEnd failed calling

critical Error DisableMbm: disable or enable is currently active. Contact Customer Support critical Error DisableMbm failed calling EmsSignalingChannelDataSend. Contact Customer Support critical Error EnableMbm failed calling EmsSignalingChannelDataSend. Contact Customer Support critical Error CreateDownloadPipe cannot start: another download pipe is in

critical Error CreateDownloadPipe cannot start: MBM must be disabled. Contact Customer Support critical Error CreateDownloadPipe: failed twice calling EmsMediaChannelOpen. Contact Customer Support

critical Error DestroyDownloadPipe cannot succeed: MBM is not disabled. Contact Customer Support critical Error DestroyDownloadPipe failed: incorrect terminal number. Contact Customer Support critical Error DestroyDownloadPipe: failed twice calling

critical Error ShutdownMediaChannels call to EmsSignalingChannelDataSend failed

critical Error Timed out waiting for MediaChannelClose confirmation! Contact Customer Support critical Error Failed to create notification event. Contact Customer Support critical Error Failed to open registry path Contact Customer Support critical Error Failed to read value from registry Contact Customer Support minor Warning The DHCP server issued a NACK to the client (MAC Address of the

critical Error The file system structure on the disk is corrupted and unusable. Please

warning Information Starting Microsoft DNS Server (Windows NT 4.0 Service Pack 5). No action required.

warning Information The DNS Server has started. No action required. warning Information The DNS Server has shutdown. No action required. warning Information The DNS Server has no 'primary' or 'secondary' zones. The DNS Serv

warning Information The DNS Server has no 'primary' or 'secondary' zones. The DNS Serv

warning Information The application, <application name>, generated an application error T

warning Information Service started No action required. warning Information Service terminated No action required.

be found. It contains the following insertion string(s): 01:10:03.895 [DECT MaintenanceConsole:4.]MCServer Started .

cause=%d

twice.

EmsSignalingChannelDataSend.

existence.

EmsSignalingChannelDataSend.

twice.

Requesting Client) for the address (Requested IP Address) request.

run chkdsk utility on the device \Device\Harddisk0\Partition3 with label "".

will run as a caching-only server

will run as a caching-only server, but will not be authoritative for any zones.

error occurred on <data>@<time> The exception generated was <exception code> at address <address> (symbol)

No action required.

Contact Customer Support

Please make sure that the address pool for dialin user is outside or is excluded from the DHCP server scopes.

Contact Support.

No action required.

Contact your Nortel Networks support team.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

No No No No No No No No No No No No

No No No No No No No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No No No No No No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No No No No No No No No No No No No No No No No No No No No No No No

No No No No No No No No No No No No

No No No No No No No No No No No No No No No No No No

No No No No No No

No No Yes Yes Yes Yes

No No No No No No No No No No No No

No No Yes No No No No No No No No No

No No No No No No

No No No Yes Yes Yes

No No No No No No No No No No No No

BCM Alarms-Traps Page 3

Component ID (Alarm)

e

n

t

s

a

2

EmsManager

151

EmsManager

152

EmsManager

153

eventLog

154

eventLog

155

eventLog

156

FTMSS

157

FTMSS

158

FTMSS

159

FTMSS

160

FTMSS

161

FTMSS

162

FTMSS

163

FTMSS

164

FTMSS

165

FTMSS

166

FTMSS

167

FTMSS

168

FTMSS

169

FTMSS

170

FTMSS

171

FTMSS

172

FTMSS

173

FTMSS

174

Generic (SNMP)

175

Generic (SNMP)

176

Generic (SNMP)

177

Generic (SNMP)

178

HotDesking

179

HotDesking

180

HotDesking

181

HotDesking

182

HotDesking

183

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

3000

3001

3002

6005 6006

6009

1 2 3 4 5 6 7

8 100 302 303 304 305 320 321 322 323 324

N/A

3000

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error MSC Driver is in the core upload mode - aborting If this happens due to an interrupted upload of the core imag

critical Error Registry contains an invalid published IP address This happens only if the IP address of a NIC, that is currently

critical Error BCM switch reset - disconnecting all applications No action required. A core reset occurred (either due to a

warning Information The Event log service was started. No action required. warning Information The Event log service was stopped. No action required. warning Information Microsoft (R) Windows NT (R) 4.0 1381 Service Pack 5 Uniprocessor

warning Information Service started. No action required. warning Information Service stopped. No action required. critical Error The Service control request handler could not be registered. No action required. critical Error Received a bad service request. No action required. critical Error Couldn't open the Service Control Manager. No action required. critical Error Couldn't open the %1 service. No action required. critical Error Couldn't create the %1 service. No action required. critical Error Couldn't delete the %1 service. No action required. critical Error (dynamic) No action required. critical Error MSC-1 can no longer be controlled. No action required. critical Error No controlled MSCs remaining. Shutdown. No action required. critical Error (dynamic) No action required. critical Error (dynamic) No action required. critical Error Map file: '%s' is required, but could not be found. No action required. critical Error Could not open map file: '%s'. No file handles. No action required. critical Error Map file: '%s' is corrupted and must be re-installed. No action required. critical Error Map file: '%s' is not compatible with this version of '%s'. No action required. critical Error Could not open map file: '%s'. No action required. N/A N/A Cold Start No action required. A coldStart trap signifies that the

N/A N/A Warm Start No action required. A warmStart trap signifies that the

N/A N/A Link Down No action required. A linkDown trap signifies that the

N/A N/A Link Up No action required. A linkUp trap signifies that the

critical Error HotDesking: Unable to create registry entry No action required. The service will shut down and be re-

critical Error HotDesking: Unable to open registry data No action required. The service will shut down and be re-

critical Error ** UTPS Services table is full. No action required. The service will shut down and be re-

critical Error ** Hot desking being terminated by UTPS. No action required. The service will shut down and be re-

critical Error Hot Desking server is unable to connect to the UTPS. No action required. The service will shut down and be re-

Free.

the user must upload the core. Once the upload procedure completes successfully, the error will go away. If this happe during a core upload, no action is required (it should not happen, because during the core upload, there is no reason start the MSM - the user is probably trying to do some "weird stuff" during the upload).

selected in the Published IP Address field of the UM, has been changed and due to some kind of an error the registry was not properly updated. The user must use the Unified Manager to select the Published IP Address again - the best is to change it to another NIC and then back to the desired NIC.

No action required.

switch from 6/2 to 5/3 DS30 configuration, a cold reset initiated by the user or a core crash). The Media Services Manager disconnects all clients at this time. The Watchdog service will be notified by the Voice MSC Service when the core is up again and restart the Voice MSC Service and all dependent services.

sending protocol entity is reinitializing itself such that the agent's configuration or the rotocol entity implementation may be altered. This i an SNMP Agent only trap and will not generate any events.

sending protocol entity is reinitializing itself such that neither the agent configuration nor the protocol entity implementation is altered. This is an SNMP Agent only trap and will not generate any events.

sending protocol entity recognizes a failure in one of the communication links represented in the agent's configuration. This is an SNMP Agent only trap and will not generate any events.

sending protocol entity recognizes th one of the communication links represented in the agent's configuration has come up. This is an SNMP Agent only trap and will not generate any events.

started by the watchdog.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

No No Yes Yes Yes Yes

No No No No No No No No No No No No

No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No Yes No No No No No Yes No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

No No No No No No

BCM Alarms-Traps Page 4

Component ID (Alarm)

2

HotDesking

184

HotDesking

185

Inventory Service

186

Inventory Service

187

Inventory Service

188

IPRIP2

189

IPSecIKE

190

IPSecIKE

191

IPSecIKE

192

IPSecIKE

193

IPSecIKE

194

IPSecIKE

195

IPSecIKE

196

IPSecIKE

197

IPSecIKE

198

IPSecIKE

199

IPSecIKE

200

IPSecIKE

201

IPSecIKE

202

IPSecIKE

203

IPSecIKE

204

IPSecIKE

205

IPSecIKE

206

IPSecIKE

207

IPSecIKE

208

IPSecIKE

209

IPSecIKE

210

IPSecIKE

211

IPSecIKE

212

IPSecIKE

213

IPSecIKE

214

IPSecIKE

215

IPSecIKE

216

IPSecIKE

217

IPSecIKE

218

IPSecIKE

219

IPSecIKE

220

IPSecIKE

221

IPSecIKE

222

IPSecIKE

223

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

3000

3300

3301

3302

30052

2

3

4

5

6

7

9

10 11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32 33

34

35

36

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error *** Unable to get a timer from the OS. No action required. The service will shut down and be re-

critical Error Hot Desking is unable to initiate the registry. No action required. The service will shut down and be re-

critical Error Inventory Service may have generated an incomplete or incorrect report.

critical Error IPRIPv2 could not join the multicast group 224.0.0.9 on the local

warning Information ISAKMP SA established on <local IP Addr> with <remote IP Addr>. No action required.

critical Error Could not initiate ISAKMP SA <local IP Addr> to <remote IP Addr>. Check settings and Connection

warning Information Deleting ISAKMP SA from <local IPAddr> to <remote IP Addr>. No action required. critical Error No response on <local IP Addr> from <remote IP Addr> - logging out Check settings and Connection

critical Error <local IP Addr> Local interface down - logging out of <remote IP Addr>.Check local interface setup.

critical Error Could not initiate Quick Mode from <local IP Addr> to <remote IP

critical Error PFS required on <local IP Addr> but not provided by <remote IP Addr>.Check PFS setting on remote side

critical Error No local interface for <local IP Addr>. Check local interface setup. minor Warning Unauthenticated Informational message received on <local IP Addr>

minor Warning Informational message received on <local IP Addr> from <remote IP

minor Warning Unprotected Notify message on <local IP Addr> from <remote IP Addr>

minor Warning Bad length on Notify message received on <local IP Addr> from

minor Warning No SPI on Notify message received on <local IP Addr> from <remote I

minor Warning Unprotected Delete message on <local IP Addr> from <remote IP

minor Warning Bad length on Delete message on <local IP Addr> from <remote IP

minor Warning Protocol not recognized on message received on <local IP Addr> from

warning Information Could not find SPI for message received on <local IP Addr> from

minor Warning Error notification (%d) received on <local IP Addr> from <remote IP

warning Information Delete message (for protocol %1) received on <local IP Addr> from

warning Information Established IPsec SAs on <local IP Addr> with <remote IP Addr>: AH

warning Information Established IPsec SAs on <local IP Addr> with <remote IP Addr>: ESP

warning Information Deleting IPsec SAs on <local IP Addr> with <remote IP Addr>: AH

warning Information Deleting IPsec SAs on <local IP Addr> with <remote IP Addr>: ESP

critical Error Failed to Establish IPsec SAs on <local IP Addr> with <remote IP

warning Information Oakley %d Mode proposal accepted on <local IP Addr> from <remote

minor Warning Unknown Notify message (%d) received on <local IP Addr> from

minor Warning Remote system <remote IP Addr> not responding! Deleting SA on

warning Information Idle imeout condition on IPSec SA between Local: <local IP addr>,

Critical Error IPSec Client connection request on %1 from %2 Rejected. No Default

Warning Warning ISAKMP Socket Open Failed on interface %1. Trying to re-init Socket

Critical Error ISAKMP Socket Open Failed on interface %1. Stop and Re-start IPSecIKE service Critical Error BCM has no IP Address on the IPSec Client private network: IP

Critical Error BCM interface that IPSec client is trying to connect to (%1) is on the

Critical Error The IP Address of the PC running the IPSec client (%1) is on the

Exception caught while loading DLLs: missing %s.dll

%s GetInventoryDocument() returned error.

Failed to open Software resource: %s

interface with IP address x.x.x.x. The data is the error code.

Addr>.

from <remote IP Addr>.

Addr> not authentic.

being dropped.

<remote IP Addr> - dropping it.

Addr> after Phase 1 - dropping it.

Addr> being dropped.

Addr> - dropping it.

<remote IP Addr> - message dropped.

Addr>.

<remote IP Addr>.

outbound SPI <Hex Number>, AH inbound SPI <Hex Number>.

outbound SPI <Hex Number>, ESP inbound SPI <Hex Number>.

outbound SPI <Hex Number>, AH inbound SPI <Hex Number>.

outbound SPI <Hex Number>, ESP inbound SPI <Hex Number>.

Addr>.

IP Addr>.

<remote IP Addr>.

interface: <local IP addr>

Remote: <remote IP addr>. Delete SA.

Route Set on BCM. IPSec Client Termination is not supported.

Interfaces.

Address: %1 IP Mask: %2.

private network (%2).

Contact customer support.

Make sure that IP RIP v2 is properly configured on the local interface from which the event is received. If the problem persists, even after configuring the interface to RIP v2, please contact tech support.

Check settings and Connection

No action required.

Check settings and Connection

No action required.

Check settings and Connection.

No action required.

Use Net Link Manager to set a Defaut Route.

No action required.

Set an interface to have a valid IP Address on the same network as assigned IP Address for IPSec client.

PC IPSec Client should connect to a different interface on the BCM. PC IPSec Client is not on the correct network.

started by the watchdog.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

Yes No No No No No

No No No No No No

No No No No No No No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No No No No No

BCM Alarms-Traps Page 5

Component ID (Alarm)

h

eventSource (Trap)

2

IPSecIKE

224

IPSecIKE

225

IPXRouterManager

226

IVR(<process-name>)

227

IVR(bim)

228

IVR(bim)

229

IVR(bim)

230

IVR(bim)

231

IVR(bim)

232

IVR(bim)

233

IVR(vmt)

234

JET

235

JET

236 237

JET

238

JET kbdclass

239 240

LLNail

241

LLNail

242

LLNail

243

LLNail

244

LLNail

245

MGS

246

MGS

247

MGS MGS

248

MGS

249

MGS

250

MGS

251

MGS

252

MGS

253

MGS

254

MGS

255

MGS

256

MGS

257

MGS

258

MGS

259

MGS

260

MGS

261

MGS

262 263

MGS MGS

264

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

Event ID (Alarm)

eventId (Trap)

37

38

20133

1

8

9

16 69

7

8001 8002 8003 8004 8005 1001 1002 1003

1004

1005

2001

2002

2003

2004

2090 3001 3002

3003

3004

3005

3006

3007

3008

3090

3091

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

Critical Error IPSec Client connection request on %1 from %2 Rejected. BCM only

minor Warning IPSec connection request Rejected on %1. Maximum number of IPSec

critical Error IPX Routing failed to start because IPX forwarder driver could not be

warning/critical/warning Information/Error/

critical Error Severity: 7 Component: #vps.<IVR#>/<BCM-name> Message: Failed

critical Error Severity: 9 Component: #vps.<IVR#>/<BCM-name> Message: Play

critical Error Severity: 7 Component: #vps.<IVR#>/<BCM-name> Message: Play

critical Error Severity: 7 Component: #vps.<IVR#>/<BCM-name> Message: Can't

warning Information Severity: 1 Component: #vps.<IVR#>/<BCM-name> Message: Call

warning Information Severity: 1 Component: #vps.<IVR#>/<BCM-name> Message:

warning Information ((215) ) The database engine 04.909.0000 started. No action required. warning Information ((xxx) ) The database engine stopped. No action required. warning Information ((xxx) ) The database is running recovery steps. No action required. warning Information ((xxx) ) Redoing log file .\wins\j50.log. No action required. critical Error Could not locate the device object for one or more keyboard port

warning Information UTWAN: KSU ready. No action required warning Information UTWAN: %2 channel(s) configured. No action required warning Information UTWAN: Issued a command to create WAN Task. No action required warning information UTWAN: Successfully created WAN Task. No action required. minor Warning UTWAN: Failed to create WAN Task. No action required. warning Information ***** MGS <version> started on <date> ***** No action required. MGS started warning Information Mgs:: Initialisation complete (max=<x>, min=<n>) No action required. MGS initialization is complete warning Information Mgs:: Shutting down on request from the SCM No action required. MGS is shutting down normally warning Information MediaTransport::(OID=<oid>) Received valid ports No action required. The problem reported in an earlier

warning Information MsmProxy:: <interface> succeeded No action required. The problem reported in an earlier

minor Warning MediaTransport::(OID=<oid>) Received bad ports: <port1> <port2> Submit a CR and attach ZIP'ed log files (archlog). The Resource Manager allocated

minor Warning MediaTransport::(OID=<oid>) Codec and/or frames per packet

minor Warning MediaTransport::(OID=<oid>) Transport mismatch <details> Submit a CR and attach ZIP'ed log files (archlog). There was a problem establishing a

minor Warning MsmProxy:: <interface> returned error <error> Submit a CR and attach ZIP'ed log files (archlog). There was a problem establishing a

minor Warning <entity>:: <interface> returned error <error> Submit a CR and attach ZIP'ed log files (archlog). There was a problem establishing a

critical Error <entity>:: Caught <exception> Submit a CR and attach ZIP'ed log files (archlog). Software bug. critical Error Mgs:: Shutting down due to gateway creation failure Look to previous log entries for error details. A Gateway could not be created.

critical Error Mgs:: Shutting down due to gateway initialisation failure Look to previous log entries for error details. A request to the Media Path Server

critical Error Mgs:: Shutting down due to fatal error Look to previous log entries for error details. A fatal error was reported by an MGS

critical Error Mgs:: Shutting down due to MSM communication failure Investigate and correct the cause, and restart the system. The Media Services Manager (MSM)

critical Error Mgs:: Shutting down due to MPS communication failure Investigate and correct the cause, and restart the system. The Media Path Server (MPS) has

critical Error Mgs:: Shutting down due to resource limits query failure Look to previous log entries for error details. A request to the Media Services

critical Error Mgs:: Shutting down due to configuration query failure Look to previous log entries for error details. A request to the Media Services

critical Error <entity>:: Caught <exception> Submit a CR and attach ZIP'ed log files (archlog). Software bug. critical Error ScmProxy:: NnuServiceStartService returned error <error> Investigate and correct the cause, and restart the system. NNU failed to start the MGS as a

Warning

supports IPSec Client connection requests from PCs on a different subnet that come in over the Interface connected to the Next Hop Router.

Tunnels reached. %1 Parameter: IP Address of Interface that IPSec was received on.

loaded. Severity:<severity> Component:<comp> Message:<message> Refer to IVR Alarm List for actions for these generic IVR

to read xref file %s::%s.

Failure. Exceeded the maximum number of play lists.

Failure. Unable to add vocab item '%s' to play list::%s.

Failure. Unknown vocabuary item '%s'.

set port capabilities to %s::%s.

presented and no ports available to receive the call.

Class=<Subsystem[MX]> mx_AnswerCall: Invalid Handle (2)

devices.

mismatch <details>

If there is a router between the PC running IPSec client and the interface you are trying to connect to on the BCM, then t NetLinkManager needs to be defined to use this interface in order to support IPSec Client..

No Action required. This is for information only. The BCM has rejected this IPSec request as the maximum number of IPSec tunnels are already connected. Contact Support.

alarms. Verify that the mmfxref.dat file exists in the specified location and if not restore it. Otherwise delete and redo MMF to VFS conversions. Modify PeriProducer application to decrease the number of items in the play request. Inspect reason for failure and take appropriate action. If the reason is ME_PLAY_LIST_FULL then modify PeriProducer application to decrease the number of items in the play request. Verify it is a recorded element in the MMF and the MMF has been converted to VFS. If not record element and perform conversion. Reconfigure the number of media gateways. First %s is the port caps and second

Configure more IVR ports.

Terminate application from all admistrative lines.

Contact Support.

Submit a CR and attach ZIP'ed log files (archlog). There was a problem establishing a

These are general IVR events; they are not BCM specific. The first %s is the path and the second %s is the reason for failure.

First %s is vocab and second %s is reason for failure.

First %s is the vocab item.

%s is reason for failure.

BCM FP1 Upgrades will fail to install, no longer supported, replace BCM hard drive.

event 2001 has now returned to normal.

event 2004 has now returned to normal.

invalid RTP ports. This is not an MGS issue.

call.

(MPS) or Media Services Manager (MSM) failed. This is not an MGS issue.

component.

has shut down unexpectedly. This is not an MGS issue.

shut down unexpectedly. This is not an MGS issue.

Manager (MSM) failed. This is not an MGS issue.

service. This is not an MGS issue.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

No No Yes No No No

No No No No No No

No No Yes No No No

No No No No No No

No No No No No No No No Yes No No No No No No No No No No No No No No No

No No No No No No

Yes No No No No No Yes No No No No No Yes No No No No No Yes No No No No No Yes No No No No No

No No No No No No No No No No No No No No No No No No

No No No No No No

No No Yes No No No No No No No No No No No No No No No

No No No No No No

No No Yes No No No

No No No No No No

BCM Alarms-Traps Page 6

Component ID (Alarm)

d

s

0

2

MGS

265

Modem

266

MPS

267

MPS

268

MPS

269

MPS

270

MPS

271

MPS

272

MPS

273

MPS

274

MPS

275

MPS

276

MPS

277

MPS

278

MPS

279

MPS

280

MPS

281

MSPAlarmService

282

mspQoS

283

mspQoSMP

284

mspQoSMP

285

mspQoSMP

286

mspQoSMP

287

mspQoSMP

288

mspQoSMP

289

mspQoSMP

290

mspQoSMP

291

mspQoSMP

292

mspQoSMP

293

mspQoSMP

294

mspQoSMP

295

mspQoSMP

296

mspQoSMP

297

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

3092

52

1001 1002 2001

2002

2003

2004

2005

3001

3002

3003

3004

3005

3006

3007

3008

N/A

2000

4003

4014 4019

4020

4021

4022

4023

4024

4026

4028

4030

4031

4032

4034

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error ScmProxy:: NnuCallback returned error <error> Investigate and correct the cause, and restart the system. NNU failed to start the MGS as a

Critical Error The specified resource type can not be found in the image file. Contact customer support. Happens on system Startup and

warning Information MPS service started No action required MPS service is successfully started.

warning Information MPS service stopped No action required MPS service is stopped. minor Warning **WARNING** Unable to register as a Service Restart system;contact customer support NNU could not start MPS as a

minor Warning **WARNING** Unable to stop service Contact customer support NNU could not stop MPS as a

minor Warning **WARNING** FUMP message could not be sent Contact customer support Could not send fump message

minor Warning **WARNING** Codec incompatible; call dropped Change or make available the correct Codec to match the

minor Warning **WARNING** Endpoint %d:%d registration failed Contact customer support Failed to register an endpoint due to

critical Error **ERROR** Unable to allocate memory;MPS service aborted May need to reboot the system System is low on memory and cannot

critical Error **ERROR** Unable to initialize MPSMI;MPS service aborted Restart system;contact customer support Cannot initialize MPSMI; this is not an

critical Error **ERROR** Unable to connect to MSM, rc=%d;MPS service aborted Restart system;contact customer support Cannot connect to Media Service

critical Error **ERROR** Unable to open FUMP channel;MPS service aborted Restart system;contact customer support Media service manager could not ope

critical Error **ERROR** FUMP channel not ready;MPS service aborted Restart system;contact customer support Fump channel is not ready; this is not

critical Error **ERROR** Reset by Network Manager Submit a CR and attach archlogs Network manager thinks MPS is dead.

critical Error **ERROR** Received EMS_EVENT_CONNECTION_LOST from

critical Error **ERROR** Unable to create event;MPS service failed to start May need to reboot the system System is low on resources and

major Failed to open client end of SNMP Trap Agent mailslot using CreateFil

warning Information The description for Event ID ( 2000 ) in Source ( mspQoS ) could not

critical Error Memory allocation failed on %2. May need to reboot system. System is low on memory and cannot

critical Error %2: Maximum filter limit has been reached. Need to remove other QoS filters. The maximum number of QoS filters

critical Error Too many ports specified for %2 - Max: 256. Reduce the number of QoS Ports specified. minor Warning Could not read registry key "%3" on %2. Use default value for now.

minor Warning Could not read registry value "%3" on %2. Possibly due to initial configuration of this module. Once the

minor Warning Could not read port values for %2. Fix Port Range entries. They are invalid. Entries in Port Range field are invalid.

critical Error Could not create symbolic link %3 of %2. QoS driver has failed to load. Reboot system. If this error

critical Error Could not create %2. QoS driver has failed to load. Reboot system. If this error

minor Warning %2 failed to register as an Intermediate Miniport. QoS driver has failed to load. Reboot system. If this error

minor Warning Unable to read "PortTable" registry entry for device %2. The default

minor Warning Zero bandwidth, disabling QoS! Check the WAN drivers. Possibly caused by the WAN driver. Contact Customer

minor Warning Error in reading IP addresses, disabling QoS! Check that the LAN and

minor Warning Error in Wan Premium Percentage. Value must be between 0 and 10

critical Error NAT %3 values are invalid. Fix Port Range entries. They are invalid. The Inside or Outside port values are

MSM;MPS service aborted

Win32 GetLast Error() value = %value%.

be found. It contains the following insertion string(s): .

Problem will go away if OAM is properly installed.

port range of 28000 - 28511 will be used.

WAN are properly installed.

Use default value for now. Reset the WAN Premium Percentage in OAM.

Codec supported by the software at the far end of the call.

Restart system;contact customer support Lost connection to Media Service

Contact customer support. This item only shows up as an alarm.

No action required. This item will only show up in DEBUG

Possibly due to initial configuration of this module. Once the module has been configured, this error should go away. Otherwise, the registry may be corrupted.

module has been configured, this error should go away. Otherwise, the registry may be corrupted.

persists, contact Customer Support.

persists, contact Customer Support. No action required. Registry value has not been initialize

Support.

Check that all LAN and WAN interfaces are valid. Contact Customer Support. Enter a valid Premium Percent value. Must be between 0 and

100.

service. This is not an MGS issue.

should be ignored

service; this is not an MPS issue.

through EMS FUMP channel; this is not an MPS issue. Call dropped due to incompatible codecs; this is not an MPS issue.

unknown endpoint type or duplication; this may not be an MPS issue.

allocate resources in the driver; this is not an MPS issue.

MPS issue.

Manager; this is not an MPS issue.

a FUMP channel for MPS; this is not an MPS issue.

an MPS issue.

Manager; this is not an MPS issue.

cannot allocate event handle in the driver; this is not an MPS issue.

builds of mspqos. Perfmon has opened the mspqos performance collector, mspperf.dll.

allocated resources in the driver.

has been reached.

Registry value is missing.

Registry key is missing.

Catastrophic driver failure.

The default range will be used. Unless other ports are chosen, this message will continue to appear. Thi will not cause problems.

The values used to calculate the Bandwidth resulted in a zero value.

invalid.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

Yes No No No No No Yes No No No No No Yes No No No No No

Yes No No No No No

No No No No No No

No No Yes No No No

No No No No No No No No No No No No

No No No No No No

BCM Alarms-Traps Page 7

Component ID (Alarm)

e

y

t

e

2

mspQoSMP

298

mspQoSMP

299

mspQoSMP

300

mspQoSMP

301

mspQoSMP

302

mspQoSMP

303

mspQoSMP

304

mspQoSMP

305

mspQoSMP

306

mspQoSMP

307

mspQoSMP

308

mspQoSMP

309

mspQoSMP

310

mspQoSMP

311

mspQoSMP

312

mspQoSMP

313

mspQoSMP

314

mspQoSMP

315

mspQoSMP

316

mspQoSMP

317

mspQoSMP

318

mspQoSMP

319

mspQoSMP

320

mspQoSMP

321

mspQoSMP

322

NCM

323

NCM

324

NCM

325

NCM

326

NetBT

327

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

4035

4036

4037

4038

4039

4040

4041

4043

4044

4045

4046

4047

4048

4049

4050

4051

4052

4053

4054

4055

5001

5005

5011

9001

9004

301

302

311

312

4319

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

minor Warning Could not read registry value "%3". %2. Possible registry corruption. Check to see if

critical Error Could not create data directory %2. Check the registry value \Machine\Software\Nortel

critical Error Could not create log file %2. Make sure that d:\Data Files\Nortel Networks\Unified

critical Error Could not write log file %2. Make sure that d:\Data Files\Nortel Networks\Unified

critical Error Terminating logging thread. Logging will not be enabled on any

critical Error Can't read an NDIS OID value. Possible network interface card failure. Cannot read the MAC address from

minor Warning Can't start logging for device mspQoSMP%d. System may be low on resources. Try rebooting the system

critical Error Possible infinite loop. %2. Possible link list corruption in driver. Reboot system and

minor Warning Linked List has unexpected number of entries. %2. Reboot system. Count of entries in linked list is out of

minor Warning %2: H225 setup message exceeds message fragment buffer. %3 Need to reduce the number of codec choices. This will

warning Informational %2: Processing more than one fragmented H.225 setup message. No action required. Detects when two setup messages

critical Error SIP parser error: %2 Send NT event log and stlog to development / ITAS. Check if

critical Error SIP Init Failure. %2: %3. Please check that mspqos.sys is properly

critical Error OSIP Failure. %2: %3. Send NT event log and stlog to development / ITAS. Error in decoding or encoding SIP

critical Error SIP Call State Machine Failure. %2: %3. Send NT event log and stlog to development / ITAS. Unexpected state machine transition

critical Error SIP Proxy Failure. %2: %3. Send NT event log and stlog to development / ITAS. Unexpected SIP data structure

critical Error SIP Firewall Failure. %2: %3. Send NT event log and stlog to development / ITAS. Firewall functionalities failed for SIP

critical Error SIP Nat Failure. %2: %3. Send NT event log and stlog to development / ITAS. Nat functionalities failed for SIP call.

warning Information Non-SIP Packet through SIP default port 5060. Send NT event log and stlog to development / ITAS. Check if

warning Information %2 link is %3. If WAN link is down, check the cable and make sure the

critical Error %2 : Could not allocate the resources necessary for operation. System is low on memory. Reboot system.

critical Error %2 : Has encountered an internal error and has failed. QoS driver has failed to load. Reboot system. If this error

critical Error %2 : A required parameter is missing from the Registry. Possible problem with LAN or WAN drivers. Could not get Information from one of

minor Warning %2 could not allocate a resource of type %3 due to system resource

critical Error %2 failed to register itself with the NDIS wrapper. QoS driver has failed to load. Reboot system. If this error

Information The description for Event ID ( 311 ) in Source ( NCM ) could not be

warning Information The description for Event ID ( 311 ) in Source ( NCM ) could not be

critical Error A duplicate name has been detected on the TCP network. The IP

interface.

loaded.

problems.

found. It contains the following insertion string(s): NCM config import started. Command option - /k.

found. It contains the following insertion string(s): NCM config command completed.

found. It contains the following insertion string(s): NCM file import started. Command option - /l.

found. It contains the following insertion string(s): NCM file command completed.

address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

\Machine\System\CurrentControlSet\mspQoSMP\Parameters\ FWFilters\Status is set to either Disabled or Enabled.

Networks\Voice Net\RunTimeDir to see if the directory is a valid directory.

Manager\FWLogs is a writable directory.

Problem with Firewall Filters logging function. Contact Customer Support.

see if problem goes away. If not, contact Customer Support.

contact Customer Support.

reduce the size of the setup message.

there are any non-SIP packets going through the BCM via the port 5060.

If SIP is to be used as the VOIP protocol, reboot system to make sure mspqos.sys is loaded properly and that there are no memory allocation issues.

there are any non-SIP packets going through the BCM via the port 5060.

configuration on both ends match.

persists, contact Customer Support.

System is low on memory. Reboot system.

persists, contact Customer Support. No action required.

No action required.

The most likely reason for this is that a duplicate name has been detected on the network. Use the NBTSTAT -N command to see the name of the computer in the conflict state. The IP address of the node that sent the message is in the data returned by this command, offset by 28 bytes.

Could not set the Firewall status. Setting status to Disabled

Could not log Firewall Filter data to th data directory specified in the Registr key RunTimeDir. Could not create text log file to d:\Data Files\Nortel Networks\Unified Manager\FWLogs.

Could not create text log file to d:\Data Files\Nortel Networks\Unified Manager\FWLogs.

Catastrophic failure of Firewall Filters logging.

one of the network interfaces.

Driver could not start the worker thread that logs packets.

Detected possible linked list corruption. Attempts to repair list.

sync with the actual number.

H.225 setup message is larger than internal storage buffer. Call may not go through properly. i.e. one-way speech

are being processed at the exact same time. This can happen when there is a SIP parser error or when a non-SIP pack passes the driver via the default 5060 SIP port.

SIP structures used in driver are not properly initialized.

packet using the OSIP parser.

for SIP processing.

manipulations.

call.

Catastrophic driver failure.

the network interface drivers.

Catastrophic driver failure.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

Yes No No No No No

No Yes No No No No

No No Yes No No No

No No No No No No

No No Yes No No No

No No No No No No

No No Yes No No No

BCM Alarms-Traps Page 8

Component ID (Alarm)

p

t

2

NetIQObjMgr

328

NetIQObjMgr

329

NetIQObjMgr

330

NetIQmc

331

NetIQccm

332

NetIQccm

333

NetIQccm

334

NetIQccm

335

NetIQccm

336

NetLinkManager

337

NetLinkManager

338

NETLOGON

339

NGRPCI

340

NGRPCI

341

NGRPCI

342

NGRPCI

343

NGRPCI

344

NGRPCI

345

Nnu

346

NSACD

347

NwRdr

348

OSPFMib

349

Perfctrs

350

Perflib

351

Perflib

352

Policy Services

353

Policy Services

354

qos_flt_init

355

qos_flt_init

356

Rdr

357

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

15000

15001

15002

0

257

261

264

0

3095

4

5

5000

5001

5003

5009

1000

0

8007

2

3101

1008

2002

5

6

0

3013

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

minor Warning The value for Authorized Management Server(s) was changed to XYZ.”No action required. The event will be generated if the

minor Warning The Bind Management Server Port number was changed to XYZ. No action required. The event will be generated if the

minor Warning The NetIQ Agent Listening Port number was changed to XYZ. No action required. The event will be generated is the

warning Information The following is the message from NetIQ AppManager:

warning Information The following is the message from NetIQmc: [764] NetIQmc warm

warning Information The following is the message from NetIQccm: [187] NetIQccm warm

warning Information NetIQccm ADMIN message: [195] Ping MS <XYZ.XYZ.XYZ.XYZ> fail

warning Information NetIQccm ADMIN message: [195] ccm is having intermittent

warning Information The description for Event ID ( 0 ) in Source ( NetLinkManager ) could

critical Error This Windows NT computer is configured as a member of a workgrou

minor Warning Adapter NGRPCi#: Adapter Link Down. Please make sure the LAN cards inside BCM is connected

warning Information Adapter NGRPCi#: Adapter Link Up. No action required This is not valid before BCM 3.0

warning informatin NGRPCI Adapter instance NGRPCI# Cable Connected Successfully No action required This event is only valid before BCM

minor Warning NGRPCI Adapter instance NGRPCI# LAN Cable Disconnected Please make sure the LAN cards inside BCM is connected

critical Error Could not find an adapter Please check the profiles first. If the BCM has only one LAN

critical Error Does not support the configuration supplied. Please check the PCI Slot and make sure that the Netgear

warning Information An NNU Logging application has registered and will process logging

critical Error ITGNS error: %d, Exit code: %d Send NT event log and stlog to development / ITAS. Manually

minor Warning The Microsoft Client Service for NetWare redirector has timed out one

warning Information Service initializing No action required. critical Error Unable to read IO control information from NBT device. In most cases, no action is required. However, please check if

critical Error The Open Procedure for service "RasRad" in DLL "rasrad.dll" failed.

minor Warning The open procedure for service (service name) in DLL (DLL name) has

warning Information Policy Service started. No action required. warning Information Policy Service stopped. No action required. warning Information The description for Event ID ( 0 ) in Source ( qos_flt_init ) could not be

warning Information The description for Event ID ( 0 ) in Source ( qos_flt_init ) could not be

minor Warning The redirector has timed out a request to <Server Name or IP>. Check the server and the connection to the server.

SERVICE_STOPPED.

started.

with error 1.”

communication / map file full failures while communicating with MS <XYZ.XYZ.XYZ.XYZ>. 1 of XYZ attempts failed within the last XYZ minutes. Last attempt succeeded.

not be found. It contains the following insertion string(s): Service started.

not be found. It contains the following insertion string(s): Service stopped.

not as a member of a domain. The Netlogon service does not need to run in this configuration.

messages.

or more requests to <Server name>.

Performance data for this service will not be available. Status code returned is DWORD 0.

taken longer than the established wait time to complete. The wait time milliseconds is shown in the date.

found. It contains the following insertion string(s): Service started.

found. It contains the following insertion string(s): Service stopped.

No action required. This event will be generated if the

No action required. A person could do some basic network testing if they see the failure to ping message to determine if they are having network problems, but no action is required.

No action required. This event will be generated if the link

No action required.

The Netlogon service should not be configured to start automatically on a server that is not a domain member. Configure the Netlogon service so that its startup type is set "Manual."

properly.

adapter installed, ignore this message. Otherwise, change the LAN adapter.

FA310 10/100 Fast Ethernet adapter is plugged into the slot porperly. Otherwise swap the Ethernet Adapter.

No action required.

restart service or reboot BCM

Contact Support.

the network connections of the BCM are working.

This event should not be seen in BCM 3.0. In case of its occurance in a BCM 3.0 machine, please contact Nortel Networks support team. No action required. However, please report the message indicating the service name and the DLL name to support.

No action required. Useful for WAN, LAN status during

No action required.

value for the “Authorized Management Server(s)” field is changed.

“Bind Management Server Port” field is modified.

value for the “NetIQ Agent Listening Port” is changed.

NetIQ AppManager Client Resource Monitor service is stopped.

NetIQ AppManager Client Communication Manager service is stopped.

NetIQ AppManager Client Resource Monitor service is started.

NetIQ AppManager Client Communication Manager service is started.

This event will be generated if the link between the BCM and the NetIQ Vivinet Manager server gets broken.

between the BCM and the NetIQ Vivinet Manager server is back up again.

This is not valid before BCM 3.0 release.

release.

3.0 release. This event is only valid before BCM

3.0 release.

Logged if service failed to start. Error number is that returned by GetLastError().

NBT = NetBIOS over TCP/IP. This can happen when trying to monitor statistics from an inactive network adapter. It can generally be ignored.

bootup but not a normal operation top alarm.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No Yes No No No No

Yes Yes No No No No

No No Yes Yes Yes Yes

No No No No No No

No No No Yes Yes Yes

No No No No No No

No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No Yes No No No

No No No No No No

BCM Alarms-Traps Page 9

Component ID (Alarm)

o

f

m

A

t

o

n

e

2

Rdr

358

Router

359

Router

360

Router

361

Router

362

Router

363

Router

364

Router

365

Router

366

Router

367

Router

368

Router

369

Router

370

Router

371

Router

372

SAM

373

Save Dump

374 375

Security Security

376

Security

377

Security

378

Security

379

Security

380

Security

381

Security

382

Security

383

Security

384

Security

385

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

8003

20013 20015

20031

20048 20049

20064

20089

20101

20103

20105

20111 20139

20139

12288

1001

512

515

528

529

538

577

624

626

628

630

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error The master browser has received a server announcement from the

critical Error The communication device attached to port COM2 is not functioning. Contact Nortel Network's support team.

warning Information The authentication is successful. No action required. critical Error Remote Access Connection Manager failed to start because it could n

warning Information A successful dialin session is ending. No action required. minor Warning A user with invalid username/password combination or a user without

warning Information The authentication for a dial-in user is successful and the BCM dials

critical Error The remote client is busy or the callback number is wrong when a user

minor Warning Using the default value for Registry parameter Enabled because the

critical Error Unable to load C:\winnt\system32\ipxrtmgr.dll. Contact Support. critical Error Unable to load the interface ModemBackup from the registry. The

critical Error Unable to load the interface TivDialup from the registry. The following

critical Error The demand dial connection fails to complete because of no answer, or

warning Information The port COM2 has been disconnected due to inactivity No action required. warning Information The dial-up link drops. No action required. critical Error SAM failed to write changes to the database. This is most likely due to

warning Information The computer has rebooted from a bugcheck. The bugcheck was:

warning Success Audit Windows NT is starting up. No action required. warning Success Audit

warning Success Audit Successful Logon: User Name: <user name> Domain: <domain> Log

major Failure Audit Logon Failure: Reason: Unknown user name or bad password User

warning Success Audit User Logoff: User Name: <name> Domain: <domain> Logon ID: <id>

major Failure Audit Privileged Service Called: Server: NT Local Security Authority /

warning Success Audit Privileged Service Called: Server: NT Local Security Authority /

warning Success Audit User Account Created: Target Account Name: <name> Target Domain:

warning Success Audit User Account Enabled: Target Account Name: <name> Target Domai

warning Success Audit User Account password set: Target Account Name: <name> Target

warning Success Audit User Account Deleted: Target Account Name: <name> Target Domain:

computer <computer name> that believes that it is the master browser for the domain on transport <transport name>. The master browser is stopping or an election is being forced.

locate port information from media DLLs. Restart the computer, if the problem persists.

dialin permission tries to dial in to the system.

back to the user on a specific number.

with callback enabled tries to dial in to the system.

value given is not in the legal range for the parameter.

following error occurred: There are no routing enabled ports available use by this demand dial interface.

error occurred: There are no routing enabled ports available for use by this demand dial interface.

invalid user, or busy line.

memory or disk-space shortage. The SAM database will be restored to an earlier state. Recent changes will be lost. Check the disk-space available and maximum pagefile size setting.

0x0000000a (0x000002d8, 0x00000002, 0x00000001, 0xf3e9f7c1). Microsoft Windows NT [v15.1381]. A dump was saved in: E:MEMORY.DMP.

trusted logon process has registered with the Local Security Authori This logon process will be trusted to submit logon requests. Logon Process Name: \inetinfo.exe

ID: <id> Logon Type: <type> Logon Process: User32 Authentication Package: <package version> Workstation Name: <name>

Name: <user name> Domain: <domain> Logon Type: <type> Logon Process: User32 Authentication Package: <package version> Workstation Name: <name>

Logon Type: 3

Authentication Service Service: LsaRegisterLogonProcess() Primary User Name: SYSTEM Primary Domain: NT AUTHORITY Primary Logon ID: (0x0,0x3E7) Client User Name: <User> Client Domain: <Domain> Client Logon ID: (0x0,0x1234) Privileges: SeTcbPrivilege

Authentication Service Service: LsaRegisterLogonProcess() Primary User Name: SYSTEM Primary Domain: NT AUTHORITY Primary Logon ID: <id> Client User Name: ee_admin Client Domain: <domain> Client Logon ID: <id> Privileges: SeTcbPrivilege

<domain> Target Account ID: <id> Caller User Name: <name> Caller Domain: <domain> Caller Logon ID: <id> Privileges: -

<domain> Target Account ID: <id> Caller User Name: <name> Caller Domain: <domain> Caller Logon ID: <id>

Domain: <domain> Target Account ID: <id> Caller User Name: <nam Caller Domain: <domain> Caller Logon ID: <id>

<domain> Target Account ID: <id> Caller User Name: <name> Caller Domain: <domain> Caller Logon ID: <id> Privileges: -

To stop the 8003 error messages, make sure the routers on the network are not forwarding UDP broadcasts, keeping browser elections on NetBT local to each subnet and enable WINS or lmhosts on the network for netbios name resolution.

Contact Nortel Network's support team. Backup configuration data using BRU

No action required.

Check whether the callback number is right.

No action required.

Contact Nortel Network's support team. Backup configuration data using BRU

Contact Support.

Contact Nortel Network's support team. Please forward the message for to the support team. Please not remove the du file.

No action required.

No action required. However, this event may indicate an unauthorized access attempt.

No action required.

No action required. This event does not indicate a security breach; you can safely ignore it.

No action required.

No action required. Note that a user account is created.

No action required. Note that a user account is enabled..

No action required. (a password set)

No action required. (a user account is deleted.)

re-ghost the hard disk with the image of the same release, and then restore the backup data.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No

No No No No No No

No No Yes Yes Yes Yes

No No No No No No

No No Yes Yes Yes Yes

No No No No No No

No No Yes No No No

No No No No No No

BCM Alarms-Traps Page 10

Component ID (Alarm)

o

e

a

u

M

r

eventSource (Trap)

2

Security

386

Security

387

Security

388

Security

389

Security

390

Security

391 392

serial Service Control Manager

393

Service Control Manager

394

Service Control Manager

395

Service Control Manager

396

Service Control Manager

397

Service Control Manager

398

Service Control Manager

399

Service Control Manager

400

Service Control Manager

401

Service Control Manager

402

Service Control Manager

403

Service Control Manager

404

Service Control Manager

405

Service Control Manager

406

Service Control Manager

407

Service Control Manager

408

Service Control Manager

409 410

Service Control Manager

411

Service Control Manager Service Control Manager

412

Service Control Manager

413

Service Control Manager

414

Service Control Manager

415

Service Control Manager

416

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

Event ID (Alarm)

eventId (Trap)

632

633

636

637

642

644

8

7000

7001

7009 7022

7023

7024

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

warning Success Audit Global Group Member Added: Member: <member id> Target Account

warning Success Audit Global Group Member Removed: Member: <member id> Target

warning Success Audit Local Group Member Added: Member: <member id> Target Account

warning Success Audit Local Group Member Removed: Member: <member id> Target Account

warning Success Audit User Account Changed: Target Account Name: <name> Target

warning Success Audit User Account Locked Out: Target Account Name: <account name>

minor Warning Not enough resources were available for the driver. This is not a problem. This message can be ignored. critical Error The Voice MSC Service service failed to start due to the following error: If voice services (ie voice mail, IP calls etc) are available then

critical Error The WANic 500 Driver service failed to start due to the following error: Contact your technical support representative. A device attached to the system is not

critical Error The Isecdrv service failed to start due to the following error: %%2 Contact Support.

critical Error The Voice Net QoS Monitor service failed to start due to the following

critical Error The Call Detail Recording service depends on the Media Services

critical Error The DECT Alarm Monitor service depends on the DECT OAM service

critical Error The DECT OAM service depends on the Media Services Manager

critical Error The Media Services Manager service depends on the Voice MSC

critical Error The Message Trace Tool service depends on the Media Services

critical Error The Task Scheduler service depends on the Net Logon service which

critical Error The UNISTIM Terminal Proxy Server service depends on the Media

critical Error The Voice CFS service depends on the Media Services Manager

critical Error The Voice CTE service depends on the Media Services Manager

critical Error The Voice Mail service depends on the Voice CTI service which failed

critical Error The Voice Software Alarm Monitor service depends on the Media

critical Error The VoIP Gateway service depends on the Media Path Server service

critical Error The Remote Access Connection manager service depends on the

critical Error Timeout (120000 milliseconds) waiting for service to connect. critical Error The Voice MSC Service service hung on starting. Contact your local support group. critical Error The Call Detail Recording service terminated with the following error: Contact your local support group.

critical Error The Voice Management Subsystem service terminated with the

critical Error The workstation service terminated with the following error: A duplicate

critical Error The Net Logon service terminated with service-specific error 3095. The Netlogon service should not be configured to start

critical Error The Voice CTI service terminated with service-specific error 204. No action required.

Name: <name> Target Domain: <domain> Target Account ID: <id> Caller User Name: <name> Caller Domain: <domain> Caller Logon ID: <id> Privileges: -

Account Name: <name> Target Domain: <domain> Target Account ID: <id> Caller User Name: <name> Caller Domain: <domain> Caller Log ID: <id> Privileges: -

Name: <name> Target Domain: <domain> Target Account ID: <id> Caller User Name: <name> Caller Domain: <domain> Caller Logon ID: <id> Privileges: -

Domain: <domain> Target Account ID: <id> Caller User Name: <nam Caller Domain: <domain> Caller Logon ID: <id> Privileges: -

Target Account ID: <SID number> Caller Machine Name: localhost/127.0.0.1 (Jintegra) Caller User Name: SYSTEM Caller Domain: NT AUTHORITY Caller Logon ID: (xxxxxxx)

error: %%1053

Manager service which failed to start because of the following error:

which failed to start because of the following error:

service which failed to start because of the following error:

Service service which failed to start because of the following error:

Manager service which failed to start because of the following error:

failed to start because of the following error:

Gateway Server service which failed to start because of the following error:

service which failed to start because of the following error:

to start because of the following error:

Services Manager service which failed to start because of the following error:

which failed to start because of the following error:

workstation service which failed to start because of the following error: duplicate name exists on the network.

following error:

name exists on the network.

No action required. (a global group member added.)

No action required. (a global group member removed.)

No action required. (a local group member added.)

No action required. (a local group member removed.)

No action required. (a user account is changed.)

The user account will automatically be unlocked after 30 minutes (default settings). The administrator can unlock the account through the User Manager interface in Unified Manager. If this activity persists, this may be an indication th someone is attempting an unauthorized access to the BCM. The organization's security prime should be notified.

The service did not respond to the there is no action required. Otherwise a restart of the BCM is required. This is not only for BCM 3.0.

Contact Support.

The Media Services Manager service needs to be started. The dependency service or group

Start Voice MSC Service. If the problems persist, contact yo technical support representative.

Start the Media Services Manager service. The dependency service or group

Start Net Logon service. The service has returned a service-

Start the Media Gateway Server. The dependency service or group

Start the Media Services Manager service. The dependency service or group

Start Voice CTI service. The dependency service or group

The Media Services Manager service needs to be started. The dependency service or group

Start the Media Path Server service. The dependency service or group

The BCM name should be unique in the network Happens when network name on BC

Please supply archlog and report to support team. Incorrect function.

The BCM name should be unique in the network

automatically on BCM that is not a domain member. Configu the Netlogon service so that its startup type is set to "Manual."

start or control request in a timely

fashion.

functioning.

BCM FP1 Upgrades will fail to install,

no longer supported, replace BCM

hard drive.

failed to start.

The service did not respond to the

start or control request in a timely

fashion.

failed to start.

specific error code.

failed to start.

is in use on the network.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

Yes No No No No No

No No No No No No

No No No Yes Yes Yes

No No No No No No No No No No No No

No No Yes No No No

No No No No No No

BCM Alarms-Traps Page 11

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

2

ABCD E F G HIJKLM

Component ID (Alarm)

eventSource (Trap)

2

Service Control Manager

417

Service Control Manager

418

Service Control Manager

419 420

SNMP

421

SNMP Trap Agent

422

SNMP Trap Agent

423

Srv Srv

424

Srv

425

SSH Secure Shell Server

426

Survivable Remote Gateway

427

Survivable Remote Gateway

428

Survivable Remote Gateway 1204 warning Information DN:XXXX, Test Local Mode Test feature

429

Survivable Remote Gateway

430

Survivable Remote Gateway

431

Survivable Remote Gateway

432

Survivable Remote Gateway

433

Survivable Remote Gateway

434

Survivable Remote Gateway 2200 minor Warning DN:XXXX, Invalid ID (1) - No endpoint in Gatekeeper database Indicates configuration problem

435

Survivable Remote Gateway 2201 minor Warning DN:XXXX, Invalid ID (2) - ID unknown within the Call Server Indicates configuration problem

436

Survivable Remote Gateway 2202 minor Warning DN:XXXX, Invalid ID (3) - Endpoint in Gatekeeper database is

437 438

Survivable Remote Gateway 2203 minor Warning Permission Denied (1) – No configured Installer Password Indicates configuration problem Survivable Remote Gateway 2204 minor Warning Permission Denied (2) - Branch User already registered with the TN

439

Survivable Remote Gateway 2205 minor Warning Permission Denied (4) – i2002 set used to register with i2004 or i2050 TNIndicates configuration problem

440 441

Survivable Remote Gateway 2206 minor Warning Permission Denied (6) – Retry Allowed Indicates configuration problem

442

Survivable Remote Gateway 2207 minor Warning Locked from Login (1) – Password failed 3 times Indicates configuration problem Survivable Remote Gateway 2208 minor Warning DN:XXXX, Local Mode - Main Office Parameters Not Provisioned Indicates configuration problem

443

Survivable Remote Gateway 3201 critical Error DN:XXXX, Local Mode - Net Connect Server Unreachable Indicates connectivity problem

444 445

Survivable Remote Gateway 3202 critical Error DN:XXXX, Local Mode - Main Office TPS Unreachable Indicates connectivity problem Survivable Remote Gateway

446

System Status Monitor

447

System Status Monitor

448

System Status Monitor

449

System Status Monitor

450

System Status Monitor

451

System Status Monitor

452

System Status Monitor

453

System Status Monitor

454 455

System Status Monitor System Status Monitor

456

System Status Monitor

457 458

System Status Monitor

Event ID (Alarm)

eventId (Trap)

7024

7026

1001

101 102

2000 2019

2021

0

1200 1201

1205

1206 1207 1208

1209

3203

1000

1001

1002

1003

1004

1005

1006

1007

1008 1009

1010

1011

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error The Remote Access Connection Manager service terminated with

critical Error The Voice MSC Service service terminated with service-specific error

critical Error The following boot-start or system-start driver(s) failed to load: intlfxsr

warning Information The SNMP Service has started successfully. No action required. warning Information The Small Site Trap Agent DLL has been loaded. No action required. warning Information The Small Site Trap Agent DLL has been unloaded. No action required. critical Error The server's call to a system service failed unexpectedly. Contact Support. critical Error The server was unable to allocate from the system nonpaged pool

minor Warning The server was unable to allocate a work item 2 times in the last 60

minor Warning Warning: DNS lookup failed for "xxx.xxx.xxx.xxx". None. DNS lookup is not required in order to log in through

warning Information SRG Starting No Action Required warning Information SRG is shutting down No Action Required

warning Information

warning Information DN:XXXX, Local Mode - Set Firmware Upgrade in Progress No Action Required warning Information DN:XXXX, Normal Mode - Set Redirected to Main Office No Action Required warning Information DN:XXXX, Local Mode - Redirection Pending (Set on call) No Action Required warning Information

critical Error

warning Information %1 reports activity. No Action Required A process has reported to the SSM

warning Information %1 reports all of its services are functioning correctly No Action Required A process has reported to the System

warning Information The System Service Monitor has been stopped No Action Required A process has reported to the System

warning Information The System Status Monitor has been started No Action Required A process has reported to the System

warning Information 1. %PCI Device Driver% Driver Recovered.

warning Information 1. %Power Value% Power Recovered.

warning Information 1. CPU Fan Recovered.

warning Information CPU Temperature Recovered. No Action Required. CPU Temperature recovered to less tha

warning Information HDD %#% Recovered. No Action Required. Hard Drives Capacity Information warning Information 1. Physical Memory Recovered.

warning Information %1, Physical RAM Recovered. No Action Required. Physical RAM size Recovery

warning Information CPU load Recovered. No Action Required. CPU Load Recovery Information

service-specific error 620.

85.

kbdclass mouclass nullinp nullvga

because the pool was empty.

seconds.

DN:XXXX, Local Mode - Firmware is out of sync with Main Office Call Server

DN:XXXX, Local Mode - Firmware Upgrade Pending (Set on call)

Originating Call Server

associated with the UserID

DN:XXXX, Local Mode - Firmware is not available on the SRG

2. %Device Name% Device Recovered.

2. Power Supply Fan1 Recovered.

3. Power Supply Fan2 Recovered.

Fan1 Recovered in Tolerance %#%. 3. Fan2 Recovered in Tolerance %#%.

2. Virtual Memory Recovered.

Please contact support. (Note for support: Start the Plug and Play service, and change the Startup mode from Manual or Disabled to Enabled. ) If voice services (ie voice mail, IP calls etc) are available then there is no action required. Otherwise a restart of the BCM is required. This is not only for BCM 3.0.

Contact Support.

SSH.

Indicates that IP set FW on main office has been upgraded and the required FW version is available on the SRG

No Action Required

Indicates configuration problem

Indicates that IP set FW on main office has been upgraded and the required FW version is not available on SRG

No Action Required. PCI Devices and Drivers Information

No Action Required. Power Supply Information

No Action Required. CPU Fan, Fan1 and Fan2 Recovery

100 degrees °C.

No Action Required. Physical and Logical Memories

BCM FP1 Upgrades will fail to install,

no longer supported, replace BCM

hard drive.

that either it, or its monitored services

are indicating activity.

Status Monitor that either it, or its

monitored services are functioning

properly.

Status Monitor that either it, or its

monitored services are stopped

normally.

Status Monitor that either it, or its

monitored services are started

normally.

Information

CPU Temperature Recovery

Information. This alarm has been

found to be insignificant as the CPU

failure temperature is lower than 100

degrees Celsius as per the CPU

specifications. Temperature alarms

will be generated by SSM Event 3017.

Recovery Information

Information. Cannot reproduce this

alarm in lab setup as this requires

faulty hardware.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No Yes Yes Yes Yes

No No No No No No

No No No No No No No No No No No No No No No No No No No No No No No No

No No No No No No

Yes No No No No No

No Yes No No No No No Yes No No No No No Yes No No No No

No Yes No No No No

No Yes No No No No No Yes No No No No No Yes No No No No

No Yes No No No No No Yes No No No No

No Yes No No No No No Yes No No No No No Yes No No No No No Yes No No No No

No Yes No No No No No Yes No No No No

No Yes No No Yes Yes No Yes No No No No

No Yes No No No No

Yes No No No No No

Yes No Yes Yes Yes Yes

Yes No No Yes No No

Yes No No Yes Yes Yes Yes No No Yes Yes Yes

Yes No No Yes Yes Yes

BCM Alarms-Traps Page 12

Component ID (Alarm)

d

eventSource (Trap)

2

System Status Monitor

459

System Status Monitor

460

System Status Monitor

461

System Status Monitor

462

System Status Monitor

463

System Status Monitor

464

System Status Monitor

465

System Status Monitor

466

System Status Monitor

467

System Status Monitor

468

System Status Monitor

469

System Status Monitor

470

System Status Monitor

471

System Status Monitor

472

System Status Monitor

473

System Status Monitor

474

System Status Monitor

475

System Status Monitor

476

System Status Monitor

477

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

Event ID (Alarm)

eventId (Trap)

1012

1013

1014

1015

1016

2000

2001

2002

2003

2004

2005

2006 2007

2008

3000

3001

3002

3003

3004

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

warning Information 1. RAID HW Found.

warning Information 1. Bytes Total/sec Recovered.

warning Information Non-PAged Memory Recovered. No Action Required. Non-Page Memory Recovery

warning Information Telephony Services %1 No Action Required. Telephony Services Status

warning Information Temperature Recovered. No Action Required. Temperature recovered to less than 40

minor Warning 1. %CPUFan Value% Below normal Tolerance.

minor Warning HDD %#% near or on its capacity. Check HDD %#% Capacity Hard Drives Capacity Warnings minor Warning Unable to get %#% Drive from system environment. No Action Required. SSM failed to retrieve the information of

minor Warning 1. Physical Memory near or on its capacity.

minor Warning %1, Physical RAM size less than expected. Increase Physical RAM size in next maintenance window to

minor Warning 1. %#% Bytes Total/sec greater than 25% of LAN/WAN %#% speed.

minor Warning CPU load above 98%. Check System Services to identify which service are

minor Warning Non-Paged Memory near or on its capacity. No Action Required. Non-Page Memory Warning critical Warning CPU Temperature Above Tolerance 100 °C for more than one Minute SSM will shutdown the BCM if the CPU temperature doesn't

critical Error %1 reports some of its services are not functioning correctly Check the service that is reporting that some services are

critical Error %1 reports that all of its services are down Check the service that is reporting services are down. A process has reported to the SSM

critical Error The time interval could not be set on the L.E.D.'S. Board No immediate Action Required but If the condition persists

critical Error The number of timeouts could not be set on the L.E.D.'S. Board No immediate Action Required but If the condition persists

critical Error BCM Reset could not be set on the L.E.D.'S. Board No immediate Action Required but If the condition persists

2. RAID HW Recovered.

3. Primary Single HDD Mode.

4. Mirrored Single HDD Mode.

5.Mirror Drives Mode.

6.Rebuilding Mirror Master HDD.

7. Rebuilding Primary Master HDD.

8. Mirror Master HDD Rebuild Complete.

9. Primary Master Rebuild Complete.

10. Replace Mirror Master HDD.

11. Replace Primary Master HDD.

12. Replace Parimay & Mirror Master HDDs.

2. getting Network Information Recovered.

3. Bytes Sent/sec Recovered.

4. Bytes Received/sec Recovered.

5. Packets Received Error/sec Recovered.

6. Packets Received Discarded/sec Recovered.

7. Packets Outbound_Error/sec Recovered.

8. Packets found Discarded/sec Recovered.

2. %Fan1 Value% failed in Tolerance %#%.

3. %Fan2 Value% failed in Tolerance %#%.

2. Virtual Memory near or on its capacity.

2. Failed to get Network Information.

3. %#% Bytes Sent/sec greater than 50% of LAN/WAN %#% speed.

4. %#% Bytes Received/sec greater than 50% of LAN/WAN %# %speed.

5. Packets Received Error/sec of LAN/WAN%#%.

6. Packets Received Discarded/sec of LAN/WAN%#%.

7. Packets Outbound_Error/sec of LAN/WAN%#%.

8. Packets found Discarded/sec of LAN/WAN%#%.

For 1 to 9, No Action Required. For 10, 11 and 12 replace HDD in next maintenance window.

No Action Required. LAN1, LAN2 and WAN Information.

degrees °C.

1. Check CPU Fan

2. Check Fan 1

3. Check Fan 2

HDD %#% from system. This HDD drive will not be monitore by SSM.

No Action Required. Its recommended that an assesment be made of memory utilization of your BCM.

increase the BCM performance. No Action Required. LAN1, LAN2 and WAN Warnings

consuming the CPU cycles.

recovered within two Minutes

down.

contact Nortel Support.

RAID Hardware Recovery Information

Information

Information. When this indicates "Up"

Unified Manager can be accessed.

Temperature Recovery Information

CPU FAN, FAN1 And FAN2

Warnings

SSM failed to retrieve the information

of HDD %#% from system. This HDD

drive will not be monitored by SSM.

Physical and Logical Memories

Warning

Increase Physical RAM size

CPU load above 98% for more than 2

minutes.

CPU Temperature above Tolerance

100 ° C for more than one Minute,

SSM will shutdown the BCM if the

CPU temperature doesn't recovered

within two Minutes. This alarm has

been found to be insignificant as the

CPU failure temperature is lower than

100 degrees Celsius as per the CPU

specifications. Temperature alarms

will be generated by SSM Event 3017.

A process has reported to the SSM

that either it, or its monitored services

are not fully functional.

that either it, or its monitored services

are all not functioning.

Upon SSM initialization the time could

not be set on the L.E.D.'S. board. A

default value will be used.

Upon SSM initialization the time could

not be set on the L.E.D.'S. board. A

default value will be used.

Upon SSM initialization the time could

not be set on the L.E.D.'S. board. A

default value will be used.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

Yes No Yes Yes Yes Yes

Yes No No No No No

Yes No No Yes Yes Yes

Yes No Yes Yes Yes Yes

Yes No No No No No

Yes No Yes Yes Yes Yes

Yes No No No No No

Yes No Yes Yes Yes Yes Yes No No Yes Yes Yes

Yes No No Yes No No

Yes No Yes No No No

Yes No No No No No

BCM Alarms-Traps Page 13

Component ID (Alarm)

m

A

e

s

o

eventSource (Trap)

2

System Status Monitor

478

System Status Monitor

479

System Status Monitor

480

System Status Monitor

481

System Status Monitor

482

System Status Monitor

483

System Status Monitor

484

System Status Monitor

485

System Status Monitor

486

System Status Monitor

487

System Status Monitor

488

System Status Monitor

489

System Status Monitor

490

Tcpip

491

Tcpip

492

TlntSvr

493

ToneSrvr

494

ToneSrvr

495

ToneSrvr

496

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

Event ID (Alarm)

eventId (Trap)

3005

3006

3007

3008

3009

3010

3011

3012

3013

3014

3015

3016

3017

4198

4199

1000

257 258

771

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error The SSM thread that responds to sanity checks from the L.E.D.'S.

critical Error Sanity Information could not be retrieved from the registry. Using

critical Error The SSM received a bad service request The SSM service should be re-started. If the condition

critical Error The Service Request handler is not installed, the SSM will not be

critical Error

critical Error Unable to access COM2. The SSM cannot be started End the process that is using COM2 and restart SSM Servic

critical Error 1. PCI Card Does not Exist.

critical Error 1. %Power Value% Power Failed.

critical Error 1. CPU Fan Stopped.

critical Error 1. DupliDisk Mirroring Kit not found.

critical Error CPU Temperature Above Tolerance 100 °C for more than two Minutes,

critical Error Non-paged memory on its capacity, SSM rebooting the BCM BCM 1000 will reboot automatically, BCM200/400 need

critical Error Temperature Above Tolerance 40 °C Check BCM's environment temperature BCM's environment temperature is to

critical Error The system detected an address conflict for IP address <IP Address>

warning Information The MS Telnet Service has started successfully. No action required. warning Information ToneSrvr Starting None warning Information ToneSrvr Terminated None critical Error IP Music - initialization failure. Service shutting down. Please disable the ToneSrvr by configuring your IP Music

board could not be created.

defaults

started

problem occurred initializing the SSM. Sanity checking is being turn

off.

2. %PCI Device Driver% Driver Failed.

3. %PCI Device Name% Device Failed.

2. %Power Supply Fan1 Value% Failed.

3. %Power Supply Fan2 Value% Failed.

2. %Fan1 Value% Below Tolerance %#%

3. %Fan2 Value% Below Tolerance %#%

2. DupliDisk Mirroring failed.

3. Mirror Software shut down.

4. Mirror Master HDD failed reading/Writing

5. Primary Master HDD Failed. Reading/Writing.

6. Replacement HDD Smaller than Active Drive.

7. Mirror HDD Smaller than Active Drive.

8. Check Mirror Master HDD.

9. Check Primary Master HDD.

SSM shutting down the power supply

with the system having network hardware address <Hardware Address>. Network operations on this system may be disrupted as a result.

No immediate Action Required but If the condition persists contact Nortel Support.

There is a problem with the Windows registry. The SSM service should be re-started. If the condition persists contact Nortel Support.

persists contact Nortel Support.

The SSM service should be re-started. If the condition persists contact Nortel Support.

If the condition persists contact Nortel Support.

1. Check for existence of the PCI device or replace it.

2. Check for PCI device driver. 3. Check for existence of the PCI device, and make sure its installed properly.

1. Check the Power Supply (Module1, Module2 on redundant System)

2.Check Power Supply Fan1

3.Check Power Supply Fan2

1. Check CPU Fan

2. Check Fan 1

3. Check Fan 2

1. Check DupliDisk Mirroring KIT.

2. Check DupliDisk Mirroring KIT.

3. Check SSM status.

4. Check Mirror Master HDD power/Data cable.

5. Check Mirror Master HDD power/Data cable. 6, 7. Replacement HDD size should be equal or Larger that the Active HDD.

8. Check Mirror Master HDD.

9. Check Primary Master HDD.

BCM 1000 will reboot automatically, BCM200/400 need restart.

restart.

Disconnect the network connection for the interface with <IP Address>, resolve the address conflict, reconnect the network connection, and reboot the machine if needed.

source as: Audio Jack. Contact Customer Support for further assistance.

Windows was not able to create a

thread required for the SSM to

perform sanity checking while

initializing the SSM. Sanity checking

will be disabled.

Upon SSM initialization the sanity

Information could not be retrieved fro

the registry. Default values will be

used.

The SSM received a bad service

request form Service Control

Manager (SCUM).

Upon SSM initialization the Service

Request handler was not correctly

loaded.

Windows was not able to create

"Events" required to perform sanity

checking.

Sanity checking will be disabled, the

board is being switched to quiet mode.

The SSM could not access COM2.

The SSM will not be started.

1. SSM Failed to detect the device.

2. PCI Device Driver failed or not

working properly. 3.

The PCI Device failed while it's

functioning

1. SSM detects there is a failure in

one of the power supply modules.

2. SSM detects there is a failure in

power supply Fan1

3. SSM detects there is a failure in

power supply Fan2

1. CPU Fan stopped or failed.

2. Fan 1 speed below tolerance level

%#%

3. Fan 2 speed below tolerance level

%#%

1. SSM failed to detect the RAID

CARD (Disk Mirroring).

2. SSM detects there is a failure in

Disk Mirroring HW or DLL.

3. SSM Detects the Mirror software

shuts it self down.

4. SSM detects there is a failure in

Primary Master HDD

5. SSM detects there is a failure in

Mirror Master HDD.

6, 7. Replacement HDD size should

be equal or Larger that the Active

HDD.

8. Mirror Master HDD not working

properly.

9. Primary Master HDD not working

properly.

CPU Temperature Above Tolerance

100 °C for more than two Minutes,

SSM shutting down the power supply.

This alarm has been found to be

insignificant as the CPU failure

temperature is lower than 100 degree

Celsius as per the CPU

specifications. Temperature alarms

will be generated by SSM Event 3017.

Non-paged memory on its capacity,

SSM rebooting the BCM

high.

This issue is captures by TcpIP event

ID 4199.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

Yes No No No No No

Yes No Yes Yes Yes Yes

Yes No No Yes No No

Yes No No Yes Yes Yes

Yes No Yes Yes Yes Yes

No No No No No No

No No Yes Yes Yes Yes

No No No No No No Yes No No No No No Yes No No No No No

Yes No No No No No

BCM Alarms-Traps Page 14

Component ID (Alarm)

l

2

ToneSrvr

497 498

UPS

499

UPS

500

UPS

501

UPS UPS

502 503

UPS

504

UPS

505

UPS

506

UPS UPS

507 508

UPS

509

UPS UPS

510

UPS

511

UPS

512

UPS

513

UPS

514

UPS

515 516

UPS

517

UPS

518

UPS

519

UPS UPS

520

UPS

521

UPS

522

UPS

523 524

UPS

525

UPS

526

UPS

527

UPS UPS

528 529

UPS UPS

530 531

UPS

532

UPS UPS

533

UPS

534

UPS

535

UPS

536

UPS

537 538

UPS

539

UPS UPS

540

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

772

1000 1001 1002 1004

1005 1006

1018 1030 1033

1034

1040 1102

1300

1320

2001

2030

2036

2037

1150 100401 100402

1253 100500

100501

100502

100503 100601

100700 100900 101300

101400

101500 101601 101700

103100 103200 103500

103600 103700 103800 110000 110100

200000

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error IP Music Error: IP Gateway - unable to open the FUMP channel.

warning Information *** PowerChute PLUS Version 5.2.1 stopped *** None warning Information *** PowerChute PLUS Version 5.2.1 started *** None warning Information Communication Established None warning Information UPS self-test passed None warning Information Administrative shutdown Save files and shut down programs, or cancel the shutdown.

warning Information Shutdown cancelled None warning Information Smart Cell signal restored None warning Information Minimum redundancy regained none warning Information Battery added None warning Information Battery removed None, if sufficient battery power still exists to support the

warning Information Bypass contactor OK None warning Information UPS internal temperature in bounds None warning Information System Shutdown None Happens twice after a 1320 alarm

warning Information System Shutdown started Save files and shut down programs, or cancel the shutdown. Happens twice before a 1300 alarm

warning Information System shutdown Complete For an administrative shutdown or a shutdown because of

minor Warning Minimum redundancy lost The UPS has too great a load, or too few operational power

critical Error System level fan failed Check the fan for obstructions. If you cannot resolve the

critical Error Bypass contactor failed An internal hardware failure exists. Contact APC Support for

warning Information Normal power restored: UPS on line None warning Information Scheduled UPS self-test passed None warning Information User-initiated UPS self-test passed None warning Information Self-test at UPS passed None warning Information Administrative shutdown started Save files and shut down programs, or cancel the shutdown.

warning Information Administrative shutdown: User initiated Save files and shut down programs, or cancel the shutdown.

warning Information Administrative shutdown: Weekly shutdown Save files and shut down programs, or cancel the shutdown.

warning Information Administrative shutdown: Daily shutdown Save files and shut down programs, or cancel the shutdown.

warning Information User-initiated shutdown cancelled None warning Information UPS returned from low battery condition None warning Information UPS batteries no longer need replacing None warning Information UPS overload condition solved None warning Information UPS runtime calibration initiated A runtime calibration deeply discharges UPS batteries. Avoid

warning Information UPS runtime calibration completed None warning Information User-initiated shutdown started Save files and shut down programs, or cancel the shutdown.

warning Information UPS returned from bypass None warning Information UPS module added None warning Information UPS module removed This is the first step in replacing a failed module. Continue

warning Information Main Intelligence module OK None warning Information Main Intelligence module added None warning Information Redundant intelligence module OK None warning Information Redundant intelligence module added None warning Information Ambient temperature back within thresholds None warning Information Ambient humidity back within thresholds None warning Information UPS on battery This event can be caused by poor power quality (i.e. power

Service shutting down.

Please disable the ToneSrvr by configuring your IP Music source as: Audio Jack. Contact Customer Support for further assistance.

load. If battery removal causes another event of higher severity, re-insert or replace the battery immediately.

input power failure, wait for the UPS to reboot and to start the supported equipment. If you specified a shutdown without a reboot sequence, you must restart the UPS.

modules to support the configured redundancy. Check that a modules are functioning properly and that the redundancy configuration is correct. If the condition persists, contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support.

problem immediately , contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support

assistance. http://www.apc.com/go/direct/index.cfm?tag=support

performing critical operations until battery recharges sufficiently to support the load in case a condition occurs that requires battery operation.

with the replacement

fluctuation). (1) If input power is still present or becomes present again quickly, decrease the sensitivity of the UPS. ( If the UPS has switched to battery operation because of complete loss of utility power, wait for power to be restored to the UPS. If the condition persists, contact an electrician to analyze your utility power. (3) If only the UPS has lost input power, check building wiring and circuit breakers.

during a UPS shutdown.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

Yes No No No No No

No Yes No No No No

No Yes No No No No Yes No No Yes Yes Yes Yes No No No No No

Yes No No No No No Yes No No No No No

Yes No No No No No Yes No No No No No Yes No No No No No

Yes No No No No No

Yes No No No No No Yes No No No No No

No Yes No No Yes Yes

Yes No No No No No

Yes No No Yes Yes Yes Yes No No No No No Yes No No No No No Yes No No No No No

Yes No No No No No

Yes No No No No No Yes No No No No No

Yes No No No No No Yes No No No No No Yes No No No No No

Yes No No No No No

Yes No No No No No Yes No No No No No Yes No No No No No

Yes No No No No No Yes No No No No No Yes No No No No No Yes No No No No No Yes No No No No No

Yes No No Yes No No

BCM Alarms-Traps Page 15

Component ID (Alarm)

n

C

2

UPS

541

UPS

542

UPS

543

UPS

544

UPS

545

UPS

546

UPS

547

UPS

548

UPS

549

UPS

550

UPS

551

UPS

552

UPS

553

UPS

554

UPS

555

UPS

556

UPS

557 558

UPS UPS

559 560

UPS UPS

561 562

UPS

563

UPS UPS

564 565

UPS UPS

566

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

200001

200002

1162

200004

200005

1165

200007

200008

200200

200301

200400 200401 200402

200403

200700

201301

201302

203100 203200 203300 203400 203500

203600

203800

203900

300000

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

minor Warning UPS on battery: High input line voltage This event can be caused by poor power quality (i.e. power

minor Warning UPS on battery: Brownout This event can be caused by poor power quality (i.e. power

minor Warning UPS on battery: Blackout Restore power to the UPS. If there is not a general power

minor Warning UPS on battery: Small momentary sag This event can be caused by poor power quality (i.e. power

minor Warning UPS on battery: Small momentary spike This event can be caused by poor power quality (i.e. power

minor Warning UPS on battery: Deep momentary sag This event can be caused by poor power quality (i.e. power

minor Warning UPS on battery: Large momentary spike This event can be caused by poor power quality (i.e. power

minor Warning UPS on battery: Simulated power failure Wait for this test to complete. warning Information UPS enabling SmartBoost If this event occurs frequently, decrease the Low Transfer

minor Warning Low battery condition The UPS cannot continue to use its battery power to support

warning Information UPS runtime calibration cancelled None warning Information UPS runtime calibration cancelled by user None warning Information UPS runtime calibration aborted by power failure Retry the calibration when power is restored minor Warning UPS unable to perform runtime calibration: Capacity < 100 % The UPS battery capacity is less than 100%, probably

warning Information UPS enabling SmartTrim If this event occurs frequently, increase the High Transfer

warning Information UPS on bypass: user set via software or panel The front panel or a software command was used to put the

warning Information UPS system is in maintenance bypass set by switch The switch at the UPS was used to put the UPS into bypass

critical Error UPS module failed Replace the failed module. minor Warning Main intelligence module removed This is the first step in replacing a failed module. Continue

critical Error Main intelligence module failed Replace the failed module. minor Warning Redundant intelligence module removed This is the first step in replacing a failed module. Continue

minor Warning Redundant intelligence module failed Replace the failed module. warning Information System level fan OK none warning Information Input circuit breaker tripped Reset the circuit breaker. If the problem persists, contact AP

warning Information Input circuit breaker reset None minor Warning Unable to communicate with UPS Check cable connections, make sure UPS is on, and check

fluctuation). Decrease the sensitivity of the UPS. If the condition persists, contact an electrician to analyze your utility power.

failure (that is, if only the UPS has lost input power), check building wiring and circuit breakers. If the condition persists, contact an electrician to analyze your utility power.

fluctuation). Decrease the sensitivity of the UPS. If the condition persists, contact an electrician to analyze your utility power.

Voltage of your UPS. If the condition persists, contact an electrician to analyze your utility power.

its equipment load. The remaining runtime equals, or is less than, the runtime defined by its "Low Battery" setting. Consider upgrading to a UPS that provides more runtime. You can use the APC UPS Selector page to identify the UPS that best meets your system's requirements. http://www.apc.com/go/direct/index.cfm?tag=selectors

because of recent battery operation of the UPS. Wait for the batteries to recharge and then retry the runtime calibration.

Voltage of your UPS. If the condition persists, contact an electrician to analyze your utility power.

UPS into bypass mode, typically for maintenance. Since the UPS cannot support its load if a power failure occurs, return the UPS to online operation as soon as possible.

mode, typically for maintenance. Since the UPS cannot support its load if a power failure occurs, return the UPS to o line operation as soon as possible.

with the replacement

Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support

network status. If the condition persists, contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

Yes No No No No No

Yes No No No Yes Yes

Yes No No No No No

Yes No No No No No Yes No No No No No Yes No No No No No

Yes No No No No No

Yes No No No No No Yes No No No No No Yes No No No No No Yes No No No No No Yes No No No No No

Yes No No No No No

BCM Alarms-Traps Page 16

Component ID (Alarm)

s

2

UPS

567

UPS

568

UPS

569

UPS

570

UPS

571

UPS

572

UPS

573

UPS

574

UPS

575

UPS

576

UPS

577

UPS

578

UPS

579

UPS

580

UPS

581

UPS

582

UPS

583

UPS

584

UPS

585 586

UPS UPS

587

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

300100

300200

300201

300202

300204

300205

300206

300300

300400

301000

301300

301301

301302

301303

301304

301400

301500

301600

310001

310002

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

minor Warning UPS output overload The UPS has sensed a load greater than 100 percent of its

minor Warning UPS self-test failed Run another self-test. If the UPS fails the self-test again,

minor Warning Scheduled UPS self-test failed Run an unscheduled self-test. If the UPS fails the second

minor Warning Scheduled UPS self-test failed: Invalid test Run another self-test. If the UPS fails the self-test again,

minor Warning User-initiated self-test failed Run another self-test. If the UPS fails the self-test again,

minor Warning Self-test at UPS failed Run another self-test. If the UPS fails the self-test again,

minor Warning User-initiated self-test failed: Invalid test Run another self-test. If the UPS fails the self-test again,

minor Warning Self-test at UPS failed: Invalid test Run another self-test. If the UPS fails the self-test again,

minor Warning UPS battery is discharged Wait for the UPS battery power to recharge. warning Information Communication lost while on battery Prepare for possible abrupt shutdown with no warning. The

minor Warning Check installation of Smart Cell signal cable Check cable connections to batteries. minor Warning UPS internal temperature over limit Make sure that there is adequate clearance around the UPS,

minor Warning UPS battery charger failure An internal hardware failure exists. Contact APC Support for

minor Warning UPS on bypass: severe DC imbalance overload An internal hardware failure exists. Contact APC Support for

minor Warning UPS on bypass: output voltage outside limits The UPS has switched automatically to bypass mode becau

critical Error UPS on bypass: top module fan needs repair A hardware failure has caused the UPS to switch to bypass

critical Error Base module fan needs repair An internal hardware failure exists. Contact APC Support for

critical Error Base module bypass power supply needs repair An internal hardware failure exists. Contact APC Support for

critical Error UPS battery needs replacing Replace all faulty batteries. To order replacement batteries,

minor Warning Below lower ambient temperature threshold Check heating and ventilation systems minor Warning Exceeded upper ambient temperature threshold Check air conditioning systems and make sure equipment is

rated capacity. Remove some attached equipment from the UPS. If this condition happens occasionally and briefly, check for attached equipment that typically uses high power periodically (such as laser printers and photocopiers). If the condition persists, contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support.

contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support.

self-test contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support.

contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support.

UPS has switched to battery operation but communication with the UPS has been lost, making it impossible to determine how much runtime the UPS has available. Check network connections, and check input power source.

and that the UPS ventilation ports are not blocked. Allowing the UPS to continue to operate in this condition can damage the UPS. If the condition persists, contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support.

assistance. http://www.apc.com/go/direct/index.cfm?tag=support

its output voltage was too high. Contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support.

operation. Since the UPS cannot support its load if a power failure occurs, correct the failure as soon as possible. Contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support

assistance. http://www.apc.com/go/direct/index.cfm?tag=support

see the following Web page. :http://www.apc.com/go/direct/index.cfm?tag=battery

adequately spaced for proper ventilation.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

Yes No No No No No

Yes No No Yes No No

Yes No No No No No

BCM Alarms-Traps Page 17

Component ID (Alarm)

2

588

UPS

589

UPS UPS

590

UTPS

591

UTPS

592

UTPS

593

UTPS

594

UTPS

595

UTPS

596

UTPS

597

UTPS

598

UTPS

599

UTPS

600

VBMain

601

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

310101 310102

310700

2000

3000

0

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

minor Warning Below humidity threshold Check air conditioning and humidity-control systems. minor Warning Exceeded upper humidity threshold Check air conditioning and humidity-control systems. minor Warning Maximum internal UPS temperature exceeded Make sure that there is adequate clearance around the UPS

minor Warning DN xyz is experiencing incoming voice packet loss while on a call. It is

critical Error <date><time> (UTPS:1.) *** MPSMI is OFF LINE. If the voice watchdog service is NOT running, you will need

critical Error *** RUDPInit initialization failure; error … If the voice watchdog service is NOT running, you will need

critical Error *** UTPS terminating due to problem with RUDP Rx socket; error … If the voice watchdog service is NOT running, you will need

critical Error *** Unable to connect to the Media Services Manager; error … If the voice watchdog service is NOT running, you will need

critical Error *** Unable to open a FUMP channel; error … If the voice watchdog service is NOT running, you will need

critical Error *** Unable to open RUDP socket; error … If the voice watchdog service is NOT running, you will need

critical Error *** Unable to get a timer from the OS. If the voice watchdog service is NOT running, you will need

critical Error *** UTPS is being shut down. If the voice watchdog service is NOT running, you will need

critical Error 12:30:34.040 [UTPS:1.]***MSM has closed the pipe to the UTPS;

critical Error VBMain error: %d, Exit code: %d Send NT event log and stlog to development / ITAS. Manually

receiving fewer voice packets than it is expecting.

shutting down.

and that the UPS ventilation ports are not blocked. Allowing the UPS to continue to operate in this condition can damage the UPS. If the condition persists, contact APC Support for assistance. http://www.apc.com/go/direct/index.cfm?tag=support.

If the message is persistent, the BCM is experiencing network routing difficulties. More quantitative information is available in the UTPS log.

to restart the UTPS service.

Restart the BCM.

restart service or reboot BCM

xyz is the IP set's DN

All UTPS events written to the NT event log are fatal, and will cause the UTPS to shutdown. The reasons for these events are either a missing dependent component (MPS or MSM), or an OS related problem (Unable to initialize a timer, socket, signaling channel to the core).

Logged if service failed to start. Error number is that returned by GetLastError().

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

Yes No No No No No Yes No No No No No

Yes No No No No No

No No Yes Yes Yes Yes

No No Yes No No No

No No No No No No

BCM Alarms-Traps Page 18

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

b

e

m

c

ABCD E F G HIJKLM

Component ID (Alarm)

eventSource (Trap)

2

VNC Service

602 603

VNetManager

604

VNetManager VNetManager

605 606

VNetQoSMonitor

607

VNetQoSMonitor VNetQoSMonitor

608

VNetQoSMonitor

609 610

VNetVoIPGtwy 100 minor Information Service H.323 VoIP Gateway Installed No action required.

611

VNetVoIPGtwy 101 minor Information Service H.323 VoIP Gateway Removed No action required.

612

VNetVoIPGtwy 102 warning Information Service H.323 VoIP Gateway started No action required.

613

VNetVoIPGtwy 105 warning Information Service H.323 VoIP Gateway stopped No action required.

614

VNetVoIPGtwy 110 minor Error Missing Registry Parameter Report error to ITAS Points to a build or upgrade error VNetVoIPGtwy 113 critical Error Syntax error in configuration file 'D:\Data Files\Nortel Networks\VoIP

615

VNetVoIPGtwy 114 minor Warning Invalid Configuration file parameter Check gateway type parameter in remotegateway.cfg table file

616 617

VNetVoIPGtwy 120 critical Error Cannot initializet H323 stack Report error to ITAS Windows or file system problem VNetVoIPGtwy 122 critical Error Cannot read info from license server Report error to ITAS Maybe permissions problem. Refer to

618

VNetVoIPGtwy 123 minor Warning Keycode applied for unknown feature Keycode applied for more recent feature than software knows

619

VNetVoIPGtwy 124 Minor Error Quality of Service monitor connection not established Report error to ITAS May be a Windows resources proble

620

VNetVoIPGtwy 130 Minor Warning Call setup rejected because of insufficient QoS bandwidth Confirm engineering traffic guidelines for network

621

VNetVoIPGtwy 131 minor Warning Dropped connected call from DN X to DN Y. Incompatible codecs or

622

VNetVoIPGtwy 200 major Error Generic System Error A wide assortment of problems. See event text for details. Report error to ITAS to inform

623

VNetVoIPGtwy 201 major Warning Generic System Warning A wide assortment of problems. See event text for details. Report error to ITAS to inform

624

VNetVoIPGtwy 202 Major Warning Registry import problems Report error to ITAS Problem with importing vngway.reg

625

VNetVoIPGtwy 203 Major Warning Registry import problems Report error to ITAS Problem with importing vngway.reg

626

VNetVoIPGtwy 204 Major Warning Registry import problems Report error to ITAS Problem with importing vngway.reg

627

Voice CTE

628

Voice CTE

629

Voice CTE

630

Voice CTE

631

Voice CTE

632

Voice CTE

633

Voice CTE

634

Voice CTE

635

Voice CTE

636

Voice CTE

637

Event ID (Alarm)

eventId (Trap)

1

301 304

306

203 204

205

206

257

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

warning Information The description for Event ID ( 1 ) in Source ( VNC service ) could not

warning Information Voice Net Manager started. No action required. warning Information Voice Net Manager stopped. No action required. minor Warning Failed to open configure or the entry is empty in : D:\Data Files\Nortel

warning Information Voice Net QoS Monitor started. No action required. N/A warning Information Voice Net QoS Monitor stopped. No action required. N/A warning Information Voice Net QoS Monitor flagged fallback. No action required. Indication. VoIP gw has taken action.

warning Information Voice Net QoS Monitor exited fallback. No action required. Indication. VoIP gw has taken action.

critical Error CTE / MSC Driver Initialization Error. Exit Error is 0x03nn. Error 0x03nn. Please collect the files CteDiag.log and

critical Error CTE / MSC Driver Initialization Error. Exit Error is 0x0301 An invalid handle passed to the driver. Please collect the files

critical Error CTE / MSC Driver Initialization Error. Exit Error is 0x0302 Device is not open. Please collect the files CteDiag.log and

critical Error CTE / MSC Driver Initialization Error. Exit Error is 0x0306 Device is already open. Please collect the files CteDiag.log

critical Error CTE / MSC Driver Initialization Error. Exit Error is 0x0307 The requested CTI device cannot be used with this version of

critical Error CTE / MSC Driver Initialization Error. Exit Error is 0x0310 The device driver for the requested CTI device is not installed.

critical Error CTE / MSC Driver Initialization Error. Exit Error is 0x0311 The device driver interface module for the CTI device is

critical Error CTE / MSC Driver Initialization Error. Exit Error is 0x0315 Unable to start a new device driver execution thread.

critical Error CTE / MSC Driver Initialization Error. Exit Error is 0xFFnn Error 0xFFnn. Please ensure the Voice CTE service has

critical Error Other CTE Initialization Error. Exit Error is 0x0002 “Error 0x0002. Please verify the installation of the Voice CTE

found. It contains the following insertion string(s): The VNC service wa started from the Product Maintenance & Support website.

Networks\VoIP Gateway\remotegateway.cfg

Gateway\localgateway.cfg'

insufficient media gateway resources

Most likely, this BCM has been accessed through VNC. Oth than this information, no action is required.

Remote gateway table is empty. If BCM has VoIP keycodes and "Direct" routing mode, user should populate this table.

Check "Local Gateway IP interface" for correct information.

of.

configuration Change or make available the correct Codec to match the Codec supported by the software at the far end of the call.

CteDiag.bak, ensure the Voice CTE service has restarted and report this problem to your support representative.

CteDiag.log and CteDiag.bak, ensure the Voice CTE service has restarted and report this problem to your support representative. <UDR0015>

CteDiag.bak, ensure the Voice CTE service has restarted and report this problem to your support representative. <UDR0016>

and CteDiag.bak, ensure the Voice CTE service has restarted and report this problem to your support representative. <UDR0017>

Windows. Please verify the installation of the Voice CTE service. <UDR0018>

Install the device driver and restart your application. <UDR001>

invalid. Please reinstall the device driver software. <UDR002>

Terminate some applications and restart your application. <UDR006>

restarted. If this fails to correct the problem then please colle the files CteDiag.log and CteDiag.bak, ensure the Voice MSC service has restarted and report this problem to your support representative.

service.”

development team Confirm Keycode server operation

that could require a reboot

Only shows in Event Viewer no Trap

designers

All CTE device driver errors have the hex base 0x0300. Driver errors which do not have specific messages are reported as “Error 0x03nn”. This generic message is rare.

Internal unexpected error.

Most likely an installation problem.

Windows system resource problem during initialization.

Error from MSC driver initialization.

Generic unexpected error. This error is only reported as an event when it causes CTE initialization to fail. In this case it is most likely an installation problem.

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

No No Yes Yes Yes Yes

No No No No No No

No No Yes Yes Yes Yes

No No No No No No

BCM Alarms-Traps Page 19

Component ID (Alarm)

h

e

c

2

Voice CTE

638

Voice CTE

639

Voice CTE

640

Voice CTE

641

Voice CTE

642

Voice CTE

643

Voice Software

644

Voice Software

645

Voice Software

646

Voice Software

647

Voice Software

648

Voice Software

649

Voice Software

650

Voice Software

651

Voice Software

652

Voice Software

653

Voice Software

654

Voice Software

655

Voice Software

656

Voice Software

657

Voice Software

658

Voice Software

659

Voice Software

660

Voice Software

661

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

257

11

18

20

21

22

23

24

31

32

33

34

35

36

37

39

40

41

42

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error Other CTE Initialization Error. Exit Error is 0x0003 “Error 0x003. Please collect the files CteDiag.log and

critical Error Other CTE Initialization Error. Exit Error is 0x0009 Cannot create a window. Terminate some applications and

critical Error Other CTE Initialization Error. Exit Error is 0x00nn CTE could not download FUMP Information about the

critical Error Other CTE Initialization Error. Exit Error is 0x0009 or 0c0055 A CTE application attempted to register with CTE before the

critical Error CTE Runtime Error . Exit Error is 0x0000 Your CTI device has been reset. All call processing has been

critical Error CTE Runtime Error. Exit Error is <No Error> The CTE atom table is corrupt or full. Please collect the files

critical Error All lines were disconnected. Power down the system and check all line

minor Warning DSP message queue (messages to be sent to DSP firmware) is full.

critical Error Wireless re-evaluation required. Initiate data re-evaluation Re-Evaluation should be initiated by the system administrator.MSCid=665, Sev=P8, Cat=F

warning Information Wireless re-evaluation in progress. No action required. This ALARM only alerts the system

warning Information Wireless re-evaluation completed. No action required. This aALARM only alerts the system

critical Error Configured cell %1 failed to come on-line. Determine which basestations belong to the failed cell.

critical Error Ettiquette: There is insufficient data to capture an RSSI signature. Run a re-evaluation with a suitable configuration that will

critical Error The download of firmware to DTCM %1 has failed. Check the logs for occurrences of Event 338. Record the

critical Error A BRI has been selected as the primary clock source rather than a

critical Error A cold start has occurred causing loss of system data. Record the message registered in the log and contact your

warning Information Device firmware download started. This event may occur more than

critical Error Device firmware download failure. Reported by the data transfer server.

critical Error Device firmware download failure. Reported by the data transfer slave.

critical Error Protocol or country profile download failure. Event parameters: %1. Check that the device is properly installed and reset the

critical Error The Market Profile is invalid. The installer must select the appropriate

critical Error The long term alarm threshold has been surpassed in DTCM %1 for th

connections on the system.

Message not sent may cause application to timeout waiting for resour Users may experience call failures.

DTCM.

once per device type.

Event parameters: %1. The device has not been brought on-line by the system.

profile.

Unavailable Seconds Error. The most likely cause is an irregularity with the PSTN connections. The cable connecting the DTCM to the network termination point or external CSU has been disconnected, or there is a problem with the signal from the network.

detection of Loss of Signal. The most likely cause is an irregularity with the PSTN connections. The cable connecting the DTCM to the network termination point or external CSU has been disconnected, or there is a problem with the signal from the network.

detection of Loss of Frame. The most likely cause is an irregularity with the PSTN connections. The cable connecting the DTCM to the network termination point or external CSU has been disconnected, or there is a problem with the signal from the network.

CteDiag.bak, ensure the Voice CTE service has restarted and report this problem to your support representative."

restart the Voice CTE service. <CTE006>

telephony switch. Please collect the files CteDiag.log and CteDiag.bak, ensure the Voice CTE service has restarted and report this problem to your support representative. <CTE005>

Voice CTE service had fully initialized ( error %ld ). If the application is not behaving correctly, restart it after the Voice CTE service has started. <RTR001>

disabled. Ensure the Voice MSC service has restarted. <CTE002>

CteDiag.log and CteDiag.bak, ensure the Voice CTE service has restarted and report this problem to your support representative. <CTE003>

Power down the system and check all line connections on the system. Customer should report event to installer to get tracebacks. MSCid=254, Sev=P6, Cat=B

administrator/installer that mobility data re-evaluation has started.

administrator/installer that mobility data re-evaluation has finished.

Replace the basestations and invoke a data re-evaluation, or warm start the system.

provide an adequate RSSI signature.

message registered in the log and contact your local support group. Power down the system and check the DTCM hardware and the link to the system.

The slot containing the DTCM must be configured as the primary clock source.

local support group. No action required. MSCid=355,Sev=P7,Cat=E

Check that the device is properly installed and reset the device. Try replacing device. If the problem persists, contact you local support group. Check that the device is properly installed and reset the device. If the problem persists, replace the device.

device. The installer must select the appropriate profile. MSCid=350, Sev=P9, Cat=F

Check the logs and look for Events ranging from 315-336. If this alarm occurs more than once over a two-week period, contact your local support group.

Generic internal unexpected error. This error is only reported as an event when it causes CTE initialization to fail.

CTE initialization failed due to Windows system problem.

CTE initialization failed because it could not download KSU identification fump. Applications are sent a CTE event with the failed ME_xxx return code.

Missing service dependency or install problem: Either CTE service is not fully initialized and some application tried to register with CTE or CTE is not registered as a service and application registration failed to launc CTE.

MSC communication error (reset). CTE responds by sending it’s apps a shutdown event with the reason CTE_SHUTDOWN_DEVICE_RESE T, and then shutting down with no error.

CTE has run out of memory or it’s internal memory structure is corrupt. CTE continues to run. Applications receive the CTE response ME_NO_HEAP_MEMORY until som memory is freed or CTE is restarted.

MSCid=254, Sev=P9, Cat=C

MSCid=878, Sev=?, Cat=E

MSCid=879, Sev=?, Cat=E

MSCid=881, Sev=?, Cat=F

MSCid=664, Sev=P9, Cat=F

MSCid=339, Sev=P6, Cat=F

MSCid=351, Sev=P6, Cat=F

MSCid=902, Sev=P8, Cat=F

MSCid=356, Sev=P6, Cat=F

MSCid=358, Sev=P6, Cat=F

MSCid=361, Sev=P6, Cat=F

MSCid=315, Sev=P8, Cat=F

MSCid=316, Sev=P8, Cat=F

MSCid=317, Sev=P8, Cat=F

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

No No Yes No No No

Yes No No No No No

No No Yes No No No

No No No No No No

No No Yes No No No

No No No No No No

No No Yes No No No

Mod No No No No No

Yes No No No No No

No No Yes Yes Yes Yes

BCM Alarms-Traps Page 20

Component ID (Alarm)

A

u

e

h

2

Voice Software

662

Voice Software

663

Voice Software

664

Voice Software

665

Voice Software

666

Voice Software

667

Voice Software

668

Voice Software

669

Voice Software

670

Voice Software

671

Voice Software

672

Voice Software

673

Voice Software

674

Voice Software

675

Voice Software

676

Voice Software

677

Voice Software

678

Voice Software

679

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

43

44

45

46

47

50

51

52

53

54

55

59

61

62

63

67

68

69

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

critical Error The long term alarm threshold has been surpassed in DTCM %1 for th

critical Error A Digital Station Computer Module on bus %1 has been disconnected

critical Error

critical Error A Trunk Computer Module has been disconnected. Event parameters:

critical Error Radio %1 has been removed from service due to an error. An

warning Information A software download to the basestations has started. No action

warning Information All downloads are complete. No action required. warning Information No more credits available for portables or sets. More credits must be

critical Error Incompatible Trunk Computer Module. A Trunk Computer Module

critical Error Invalid Auto Answer Setting. What this means is that a line has been s

critical Error There are no more DTMF receivers that can be allocated. DTMF

critical Error An invalid Trunk Computer Module has been connected to port %1. Power down the system. Disconnect the Trunk Computer

critical Error A device has been connected to a port which is not available for the

critical Error Software registrar error. Error Type: %1. Contact your local support group and get Event tracebacks.

detection of Alarm Indication Signal. The most likely cause is an irregularity with the PSTN connections. The cable connecting the DTCM to the network termination point or external CSU has been disconnected, or there is a problem with the signal from the network.

detection of Remote Alarm Indication. The most likely cause is an irregularity with the PSTN connections. The cable connecting the DTCM to the network termination point or external CSU has been disconnected, or there is a problem with the signal from the network.

detection of Loss of Signal on time-slot 16. The most likely cause is an irregularity with the PSTN connections. The cable connecting the DTCM to the network termination point or external CSU has been disconnected, or there is a problem with the signal from the network.

detection of Alarm Indication Signal on time-slot 16. The most likely cause is an irregularity with the PSTN connections. The cable connecting the DTCM to the network termination point or external CSU has been disconnected, or there is a problem with the signal from the network.

detection of Remote Alarm Indication on time-slot 16. The most likely cause is an irregularity with the PSTN connections. The cable connecting the DTCM to the network termination point or external CSU has been disconnected, or there is a problem with the signal from the network.

or powered down.

Digital Trunk Computer Module or Called ID Computer Module on b

%1 has been disconnected or powered down.

%1 (Module - Card).

accompanying Event message will indicate an explicit reason for the radio failure.

required. During basestation download, system performance may be sluggish, and wireless functionality will not be complete.

acquired before all the registered portables or installed sets can be activated. Parameters: %1 (0=Portable credit required, 1=Set credit required)

cannot operate with the trunk Type assigned to it in Configuration. Eve parameters: %1 (Module - Card). Check that the trunk Type programmed matches the module.

to auto answer but the type of trunk is not suitable for auto answer. Event parameters: %1 (Module - Card). Change the trunk programming to manual answer.

receivers are busy, not working properly, or have not been installed. T line requesting a receiver is on port %1.

device Type. The affected port is %1.

Check the logs and look for Events ranging from 315-336. If this alarm occurs more than once over a two-week period, contact your local support group.

Power down the system and check all connections to the module. If the problem persists, replace the module.

Power down the system and check all connections to the module. Check that the module is properly seated. If the problem persists, replace the module.

Perform diagnostics on the basestation. MSCid=300, Sev=P6, Cat=C

Wait for Event 55.

Acquire more portable credits MSCid=275, Sev=P9, Cat=F

Check that the trunk Type programmed matches the module. MSCid=255, Sev=P9, Cat=F

Change the trunk programming to manual answer. MSCid=256, Sev=P9, Cat=F

If this alarm occurs frequently, add additional DTMF receivers to the system.

Module from the indicated port and check module compatibili for the specific country. Replace the module with as required.

Power down the system and disconnect the device from the port identified. Reconnect it to a valid port.

Replace the Feature Cartridge with the most recent version.

MSCid=318, Sev=8, Cat=F

MSCid=319, Sev=P8, Cat=F

MSCid=320, Sev=P8, Cat=F

MSCid=321, Sev=P8, Cat=F

MSCid=322, Sev=P8, Cat=F

MSCid=250, Sev=P9, Cat=C. On system boot-up the BCM waits 3 minutes before reporting alarm 50/51 to give the modules time to boot up. On a running system the BCM requires a module to be lost for at least 2 minutes before reporting alarm 50/51.

MSCid=251, Sev=P9, Cat=C. On system boot-up the BCM waits 3 minutes before reporting alarm 50/51 to give the modules time to boot up. On a running system the BCM requires a module to be lost for at least 2 minutes before reporting alarm 50/51.

MSCid=252, Sev=P9, Cat=C This only applies to trunk MBM's that shar a DS30 bus. So CTM and BRI MBM's can generate this. To reproduce this bring 2 CTM's or BRI MBM's on a single DS30 and disconnect 1 of the MBM's.On a running system the BCM requires a module to be lost for at least 2 minutes before reporting alarm 50/51./52

MSCid=267, Sev=P8, Cat=F

MSCid=343, Sev=P8, Cat=f

MSCid=863, Sev=P4, Cat=F

MSCid=185, Sev=P9, Cat=F

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No Yes Yes Yes Yes

No No Yes No No No

No No Yes Yes Yes Yes

No No No No No No

Yes No No No No No

No No Yes Yes Yes Yes

No No No No No No

No No Yes No No No

BCM Alarms-Traps Page 21

Component ID (Alarm)

r

A

e

2

Voice Software

680

Voice Software

681

Voice Software

682

Voice Software

683

Voice Software

684

Voice Software

685

Voice Software

686

Voice Software

687

Voice Software

688

Voice Software

689

Voice Software

690

Voice Software

691

Voice Software

692

Voice Software

693

Voice Software

694

Voice Software

695

Voice Software

696

Voice Software

697

Voice Software

698

Voice Software

699

Voice Software

700

Voice Software

701

Voice Software

702

Voice Software

703

Voice Software

704

Voice Software

705

Voice Software

706

Voice Software

707

Voice Software

708

Voice Software

709

Voice Software

710

Voice Software

711

Voice Software

712

Voice Software

713

Voice Software

714

Voice Software

715

Voice Software

716

Voice Software

717

Voice Software

718

Voice Software

719

Voice Software

720

Voice Software

721

Voice Software

722

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

71 72 75

77

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

102

103

194

200 201 202 203 204 205 206 207 208 209

224

226

229

247

260

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

warning Information A log Event has activated the emergency transfer relay. No action required. The alarm was generated by a power

critical Error TEI request error for ISDN emulator. Event parameters: %1. Withdraw the last request for a TEI. MSCid=352, Sev=P1, Cat=D critical Error Clock control is in free run. This could indicate a problem with the cable

critical Error NVRAM Corruption. Re-program the data for Call-by-Call Services. Re-program the data for Call-by-Call Services. MSCid=458, Sev=P4, Cat=A

critical Error Analog Station Computer Module firmware download failure. Event

critical Error An alarm generated by a server application. Refer to application documentation for appropriate action.

critical Error An alarm generated by a server application. Refer to application documentation for appropriate action. MSCid=990, Sev=P5, Cat=F

critical Error An alarm generated by a server application. Refer to application documentation for appropriate action.

warning Information Two modules have been configured to use the same DS30 but cannot

warning Information The trial period for a feature has expired. Feature Parameter: %1

critical Error The Call Server Operating System software has returned an error code.

critical Error Ettiquette: insufficient CFP credits. Purchase additional Portable licenses MSCid=665, Sev=P8, Cat=F warning Information Ettiquette: CFP credits decreased. No action required. MSCid=666, Sev=P8, Cat=E warning Information Ettiquette: UTAM keys required. Purchase a UTAM key MSCid=667, Sev=P8, Cat=F critical Error Ettiquette: UTAM test failed. No action required. MSCid=668, Sev=P8, Cat=F warning Information Ettiquette: Re-eval override done. No action required. MSCid=669, Sev=P8, Cat=E warning Information Ettiquette: Disablement test active. No action required. MSCid=670, Sev=P8, Cat=E warning Information Ettiquette: Disablement test done. No action required. No action required. MSCid=671, Sev=P8, Cat=E warning Information Ettiquette: System startup. No action required. No action required. MSCid=672, Sev=P1, Cat=E warning Information Ettiquette: System online. No action required. No action required. MSCid=673, Sev=P8, Cat=E warning Information Ettiquette: Demo system. No action required. No action required. MSCid=675, Sev=P8, Cat=E critical Error Could not re-enable all devices after a Call Server restore took place.

minor Warning Call Server backup failed. Customer should contact installer to get the

critical Error Call Server restore failed. Call Server will be restarted. Customer shou

critical Error

minor Warning No battery feed. When the system is booted a check is made to

connection, or with the signal from the network.

parameters: %1. The ASCM will not be brought on-line by the system.

co-exist at the configured offsets.

(00=Hunt Groups, 01=Hospitality Services, 02=DPNSS Networking, 03=MCDN Networking, 04=Q.Sig Networking). The permanent softwa key may be purchased to allow continued use of this feature.

A restart will occur. Record the traceback and event parameters and report the error.

Call Server will be restarted. Customer should report event to installer to get tracebacks.

SP event tracabecks.

contact installer to tracebacks.

n invalid event was received on a TCM channel. Check that all devic on the system are supported and that the wiring to the devices is correct.

determine if lines are physically attached to the line ports. This is done by performing a line presence test. If this test fails then it indicates that a line is not attached. Line taken out of service. If no line is attached to the port attach a line. Port = %1. If a line is attached then determine if the line is operational.

failure.

Check the cable connnection or the signal from the network MSCid=447, Sev=P1, Cat=D

Perform diagnostics on the ASCM. MSCid=369, Sev=P6, Cat=F

Correct the DS30 assignments using the dip-switches on the modules. Purchase permanent licenses MSCid=465, Sev=P8, Cat=F

Record the traceback and event parameters and report the error.

Customer should report event to installer to get tracebacks. MSCid=224, Sev=P8, Cat=B

Customer should contact installer to get the SP event tracabecks. Customer should contact installer to tracabecks. MSCid=229, Sev=P8, Cat=B

Check that all devices on the system are supported and that the wiring to the devices is correct.

If no line is attached to the port, attach a line. If a line is attached, then determine if the line is operational.

MSCid=376, Sev=P7, Cat=F

MSCid=226, Sev=P8, Cat=A

MSCid=247, Sev=P8, Cat=B

MSCid=260, Sev=P8, Cat=C

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No No No No No No No No No No Yes Yes Yes

No No Yes No No No

No No No No No No

Yes No No No No No

No No No No No No

Yes No No No No No

No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

Yes No No No No No

No Yes No No No No

Yes No No No No No

BCM Alarms-Traps Page 22

Component ID (Alarm)

h

u

A

2

Voice Software

723

Voice Software

724

Voice Software

725

Voice Software

726

Voice Software

727

Voice Software

728

Voice Software

729

Voice Software

730

Voice Software

731

Voice Software

732

Voice Software

733

Voice Software

734

Voice Software

735

Voice Software

736

Voice Software

737

Voice Software

738

Voice Software

739

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

ABCD E F G HIJKLM

eventSource (Trap)

Event ID (Alarm)

eventId (Trap)

262

263

265

270

271

323

324

325

326

327

328

329

330

331

332

333

334

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

minor Warning No dialtone. When a line is seized a test is made to determine if dial

minor Warning Invalid disconnect sequence. The handshake which occurs between

minor Warning When seizing a trunk to make an outgoing call a handshake must occur

minor Warning Invalid Message. The Call Server is dealing with a multi byte message

minor Warning

minor Warning This event is generated when the short-term alarm threshold has been

tone is present. If this test fails this event is raised. Port = %1. Check the physical trunk line to see if it operating correctly.

the analog trunk and the network when a line is released was not properly completed. The analog turnk is unusable until the disconnect completes. Port = %1. Check the trunk interface with the network to determine if it operating correctly.

between the Call Server trunk and the network before digits can be dialled. This event indicates that this handshake failed since the network did not acknowledge the Call Server request to seize the line. The trunk is unusable until the handshake is properly completed. Port = %1. Check the trunk interface with the network to determine if it operating correctly.

that it does not understand while trying to initialize a set. TN = %1. If t event occurs many times, unplug the set, wait for 3 minutes, then repl the set. May be caused by a noisy line.

set has firmware that is incompatible with the current Call Server loa Customer should contact installer to change Call Server load or the set.

surpassed in the Digital Trunk Interface module for the detection of a degraded minute. The module is in a no-new-calls state. DTCM = %1 Intervention is required to find out why the

surpassed in the Digital Trunk Interface module for the detection of a severely errored second. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out why the Digital Trunk Interface module is alarmed.

surpassed in the Digital Trunk Interface module for the detection of an errored second. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out why the

surpassed in the Digital Trunk Interface module for the detection of controlled slip underflow. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out why the Digital Trunk Interface module is alarmed.

surpassed in the Digital Trunk Interface module for the detection of controlled slip overflow. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out .

surpassed in the Digital Trunk Interface module for the detection of a line code violation. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out why the Digital Trunk Interface module is alarmed.

surpassed in the Digital Trunk Interface module for the detection of loss of signal. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out why the Digital Trunk Interface module is alarmed.

surpassed in the Digital Trunk Interface module for the detection of loss of frame. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out why the Digital Trunk Interface module is alarmed.

surpassed in the Digital Trunk Interface module for the detection of alarm indication signal. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out why the Digital Trunk Interface module is alarmed.

surpassed in the Digital Trunk Interface module for the detection of remote alarm indication. The module is in a no-new-calls state. DTCM %1. Intervention is required to find out why the Digital Trunk Interface module is alarmed.

surpassed in the Digital Trunk Interface module for the detection of loss of frame in timeslot 16. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out why the Digital Trunk Interface module is alarmed.

surpassed in the Digital Trunk Interface module for the detection of alarm indication signal in time slot 16. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out why the Digital Trunk Interface module is alarmed.

Check the physical trunk line to see if it operating correctly. MSCid=262, Sev=P7, Cat=C

Check the trunk interface with the network to determine if it operating correctly.

If the event occurs many times, unplug the set, wait for 3 minutes, then replug the set.

Customer should contact installer to change Call Server load or the set.

Intervention is required to find out why the Digital Trunk Interface module is alarmed.

MSCid=263, Sev=P8, Cat=C

MSCid=265, Sev=P7, Cat=C

MSCid=270, Sev=P8, Cat=A

MSCid=271, Sev=P8, Cat=A

MSCid=323, Sev=P5, Cat=C

MSCid=324, Sev=P5, Cat=C

MSCid=325, Sev=P5, Cat=C

MSCid=326, Sev=P5, Cat=C

MSCid=327, Sev=P5, Cat=C

MSCid=328, Sev=P5, Cat=C

MSCid=329, Sev=P5, Cat=C

MSCid=330, Sev=P5, Cat=C

MSCid=331, Sev=P5, Cat=C

MSCid=332, Sev=P5, Cat=C

MSCid=333, Sev=P5, Cat=C

MSCid=334, Sev=P5, Cat=C

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

Yes No No No No No

No No No No Yes Yes

Yes No No No No No

No No No No Yes Yes

Yes No No No No No

No No No No Yes Yes

Yes No No Yes Yes Yes

Yes No No No No No

BCM Alarms-Traps Page 23

ABCD E F G HIJKLM

A

e

n

Component ID (Alarm)

eventSource (Trap)

2

Voice Software

740

Voice Software

741

Voice Software

742

Voice Software

743

Voice Software

744

Voice Software

745

Voice Software

746

Voice Software

747

Voice Software

748

Voice Software

749

Voice Software 949 minor Warning A bad protocol call control has been received from the Basic Rate

750

Voice Software

751

Voice Software

752

Voice Software

753

VoiceCTI

754

VoiceCTI

755

VoiceCTI

756

VoiceCTI

757

VoiceCTI

758

VoiceCTI

759

VoiceCTI

760

VoiceCTI

761

VoiceCTI

762

VoiceCTI

763

VoiceCTI

764

VoiceCTI

765

VoiceManagementSubsystem

766

VoiceManagementSubsystem

767

VoiceManagementSubsystem

768

VoiceManagementSubsystem

769

VoiceMSCService

770

VoiceMSCService

771

Event ID (Alarm)

eventId (Trap)

335

367

400

401

608

617

639

799

894

901

997 998

999 257

257

258

259

259 259

1 2

100

257

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

minor Warning This event is generated when the short-term alarm threshold has been

minor Warning A reset has occurred in the Basic Rate Interface or Digital Trunk

warning Information A warm start has been done. No action required. No action required. MSCid=400, Sev=P9, Cat=E minor Warning A search of the terminal address table failed to find a TN that matched

minor Warning Attempt to attach a device type to a port that is not supported in the

minor Warning Cannot acquire a session. This happens only on Companion devices.

minor Warning A bad message has been received by a CAP while getting key

minor Warning A call processing error has occured on an ISDN line. No action

minor Warning An attempt was made to enqueue a message into the DASS2/DPNSS

critical Error Part or all of the telephony system memory has been corrupted. A

warning Information Telephony time discrepancy with the System time has been noted. No

warning Information Telephony time has been synchronized with the System time. No action required. MSCid=998, Sev=P4, Cat=B warning Information Unknown alarm detected. Alarm code: %1. Contact your local support group. MSCid=999, Sev=P7, Cat=B critical Error Less than 5% voice file space avail. to delete voice messages (especially check the General

critical Error All CallPilot ports busy, change resource allocation. All voice ports in use. Enable additional voice ports to avoid

minor Warning Restart BCM, so that change in Call Center refresher channel will take

minor Warning SetPortCapability voice failed - no resource Voice ports need to be allocated for the media services card

warning Information SetServiceStatus PENDING No action required. This event Is NOT passed via the

warning Information SetServiceStatus RUNNING No action required. This event Is NOT passed via the

warning Information SetServiceStatus STOPPED No action required. This event Is NOT passed via the

critical Error Voice Mail may not have started. You may have to restart the system If

critical Error

warning Information Current number of mbxes is greater than keycoded limit If the number of mailboxes initialized is greater than the

warning Information AA/CCR calls cannot be parked since park prefix is set to None. To resolve please configure the park prefix from Unified

warning Information Voice Mail is operational No action required. warning Information Voice Management Subsystem Service started. No action required. warning Information Voice Management Subsystem Service stopped. No action required. minor Warning The 'Restore' of the 'System programming' option has FAILED (Reaso

minor Warning The 'Restore' of the 'System programming' option has FAILED (Reaso

critical Error !* DN length length change detected This is an event which indicates an MSC reset due to an

critical Error !* StartD1Channels: we were told to shutdown the KSU This no longer applies to BCM 3.0. Earlier it was a log

surpassed in the Digital Trunk Interface module for the detection of remote alarm indication in time slot 16. The module is in a no-new-calls state. DTCM = %1. Intervention is required to find out why the Digital Trunk Interface module is alarmed.

Interface module. This event should only occur when the system first boots.

the TN of the device that is initializing and requesting its LAD. The device will fail to initialize. This is a software error that can occur on initialization of any TCM peripheral. Report the problem and the software version.

software. The device will not initialize nor be operational. Verify that all types of attached peripherals initialize and function. Remove any unsupported device types.

Contact the installer to get the traceback data.

information. Contact the installer to get the event traceback data.

required.

layer 3 flow control queue, but the queue was full. The message has been dropped, and will not be sent out to the network. This can arise if the link has gone down but the Digital Trunk Interface module has failed to report it. Port = %1. Customer should report the problem. Installer should verify that the link is operational and the module is still functioning.

coldstart of the telephony subsystem will occur. This problem should be reported. All telephony data will need to be reprogrammed.

Interface module. Determine reason for event and resolve.

action is required.

effect.

problem persists, contact your service representative. These are 259, even though they are errors.

call to SetServiceStatus failed. If Voice Mail has started normally, th no action is required. However Voice Mail may not have started. You may have to restart the system If problem persists, contact your service representative. These are 259, even though they are errors.

internal error.)

open session rejected - auto admin re-eval is occurring, wireless.)

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

Intervention is required to find out why the Digital Trunk Interface module is alarmed.

Obtain the traceback for the module that reset. MSCid=367, Sev=P5, Cat=B

Report the problem and the software version. MSCid=401, Sev=P4, Cat=B

Verify that all types of attached peripherals initialize and function. Remove any unsupported device types.

Contact the installer to get the traceback data. MSCid=617, Sev=P4, Cat=A

Contact the installer to get the event traceback data. MSCid=639, Sev=P4, Cat=A

No action required. MSCid=799, Sev=P7, Cat=B

Customer should report the problem. Installer should verify that the link is operational and the module is still functioning.

Report the problem. All telephony data will need to be reprogrammed.

Determine reason for event and resolve. MSCid=949, Sev=P6, Cat=B

No action is required. MSCid=997, Sev=P1, Cat=B

Delivery Mailbox).

this situation. Restart VoiceMail to have the new Refresher Channel value in effect

so that voice mail will function.

StartServiceCtrlDispatcher failed This event Is NOT passed via the

SetServiceStatus This event Is NOT passed via the

number of mailboxes enabled by keycode when a user attempts to login via unified messaging or the telset this event will be generated. To resolve apply a mailbox expansion keycode to ensure the number of keycoded mailboxes is sufficient to enable all initialized mailboxes.

Manager.

No action required.

administered change to the internal dialling plan length (number of digits). There is no action required.

indicating that the MSC was being put into upload mode. There is no action required.

MSCid=335, Sev=P5, Cat=C

MSCid=608, Sev=P6, Cat=F

MSCid=894, Sev=P4, Cat=C

MSCid=901, Sev=P8, Cat=F

Disk full (data partition) condition.

mbLogMessage API

This typically occurs immediately after a restore to a new system where keycodes have not yet been applied.

shutting down ...

exiting

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

Yes No No No No No

No No No No No No No No No No No No

No No Yes Yes Yes Yes

No No No Yes Yes Yes

No No No No No No

No No Yes No No No

No No No No No No

Yes No No No No No

No No No No No No No No No No No No No No Yes No No No

No No No No No No

BCM Alarms-Traps Page 24

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

d

n

u

o

P

ABCD E F G HIJKLM

Component ID (Alarm)

eventSource (Trap)

2

VoiceRecord

772

VoiceRecord

773

VoiceRecord

774

VoiceRecord

775

VoiceRecord

776

VoiceRecord

777

VoiceRecord

778

VoiceRecord

779

VoiceTimeSynch 1001 warning Information Starting up NTP service version 3.0, server No action required.

780

VoiceTimeSynch 1001 warning Information No Time Adjustment : "Seconds" seconds > max of "Seconds" No action required.

781

VoiceTimeSynch 1001 warning Information No Time Adjustment : "Seconds" seconds > min of "Seconds" No action required.

782

VoiceTimeSynch 1001 warning Information Couldn't get registry information Stop and Start VoiceTimeSync Service

783

VoiceTimeSynch 1001 warning Information time adjustment of "Seconds" seconds > max of "Seconds" No action required.

784

VoiceTimeSynch 1002 critical Error no response from NTP server, check IP number or network connectioncheck IP number or network connection

785

VoiceWatchdog

786

VoiceWatchdog

787

VoiceWatchdog

788

VoiceWatchdog

789

VoiceWatchdog

790

VoiceWatchdog

791

VoiceWatchdog

792

VoiceWatchdog

793

VoiceWatchdog

794

VoiceWatchdog

795

VoiceWatchdog

796

VoiceWatchdog

797

VoiceWatchdog

798

VoiceWatchdog

799

VoiceWatchdog

800

VoIPSipGateway 100 minor Information Service SIP VoIP Gateway Installed No action required.

801

VoIPSipGateway 101 minor Information Service SIP VoIP Gateway Removed No action required.

802

VoIPSipGateway 102 warning Information Service SIP VoIP Gateway started No action required.

803

VoIPSipGateway 105 warning Information Service SIP VoIP Gateway stopped No action required.

804

VoIPSipGateway 110 minor Error Missing Registry Parameter Report error to ITAS Points to a build or upgrade error

805

VoIPSipGateway 113 critical Error Syntax error in configuration registry entry for Address book Check HKLM\\Software\\Nortel Networks\\VoIPGateways\\SI

806

VoIPSipGateway 114 minor Warning Invalid Configuration file parameter Check gateway type parameter in remotegateway.cfg table file

807 808

VoIPSipGateway 120 critical Error Cannot initializet H323 stack Report error to ITAS Windows or file system problem VoIPSipGateway 122 critical Error Cannot read info from license server Report error to ITAS Maybe permissions problem. Refer to

809

Event ID (Alarm)

eventId (Trap)

100

101

102

103

104 105

106

108

1000

1001

1002

1003

1004

1005 1006

1007 2000

3000

3001

3002

3003

3004 3005

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

warning Information Successfully created the VoiceRecord WinNt service. No action required. Can Never Occur on BCM during

warning Information Successfully deleted the VoiceRecord WinNt service. The VoiceRecor

critical Error Failed to delete the VoiceRecord WinNt service.The VoiceRecord

critical Error Init fails. Unexpected WinNt Services initialization error. The control

warning Information The service was started. No action required. critical Error Unexpected services request generated internally or by WinNt Service

warning Information The service was stopped. No action required.

warning Information KSU Down. Telephony services will be stopped temporarily. The alarm

warning Information KSU Reset. Telephony services being restarted and will be up within

warning Information KSU UP. Telephony services being restarted and will be up within

warning Information %Date/Time% Received KSU DN Length change notice No action required. Voice Watchdog received the KSU DN

warning Information Restarting All Monitored Services. No action required. Voice Watchdog restarting the root

warning Information %Service Name% was manually restarted and Watchdog is monitoring

warning Information Watchdog was started as a service No action required warning Information %Service Name% started successfully. No action required minor Warning ATTENTION: Communication with LED panel has been lost. Status

critical Error %Service Name% failed:%#% --> Format Message failed: Unknown

critical Error %Service Name% failed:%#% --> %Error Message%. Start this service manually. If unable to resolve the problem

critical Error Service %Service Name% has reached the failure repeat limit and m

critical Error %Service Name% Start Service failed: The dependent service or group

critical Error %Service Name% Failed to start. Start this service manually. If unable to resolve the problem

critical Error Service %Service Name% stopped unexpectedly. Watchdog will restart this service, No action required.

service was removed.

service could not be removed.

handler could not be installed.

Execution continues. The service received an unsupported request.

its tree again.

LED may not reflect true system status.

error.

be restarted manually

failed to start.

No action required. Can Never Occur on BCM during

No action required.

No action required. Can Never Occur on BCM during

KSU_UP will be received when the telphony services are being restarted.

10~15 minutes.

Length change from the VoiceMSCService, VoiceMSCDriver and all its dependencies will be stopped/Restart. Wait for 15 minutes to get telephone sets back.

service and all it's dependencies. No action required Voice Watchdog started monitoring

Investigate the possible cause in the next maintenance window Call for Support and advise of "unknown error" received Voice Watchdog received an unknow

call for Support and advise of the error message.

Start this service manually. If unable to resolve the problem call for Support. Voice Watchdog encountered the maximum limit of services restarting times and the service needs to be restarted manually.

Start the root service of failed service manually. If unable to resolve the problem call for Support.

call for Support.

Gateway\\Gateway Data\\Address Book entries for correct information.

normal operation

Voice Watchdog received the KSU Down from the VoiceMSCService. All services depending on VoiceMSCService will stopped

Voice Watchdog received the KSU UP from the VoiceMSCService. VoiceMSCDriver and all its dependencies will be stopped/Restarted. Wait for 15 minutes to get telephone sets back.

Voice Watchdog received the KSU UP from the VoiceMSCService, VoiceMSCDriver and all its dependencies will be Restarted. Wait for 15 minutes to get telephone sets back.

this service.

error number from the Service Control Manager while querying the Service Status

Voice Watchdog received error message from the Service Control Manager while querying the Service Status

The service failed to start according t the failure in the root (parent) service. The root service needs to be started manually.

development team

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

No No Yes No No No

No No No No No No

No No No No No No No No No No No No

No No Yes No No No

No No No No No No No No No No No No

No No No No No No

Yes No Yes Yes Yes Yes

Yes No No Yes Yes Yes

Yes No No No No No

Yes No Yes Yes Yes Yes

Yes No No No No No Yes No No No No No

Yes No No Yes Yes Yes Yes No No No No No

Yes No Yes Yes Yes Yes

Yes No No No No No

Yes No Yes No No No

Yes No Yes Yes Yes Yes

Yes No Yes Yes Yes Yes Yes No Yes Yes Yes Yes

No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

No No No No No No

No No No No No No No No No No No No No No No No No No

BCM Alarms-Traps Page 25

BCM3.x_Alarms_SNMPTraps_Issue3.0e_14Nov05.xls

m

ABCD E F G HIJKLM

Component ID (Alarm)

eventSource (Trap)

2

VoIPSipGateway 123 minor Warning Keycode applied for unknown feature Keycode applied for more recent feature than software knows

810

VoIPSipGateway 124 Minor Error Quality of Service monitor connection not established Report error to ITAS May be a Windows resources proble

811

VoIPSipGateway 130 Minor Warning Call setup rejected because of insufficient QoS bandwidth Confirm engineering traffic guidelines for network

812

VoIPSipGateway 131 minor Warning Dropped connected call from DN X to DN Y. Incompatible codecs or

813

VoIPSipGateway 200 major Error Generic System Error A wide assortment of problems. See event text for details. Report error to ITAS to inform

814

VoIPSipGateway 201 major Warning Generic System Warning A wide assortment of problems. See event text for details. Report error to ITAS to inform

815

VoIPSipGateway 202 Major Warning Registry import problems Report error to ITAS Problem with importing vngway.reg

816

VoIPSipGateway 203 Major Warning Registry import problems Report error to ITAS Problem with importing vngway.reg

817

VoIPSipGateway 204 Major Warning Registry import problems Report error to ITAS Problem with importing vngway.reg

818

Wins

819

Wins

820

WINSCTRS

821

Workstation

822

Event ID (Alarm)

eventId (Trap)

4097

4098 4314

3870

Alarm Severity Trap-Type Problem Description (Alarm) / eventDescr (Trap) Action Req'd Comments

of.

configuration

insufficient media gateway resources

warning Information WINS HAS INITIALIZED PROPERLY AND IS NOW FULLY

warning Information WINS was terminated by the service controller. Wins will gracefully

critical Error WINSCTRS could not get the WINS statistics. No action required. critical Error "System Name" is not a valid computer name. The BCM name should be unique in the network.

OPERATIONAL.

terminate.

Change or make available the correct Codec to match the Codec supported by the software at the far end of the call.

No action required.

Confirm Keycode server operation

that could require a reboot

Only shows in Event Viewer no Trap

designers

New/Changed in BCM3.5 New/Changed in BCM3.6/3.7 BCM 3.0 BCM 3.5 BCM 3.6 BCM 3.7

No No No No No No

No No No No No No No No No No No No

No No No No No No

BCM Alarms-Traps Page 26

Avaya BCM3.x User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual