RMS Alarms

RMS Alarms
RMS Alarms
• Upload Server Alarms, page 1
• Upload Server Syslog Messages, page 2
• PMG Alarms, page 2
• PAR System Alarms, page 4
• PNR System Alarms, page 4
• PNR Syslog Messages, page 4
• BAC Alarms, page 5
• BAC Syslog Messages, page 6
• RMS Alarms for AP Accessibility, page 7
Upload Server Alarms
The Upload Server includes the SNMP alarm support that uses the CISCO-MHS MIB in triggering Upload
server alarms. This table includes some of the Upload Server alarms triggered during the monitoring of the
Upload Server processes. In all of these traps, the value of the trap is provided in the ciscoMhsAlarmDescription
Object which has OID 1.3.6.1.4.1.9.9.9999.1.13.
Table 1: Upload Server Alarms
OID
Trap
Description
1.3.6.1.4.1.9.9.9999.0.5
Upload Server exited
unexpectedly
Upload Server watchdog process
Critical (1)
"god" is not running on the Upload
Node
1.3.6.1.4.1.9.9.9999.0.6
Upload Server has started Upload Server watchdog process
"god" is running on the Upload
Node
Clear (6)
1.3.6.1.4.1.9.9.9999.0.5
Disk Usage exceeds
Warning Threshold
Warning (4)
Log Upload server disk utilization
is going high
Severity
Cisco RAN Management System SNMP/MIB Guide, Release 4.1
September 10, 2014
1
RMS Alarms
Upload Server Syslog Messages
OID
Trap
Description
Severity
1.3.6.1.4.1.9.9.9999.0.5
Disk Usage exceeds
Critical Threshold
Log Upload server disk utilization
is in critical state
Critical (1)
1.3.6.1.4.1.9.9.9999.0.5
Disk Usage reached Info Log Upload server disk utilization
Level
will be high soon
Informational
(7)
Configuring SNMP Traps for Upload Server
To configure the SNMP traps for the Upload Server, navigate to /opt/CSCOuls/conf/ folder and modify the
UploadServer.properties files as follows:
alarms.snmp.nummanagers=1
alarms.snmp.manager.address.1=<ip address of the snmp destination>
alarms.snmp.manager.port.1=162
alarms.snmp.manager.community.1=movmmt+21
For information about Upload Server syslog messages, see Upload Server Syslog Messages, on page 2.
Upload Server Syslog Messages
This table lists some of the Upload Server conditions and the corresponding syslog messages generated as
output for the Upload Server alarms. For more information, see Upload Server Alarms.
Table 2: Upload Server Syslog Messages
Conditions
Syslog Messages
Upload Server process has started.
UploadServer [trigger] process is running
(ProcessRunning)
Upload Server process has stopped.
UploadServer has stopped
Upload Server disk usage exceeds the INFO threshold "AlarmEvents Total disk utilization: exceeds INFO
threshold"
Upload Server disk usage exceeds the WARNING
threshold
"AlarmEvents Total disk utilization: exceeds
WARNING threshold"
Upload Server disk usage exceeds the CRITICAL
threshold
"AlarmEvents Total disk utilization: exceeds
CRITICAL threshold"
PMG Alarms
The Provisioning and Management Gateway (PMG) triggers alarms for the following conditions and these
logs are logged to the file "pmg-alarm.log". PMG raises ciscoMhsServerAlarm and ciscoMhsServerAlarmClear
alarms that are defined in the CISCO-MHS MIB.
Cisco RAN Management System SNMP/MIB Guide, Release 4.1
2
September 10, 2014
RMS Alarms
PMG Alarms
This table lists the traps logged for the PMG. In all of these traps, the value of the trap is provided in the
ciscoMhsAlarmDescription Object which has OID 1.3.6.1.4.1.9.9.9999.1.13.
Table 3: PMG Alarms
OID
Trap
Description
Severity
1.3.6.1.4.1.9.9.9999.0.5
PMG server is terminated pmgServer.sh has stopped Critical (1)
or the PMG server has
terminated abruptly
1.3.6.1.4.1.9.9.9999.0.6
PMG server has started
pmgServer.sh has started Clear (6)
1.3.6.1.4.1.9.9.9999.0.5
Connection with RDU
lost
RDU connection is lost Major (2)
and PMG cannot connect
to the RDU
1.3.6.1.4.1.9.9.9999.0.6
Connection with RDU
established
Clear (6)
1.3.6.1.4.1.9.9.9999.0.5
Northbound connection
limit approaching
PMG NBI connections
Warning (4)
are approaching the limit
specified in
pmg.max.connections
property in
PMGServer.properties
1.3.6.1.4.1.9.9.9999.0.5
Northbound connection
limit exceeded
PMG NBI connections
exceeded the limit
specified in
pmg.max.connections
property in
PMGServer.properties
Critical (1)
Configuring SNMP Traps for PMG
The following are the SNMP trap destination configuration in the PMGServer.properties file.
• Number of SNMP Trap destinations - pmg.alarms.snmp.nummanagers
• IP address, Port, and community String per SNMP destination - Multiple SNMP trap destinations are
configured as below:
#Alarm
pmg.alarms.snmp.nummanagers=2
pmg.alarms.snmp.manager.address.1=127.0.0.1
pmg.alarms.snmp.manager.port.1=162
pmg.alarms.snmp.manager.community.1=public
pmg.alarms.snmp.manager.address.2=10.30.34.22
Cisco RAN Management System SNMP/MIB Guide, Release 4.1
September 10, 2014
3
RMS Alarms
PAR System Alarms
PAR System Alarms
This table lists the Prime Access Registrar (PAR) system alarms that are triggered during the monitoring of
the processes. For more information refer to CISCO-ACCESS-REGISTRAR-MIB.
Table 4: PAR System Alarms
OID
Trap
Description
Severity
1.3.6.1.4.1.9.10.70.2.0.2
PAR Sever stop
Server has stopped
Critical (1)
normally on the host from
which this notification is
sent
1.3.6.1.4.1.9.10.70.2.0.1
PAR Server start
Clear (6)
For details about configuring SNMP destinations for receiving PAR Alarms, see the "Using SNMP" section
in the Cisco Access Registrar, 5.1 User Guide ( http://www.cisco.com/en/US/docs/net_mgmt/access_registrar/
5.1/user/guide/CAR5.1_usersguide.pdf).
PNR System Alarms
This table lists the Prime Network Registrar (PNR) system alarms that are triggered during the monitoring of
the processes.
Table 5: PNR System Alarms
OID
Trap
Description
Severity
1.3.6.1.4.1.9.10.70.2.0.4
ciscoNetRegServerStop
Critical (1)
1.3.6.1.4.1.9.10.70.2.0.3
ciscoNetRegServerStart
Clear (6)
For information about the PNR syslog messages, see PNR Syslog Messages, on page 4.
For details about configuring SNMP destinations for receiving PNR Alarms, see the "Simple Network
Management" section in the Cisco Prime Network Registrar 8.1 User Guide (http://www.cisco.com/en/US/
docs/net_mgmt/prime/network_registrar/8.1/user/guide/CPNR81UserGuide.pdf ).
PNR Syslog Messages
This table lists the Prime Network Registrar (PNR) syslog messages generated as output for the PNR alarms.
For more information, see PAR System Alarms, on page 4.
Cisco RAN Management System SNMP/MIB Guide, Release 4.1
4
September 10, 2014
RMS Alarms
BAC Alarms
Table 6: PNR Syslog Messages
Conditions
Syslog Messages
Indicates that the PNR watchdog/main process
<Date-time> <hostname> NR.cnrservagt[8524]: Info:
"cnrseragt " has successfully exited. For example, 0 08059 server agent exiting.
Aug 6 11:55:44 dkukrety-lnx NR.cnrservagt
[10263]: Info: 0 08002 Network Registrar
8.3 build
#8.3.1408012132
Aug 6 11:55:44 dkukrety-lnx
NR.cnrservagt[10263]:
Info: 0 08005 CNR server agent startup,
local mode
…..
<Date-time> <hostname> NR.cnrservagt[8524]:
Info: 0 08059 server agent exiting.
Indicates that the PNR watchdog/main process
"cnrservagt" has started on the host. For example,
<Date-time> <hostname> NR.cnrservagt[8210]: Info:
0 08005 CNR server agent startup, local mode
<Date-time> <hostname> NR.dns[10267]:
Info: 0 00102 name/dns (Domain Name Server
Release
Build) startup
BAC Alarms
This table lists the Broadband Access Center (BAC) alarms that are triggered during the monitoring of the
processes. For more information, see CISCO-BACC-SERVER-MIB.my.
Table 7: BAC Alarms
Note
OID
Trap
Description
1.3.6.1.4.1.9.9.349.0.1
DPE process has stopped
BAC server DPE is offline
1.3.6.1.4.1.9.9.349.0.1
DPE process has started
BAC server DPE is ready
1.3.6.1.4.1.9.9.349.0.1
RDU process has stopped
BAC server RDU is offline
1.3.6.1.4.1.9.9.349.0.1
RDU process has started
BAC server RDU is ready
The BAC alarms carry no explicit severity information. Refer to the following objects to determine for
which server the alarm is raised and the exact state of the server.
Cisco RAN Management System SNMP/MIB Guide, Release 4.1
September 10, 2014
5
RMS Alarms
BAC Syslog Messages
Table 8: Objects Related to BAC Alarms
Object
OID
Possible Values
cbsState
1.3.6.1.4.1.9.9.349.1.1.1.1.3 1—Unknown
2—Initializing
3—Disconnected
4—Shutting Down
5—Ready Overload
6—Ready
7—Offline
8—Unlicensed
cbsServerType
1.3.6.1.4.1.9.9.349.1.1.1.1.6 DPE
Description
Current state of the
server. Values of 3, 4 and
7 can be considered
Critical. A value of 6 can
be considered as a Clear.
Values of 1 and 8 should
be considered major. A
value of 2 can be
considered informational.
A value of 5 can be
considered minor.
Server to which the alarm
applies.
RDU
For information about the BAC syslog messages, see BAC Syslog Messages, on page 6.
For details about configuring SNMP destinations for receiving BAC Alarms , see the Configuring SNMP
Trap for CPEs section in Cisco Broadband Access Center Administration Guide 3.8.1 (http://www.cisco.com/
c/en/us/td/docs/net_mgmt/broadband_access_center/3-8-1/administration/guide/Cisco_BAC381_Admin_Guide/
chap_4.html#pgfId-1042091). This configuration is also applicable for sending access point generated alarms
to NMS/EMS; for example, Prime Central.
BAC Syslog Messages
This table lists the Broadband Access Center (BAC) syslog messages generated as output for the BAC alarms.
For more information, see BAC Alarms, on page 5.
Condition
Syslog Messages
Notifies that the DPE hard drive is full.
"DPE out of disk space"
Indicates that the DPE process has run out of memory.
"DPE out of memory"
Indicates that the RDU cannot be contacted.
"Failed to connect to RDU"
Indicates that the DPE is connected to the RDU.
"Connected to RDU"
Indicates that process watchdog failed to start the DPE
process.
"Failed to start DPE process"
Process watchdog detects that the DPE process
unexpectedly terminated.
"DPE process terminated"
Cisco RAN Management System SNMP/MIB Guide, Release 4.1
6
September 10, 2014
RMS Alarms
RMS Alarms for AP Accessibility
Indicates that process watchdog failed to start the DPE
process.
"DPE process has started"
Indicates that the DPE process is stopped.
"DPE process has stopped"
Indicates that the DPE watchdog process "
"Process watchdog is not running (DPE)"
bpr_agent
" is not running on the host.
Indicates that the DPE watchdog process "bpr_agent" is
running on the host.
"Process watchdog is running (DPE)"
Indicates that RDU is out of disk space.
"RDU out of disk space"
Indicates that RDU is out of memory.
"RDU out of memory"
Indicates that RDU is running out of licenses.
"RDU is running out of licenses"
Indicates that process watchdog failed to start the RDU
process.
"Failed to start RDU process"
Triggered when the process watchdog detects the RDU
process unexpectedly terminated.
"RDU process terminated'
Indicates that process watchdog failed to start the RDU
process.
"RDU process has started"
Indicates that the RDU process is stopped.
"RDU process has stopped"
Indicates that the RDU process is stopped.
"RDU process has stopped"
This alarm is triggered when the process watchdog detects "The tomcat unexpectedly terminated"
that the webserver which runs PMG and UI services has
unexpectedly terminated.
This alarm indicates that the process watchdog failed to
start the web server which runs PMG and UI services.
"The tomcat has started"
This alarm indicates that the web server which runs PMG "The tomcat has stopped"
and User Equipment (UE) is stopped.
RMS Alarms for AP Accessibility
The AP Unreachable Alarm is raised when the AP goes down abruptly and breaks the connection between
the FAP and Cisco RMS. To enable this alarm, see the "AP Unreachable Alarm" section of the Cisco RAN
Management System Administration Guide.
Cisco RAN Management System SNMP/MIB Guide, Release 4.1
September 10, 2014
7
RMS Alarms
RMS Alarms for AP Accessibility
Whenever location verification for a particular small cell (AP) device fails, Cisco RMS raises an AP Location
Verification Failure Alarm for that device. To enable this alarm, see the "AP Location Verification Alarm"
section of the Cisco RAN Management System Administration Guide.
The following table lists the AP alarms.
OID
Trap
Description
Severity
1.3.6.1.4.1.9.9.311.1.1.2.1.16 AP Location
Verification Failure
AP device location
Major (2)
verification has failed, its
location is considered
invalid, and the device is
not activated by RMS
1.3.6.1.4.1.9.9.311.1.1.2.1.16 AP Unreachable
AP is not reachable from Major (2)
Cisco RMS and is not
responsive to the
connection request
To view a clear trap for either of these notifications, look for the clear value of "6" in the Object
cenAlarmSeverityDefinition which has OID of 1.3.6.1.4.1.9.9.311.1.1.2.1.18.
Cisco RAN Management System SNMP/MIB Guide, Release 4.1
8
September 10, 2014
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising