Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Fault Management: Events Overview

    The Fault Management: Events chapter of the Management and Monitoring Guide for IP/MPLSView describes how to use the Event Browser to monitor events and SNMP traps from devices in the live network. The Event Browser can be accessed from the Web Portal or the Desktop Client. The instructions provided in this document apply to both methods of accessing the Event Browser.

    IP/MPLSView’s Fault Management solution is comprised of three main topics:

    • The Event Browser and Event Map are used to record and view events and SNMP traps from devices in a live network. This can be used to monitor changes to the network such as link down/up status, LSP tunnel up/down status, VPN status, application errors, and many other types of events. In addition to viewing events, the Event Browser allows you to manage these items by acknowledging and clearing events that require attention (explained later). Advanced options are also available to define new traps.
    • The Subscription Editor is used to set up e-mail/SMS subscriptions to events of particular interest. Advanced options are also available to set up UDP and JMS subscriptions for use with third-party interfaces, or to forward traps northbound to another third-party management system. See Subscription Editor for more details.
    • The Threshold Editor is used to create threshold crossing alerts. For example, threshold events can be generated when link utilization, or CPU utilization, exceeds a certain percentage. See Fault Management: Threshold Crossing Alerts Overview for more details.

    To see trap data via the Event Browser, the network devices must be configured to send and receive SNMP trap messages. This setup can include setting up SNMPv2c community strings and read/write authorizations or SNMPv3 authentication as well as categories of traps that will be enabled (or all). Refer to your device’s manual for the relevant commands

    After configuring your network routers to send and receive SNMP trap messages, you must configure for the devices to send traps to the IP/MPLSView server by including the IP/MPLSView server’s IP address as one of the target hosts. If the IP/MPLSView server has more than one IP address, use the IP address that is used to reach the network routers, and set it accordingly as the SNMP Trap Server IP address (SNMP Trap Daemon IP) during the IP/MPLSView installation, or via changeconfig.sh. Example router configuration statements are included in the table below:

    For details about creating customized traps, refer to Configuring the SNMP Traps and Events to Record (Advanced).

    The IP/MPLSView SNMP trap server also needs to be started up in order to receive SNMP traps. When running the /u/wandl/bin/startup_mplsview command, answer “y” when asked “Would you like to start the SNMP Trap Server”. To check if the trap server is up, run /u/wandl/bin/status_mplsview and check whether or not the SNMP Trap Server Process is detected. If everything else is started up, you can start up just the trap server individually using the command “/u/wandl/bin/.snmptrap start”.

    Finally, the Fault Management: Events chapter assumes that you already done a live network collection and have one or more devices in their live network topology. To schedule a live network collection, see Live Network Collection Overview.

    The Event Browser keeps a record of events, including

    Modified: 2016-11-08