- Overview of Prime Network GUI clients
- Setting Up the Prime Network Clients
- Setting Up Change and Configuration Management
- Setting Up Vision Client Maps
- Setting Up Native Reports
- Setting Up Fault Management and the Events Client Default Settings
- Viewing Devices, Links, and Services in Maps
- Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties
- Manage Device Configurations and Software Images
- How Prime Network Handles Incoming Events
- Managing Tickets with the Vision Client
- Viewing All Event Types in Prime Network
- Cisco Path Tracer
- Managing IP Address Pools
- Monitoring AAA Configurations
- Managing DWDM Networks
- Managing MPLS Networks
- Managing Carrier Ethernet Configurations
- Managing Ethernet Networks Using Operations, Administration, and Maintenance Tools
- Monitoring Carrier Grade NAT Configurations
- Monitoring Quality of Service
- Managing IP Service Level Agreement (IP SLA) Configurations
- Monitoring IP and MPLS Multicast Configurations
- Managing Session Border Controllers
- Monitoring BNG Configurations
- Managing Mobile Transport Over Pseudowire (MToP) Networks
- Managing Mobile Networks
- Managing Data Center Networks
- Monitoring Cable Technologies
- Monitoring ADSL2+ and VDSL2 Technologies
- Monitoring Quantum Virtualized Packet Core
- VSS Redundancy System
- Icon Reference
- Permissions Required to Perform Tasks Using the Prime Network Clients
- Correlation Examples
- Managing certificates
Cisco Prime Network User Guide, 5.1
Bias-Free Language
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.
- Updated:
- January 14, 2019
Chapter: Setting Up Fault Management and the Events Client Default Settings
Setting Up Fault Management and the Events Client Default Settings
The following topics describe how to use the Events client to view and manage faults:
- Workflow for Setting Up Fault Management
- Check Global Settings for the Events and Vision Clients
- Making Sure Devices Are Configured Correctly
- Setting Up Your Events View
- Creating Ticket and Event Filters for Vision and Events Client Users
Whether you can perform these setup tasks depends on your account privileges. See Permissions Required to Perform Tasks Using the Prime Network Clients for more information.
Workflow for Setting Up Fault Management
Most of the fault management setup tasks are documented in the Cisco Prime Network 5.1 Administrator Guide and should already be completed. The following table provides the basic workflow for the remaining fault management setup tasks.
|
|
|
|
|---|---|---|
Check the global setting that control when tickets are auto-cleared and auto-archived, when a cleared ticket can no longer be reopened, whether raw events are saved, and when data is purged from the Oracle database |
||
Check the device setup tasks to see if there are any changes you need to make, such as enabling SNMP traps |
||
Adjust the Events client settings (client refresh interval, age of events to display, number of events to display) |
||
(Optional) Create event filters and save them so you can use them as needed |
Creating Ticket and Event Filters for Vision and Events Client Users |
|
Check Global Settings for the Events and Vision Clients
The following fault-related actions are controlled from the Administration client:
- The Vision client and Events client operations users can perform, and the devices users can view and manage. When a user account is created, the administrator assigns:
–
A user access level to the user account (Viewer, Operator, Operator Plus, Configurator, or Administrator). It controls what actions the user can perform using the Vision client, such as clearing or adding notes to tickets).
– One or more device scopes. Device scopes determine which devices a user has permission to access, and the actions a user can perform on those devices. For example, a user might have sufficient privileges to clear a device ticket, but the user can only do so if the device is in their device scope.
For a matrix of actions users can perform depending on their user access level and device scope assignments, see Permissions Required to Perform Tasks Using the Prime Network Clients.
The following default settings are configured from the Administration client:
For more information on how Prime Network responds to incoming events, see How Prime Network Handles Incoming Events.
Users with Administrator privileges can change these settings by following the directions in the Cisco Prime Network 5.1 Administrator Guide.
Making Sure Devices Are Configured Correctly
In order for Prime Network to fully model and manage faults on your devices and network, the NEs must be configured correctly so that Prime Network can get the information it needs. A complete list of required and recommended configurations is provided in an appendix to the Cisco Prime Network 5.1 Administrator Guide.
You can make most required configuration changes using commands that are packaged with Prime Network. To launch these commands, right-click an NE and choose Commands. Whether or not you can run these commands depends on your user privileges. See these topics for information on how to use these packaged commands:
- Changing the SNMP Configuration and Managing SNMP Traps
- Changing Device Port Properties and Disabling Ports
- Changing Device Interface Properties and Disabling Interfaces
- Changing Server Settings for DNS, NTP, RADIUS, and TACACs
Other commands are described throughout this document with the services and technologies they apply to.
Configuring Prime Network to Support Unmanaged Devices
You can configure Prime Network to also support events from unmanaged devices. Prime Network can then include these devices in its reports, and you can configure an Event Notification Service to forward these events to northbound clients.
To enable support for unmanaged devices, you must configure the support using the Prime Network Broadband Query Language (BQL) as described in the Cisco Prime Network Integration Developer Guide.
An Event Notification Service can be configured using the Administration client as described in Cisco Prime Network 5.1 Administrator Guide.
Setting Up Your Events View
The Events client Options dialog box enables you to change various aspects of the event display in Events client.
To set up your events view, choose Tools > Options from the main menu. Table 6-1 lists the available options.
Creating Ticket and Event Filters for Vision and Events Client Users
The Vision client and Events client both support a filtering mechanism that lets you create filters and save them for later use. Filters created in a client can be shared, which means other users of the same client can access and run the filters. The following table describes the filters you can create from the two clients and where to get more information.
|
|
|
|
|---|---|---|
|
|
||
|
|
||
Trap events and Syslog events from unmanaged devices (if enabled) |
||
Viewing Investigation Ticket Information
The information ticket is generated only when the investigation-state-update-ticket option is enabled. By default, this option is enabled.If you require to disable the option, the below run registry tool command is given:
runRegTool.sh -gs localhost set 0.0.0.0 agentdefaults/da/investigation-progress/investigation-state-update-ticket false
VNEs undergo multiple investigation states in its lifecycle. The tracking of information is enabled as Information tickets. Using these tickets, you can receive notification if the state of the VNEs is changed.
The information ticket is generated once the VNE is started and the same ticket is updated whenever the VNE state changes in its lifecycle. Once the VNE comes to the Operational state, the ticket is cleared.
Once a ticket is opened, you can view the reason for each state in the Details pane. You can view the history details of a particular ticket with information on various states of the ticket in the History window. Figure 6-1 provides the details of ticket information
Figure 6-1 Viewing Investigation Ticket Information
Once a ticket is opened, you can view the reason for each state in the Details pane. You can view the history details of a particular ticket with information on various states of the ticket in the History window. Figure 6-2 displays the information ticket in Details pane.
Figure 6-2 Viewing the Investigation Ticket Information in Details Pane
Monitoring Alarms/Events in Prime Network (Event Manager)
In the devices like ASR 903 or ASR 9K, we have monitored service alarms/events to find out the time taken by Prime network to generate the service alarms/events whenever changes on devices such as interface/port/link down or vice versa. Prime Network has the option of monitoring the time taken to generate the alarms /events for the following:
The Status of the device will be in Disabled when there is any interface /port /link is down in physical inventory and the status will be in OK state if the same is up. Refer Figure 6-3.Whenever there is change in status in physical inventory, the Prime Network event manager generates the events.
Figure 6-3 Viewing the Status of the device
Figure 6-4displays the various investigation states of VNEs
Figure 6-4 Viewing various investigation states of a VNE
The monitoring of alarms /events has been carried out using two types of polling:
Reduced Polling—It is a default polling which provides the time taken by Prime Network for checking any change in the device.
Regular Polling— In regular polling, the time taken by Prime Network for checking any change in device will be more than Reduced Polling.
Feedback