The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to configure the events for fault management on the Cisco cBR Series Converged Broadband Router.
Fault management on RPD is required for remote monitoring, detection, diagnosis, reporting, and correcting the issues.
The Fault management module provides the following support:
RPD can send events to the CCAP core
CCAP core can get events from RPD
Send RPD events using SNMP traps
On the CCAP core, view log in to the CLI
SNMP poll events are supported
An RPD logs events, generates asynchronous notifications that indicate malfunction situations, and notifies the operator about important events. The RPD event reporting includes two methods of reporting.
During the initialization of RPD, CCAP core synchronizes events from the RPD.
During run-time operations, RPD notifies the CCAP Core of the events
Following restrictions are applicable:
A maximum of 1000 events are retained on Cisco cBR. The RPD retains 1000 events locally and 1000 events in pending state.
Note | To know more about the commands referenced in this module, see the Cisco IOS Master Command List. |
enable configure terminal cable profile rpd-event profile_id priority {emergency|alert|critical|error|warning|notice|informational|debug} {0x0|0x1|0x2|0x3} enable-notify
0x0—No log
0x1— Save log in RPD local storage
0x2—Report to Cisco cBR
0x3— Save log in RPD local storage and report to Cisco cBR
You must enable-notifications for the RPD to report any event to the Core.
enable configure terminal cable rpd rpd_name rpd-event profile profile_id
Note | If RPD is online when changing the profile, reset the RPD, after you change the profile. |
enable configure terminal snmp-server enable traps rpd-event priority
Priority can be 1-8, where:
1—Enable RPD event trap for emergency priority
2— Enable RPD event trap for alert priority
3—Enable RPD event trap for critical priority
4— Enable RPD event trap for error priority
5— Enable RPD event trap for warning priority
6— Enable RPD event trap for notice priority
7— Enable RPD event trap for informational priority
8— Enable RPD event trap for debug priority
The priority higher than the selected priority is also displayed.
You can configure SNMP trap server on the cable modem using the following commands:
enable cnfigure terminal Router# snmp-server host ip_address traps version 2c public udp-port port_number
where,
ip_address—IP address of the server
port_number—UDP port number assigned to receive the SNMP traps. The same port number must also be configured on the SNMP server.
Router#cable rpd 30.84.2.111 event pending
Router#clear cable rpd all event
Router# show cable rpd 93.3.50.7 event RPD EventId Level Count LastTime Message 0004.9f00.0861 66070204 Error 1 Feb21 12:11:06 GCP Connection Failure CCAP-IP=30.85.33.2;RPD-ID=0004.9f00.0861; 0004.9f00.0861 2148074241 Error 1 Feb21 12:11:25 Session failed:connecting timeout, @SLAVE: 93.3.50.7:None --> 30.85.33.2:8190;RPD-ID=0004.9f00.0861;
Router# show logging | include RPD-ID=0004.9f00.0861 004181: Feb 21 12:18:59.649 CST: %RPHYMAN-3-RPD_EVENT_ERROR: CLC5: rphyman: GCP Connection Failure CCAP-IP=30.85.33.2;RPD-ID=0004.9f00.0861;EVENT-ID=66070204; FirstTime=2017-2-21,12:11:6.0; LastTime=2017-2-21,12:11:6.0; Count=1;PendingQueue; 004185: Feb 21 12:19:18.875 CST: %RPHYMAN-3-RPD_EVENT_ERROR: CLC5: rphyman: Session failed:connecting timeout, @SLAVE: 93.3.50.7:None --> 10.10.10.12:1190; RPD-ID=0004.9f00.0861; EVENT-ID=2148074241; FirstTime=2017-2-21,12:11:25.0; LastTime=2017-2-21,12:11:25.0; Count=1;PendingQueue;
This section provides example for the fault management configuration on Cisco cBR-8.
enable configure terminal cable profile rpd-event 6 priority emergency 0x3 priority alert 0x3 priority critical 0x3 priority error 0x3 priority warning 0x3 priority notice 0x3 priority informational 0x3 enable-notify cable rpd node6 identifier badb.ad13.5e08 core-interface Te3/1/5 principal rpd-ds 0 downstream-cable 3/0/17 profile 10 rpd-us 0 upstream-cable 3/0/34 profile 13 r-dti 16 rpd-event profile 6
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note | The table below lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. |
Feature Name |
Releases |
Feature Information |
---|---|---|
R-PHY Fault Management |
This feature was integated into the Cisco Remote PHY Device. |