Home > Cisco > Network Hardware > Cisco Prime Nerk 43 User Guide

Cisco Prime Nerk 43 User Guide

    Download as PDF Print this page Share this page

    Have a look at the manual Cisco Prime Nerk 43 User Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 53 Cisco manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    Page
    of 1168
    							  
    5-11
    Cisco Prime Network 4.3.2 User Guide
    Chapter 5      Setting Up Native Reports
      Entering Report Criteria and Testing Your Report
    General Criteria:
    Special Criteria for Traps:
    Report Settings
    Report SecurityNoteThis field is displayed only if report sharing is enabled. See 
    Checking Global Settings for Report Operations, page 5-2.
    Private—Can only be viewed by creator. 
    Public—Can be viewed by all users, even if the devices are outside their 
    scope.
    If sharing is enabled, this setting can be changed after the report is created 
    (by right-clicking the report and selecting Share or Unshare).
    Display n  Number of items to be displayed in report.
    Data Source Run report based on actionable or generic events
    Include pie charts in 
    report outputAlso generate pie chart.
    Device Selection
    Select Devices To select specific devices:
    1.Click Select Devices. 
    2.Click Add. 
    3.In the Add Network Element dialog box: 
    –Click Search to find NEs based on your criteria.
    –Click Show All to choose from a list of all NEs.
    4.Select the NEs and click OK. 
    Traps Detailed 
    DescriptionInclude traps with descriptions that match string.
    Long 
    Description(Actionable events) Include traps that have string in their long description.
    1.Check Show Long Description check box. 
    2.Enter the string that the trap long description must contain.
    SNMP Version (Generic events) SNMP versions to include in the report: All, 1, 2, or 3. 
    Generic Include generic (non-actionable) traps:
    All All generic traps
    0coldStart
    1 warmStart
    2 linkDown
    3 linkUp
    4 authenticationFailure
    5 egpNeighborLoss
    6 enterpriseSpecific (enter comma-separated OIDs, up to 125 digits, in Vendor 
    Specific field) 
    						
    							  
    5-12
    Cisco Prime Network 4.3.2 User Guide
    Chapter 5      Setting Up Native Reports
      Scheduling a Recurring Report
    Step 4Click the Scheduling tab and choose Run Now. 
    Step 5Verify the results in Report Manager or when the report is displayed in the web browser.
    Scheduling a Recurring Report
    To schedule a recurring customized report, use the Report Manager. If you want to schedule a predefined 
    report, you can run it from Report Manager or directly from the Prime Network client Reports menu. To 
    run a report immediately, click the Schedule tab and choose Run Now.
    To schedule a report:
    Step 1Select the report you want to schedule.
    Step 2Supply your report criteria. 
    Step 3Click the Scheduling tab and give the job a meaningful title (for example, 24-Hour Ticket Report Job).
    Step 4Enter the schedule criteria—for example: Recurring, Daily, Run Indefinitely, and from the current time 
    for 30 days.
    Once you schedule a job, the job information can only be edited from the Job Manager by choosing 
    Tools > Schedule Job from the Vision client main menu. You can also rerun the job and clone the job 
    using the Job Manager.
    Sending a Report Through E-mail Notification
    To send a report, you can enter the e-mail notification criteria in the Create Report window. If e-mail 
    notification details are provided, you can run the report and automatically the report is mailed as an 
    attachment in a desired format. You can attach reports in the XML, PDF, CSV, XLS, or HTML format.
    To enter criteria and send a report through e-mail notification:
    Step 1Select Reports > Report Manager. In the Reports Manager window, expand either one of the Events 
    Reports, Inventory Reports, or Network Service Reports node.
    NoteYou can also create and send a report by using the following navigation path:
    Select Reports >Run Report >Events Reports > click a report
    Select Reports >Run Report >Inventory Reports > click a report.
    Select Reports >Run Report >Network Service Reports > click a report. Report Type Run From Main Menu:
    Predefined reports that come with Prime NetworkReports > Run Report
    Customized reports (reports you modified and 
    saved)Reports > Report Manager > Run Report 
    						
    							  
    5-13
    Cisco Prime Network 4.3.2 User Guide
    Chapter 5      Setting Up Native Reports
      Sending a Report Through E-mail Notification
    Step 2Choose a report> right-click a selected report> click Run. The Create Report page appears. 
    Figure 5-1 E-mail Notification Tab
    Step 3
    Click the E-Mail Notifications tab, enter a valid Email Servers, To-Address, From-Address (es), and 
    Subject details.
    NoteIf you have configured the Email Server and From Address in the Global Report Settings then 
    those details will be displayed by default.
    Step 4From the Attach results as drop-down list, choose a report format to attach in an email. 
    Step 5Click OK to create a report and to send the report as an attachment. 
    						
    							  
    5-14
    Cisco Prime Network 4.3.2 User Guide
    Chapter 5      Setting Up Native Reports
      Sending a Report Through E-mail Notification 
    						
    							CH A P T E R
      
    6-1
    Cisco Prime Network 4.3.2 User Guide
    6
    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, page 6-1
    Check Global Settings for the Events and Vision Clients, page 6-2
    Making Sure Devices Are Configured Correctly, page 6-3
    Setting Up Your Events View, page 6-4
    Creating Ticket and Event Filters for Vision and Events Client Users, page 6-5
    Whether you can perform these setup tasks depends on your account privileges. See Permissions 
    Required to Perform Tasks Using the Prime Network Clients, page B-1 for more information.
    Workflow for Setting Up Fault Management
    Most of the fault management setup tasks are documented in the Cisco Prime Network 4.3.2 
    Administrator Guide and should already be completed. The following table provides the basic workflow 
    for the remaining fault management setup tasks.
    Description See:
    Step 1Check 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 databaseCheck Global Settings for the Events 
    and Vision Clients, page 6-2
    Step 2Check the device setup tasks to see if there are any changes 
    you need to make, such as enabling SNMP trapsMaking Sure Devices Are Configured 
    Correctly, page 6-3
    Step 3Adjust the Events client settings (client refresh interval, age 
    of events to display, number of events to display)Setting Up Your Events View, page 6-4
    Step 4(Optional) Create event filters and save them so you can use 
    them as neededCreating Ticket and Event Filters for 
    Vision and Events Client Users, 
    page 6-5 
    						
    							  
    6-2
    Cisco Prime Network 4.3.2 User Guide
    Chapter 6      Setting Up Fault Management and the Events Client Default Settings
      Check Global Settings for the Events and Vision Clients
    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, 
    page B-1.
    The following default settings are configured from the Administration client:
    Step 5(Optional) Extend Prime Network:
    Download and install new events support using Prime 
    Network Device Packages (DPs) Cisco Prime Network 4.3.2 
    Administrator Guide
    Add support for customized events and 
    threshold-crossing alarmsCisco Prime Network 4.3.2 
    Customization Guide Description See:
    Options Description Default Setting
    Events client 
    loginUser access role that is required to log in to the Events client (the 
    Events client is for advanced users).Administrator
    Locking cleared 
    ticketsAge at which a cleared. ticket can no longer be reopened or have 
    new events added to it.Disabled
    Auto-clearing 
    ticketsAuto-clear tickets if they meet the following criteria:
    Is the specified severity (or lower), and 
    Has not been modified for a specified period of days.Disabled
    Auto-archiving 
    cleared ticketsMove the ticket from an active to an archive partition in the Oracle 
    database and it begins aging.
    When the total number of cleared tickets exceeds a specified 
    number.16,000
    When a single ticket contains more than a specified number of 
    associated events.150
    Saving raw traps 
    and syslogsWhether raw traps and syslogs received from devices are saved to 
    the Oracle database. It can also store information from unmanaged 
    devices if notification from unmanaged devices is enabled.Enabled 
    						
    							  
    6-3
    Cisco Prime Network 4.3.2 User Guide
    Chapter 6      Setting Up Fault Management and the Events Client Default Settings
      Making Sure Devices Are Configured Correctly
    For more information on how Prime Network responds to incoming events, see How Prime Network 
    Handles Incoming Events, page 10-1.
    Users with Administrator privileges can change these settings by following the directions in the Cisco 
    Prime Network 4.3.2 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 4.3.2 
    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, page 8-27
    Changing Device Port Properties and Disabling Ports, page 8-28
    Changing Device Interface Properties and Disabling Interfaces, page 8-29
    Changing Server Settings for DNS, NTP, RADIUS, and TACACs, page 8-30
    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.Vi ew i n g  
    standard eventsWhether standard events can be viewed in the clients. Standard 
    events are events for which Prime Network only does very basic 
    parsing; they are not examined for correlation or used as a basis for 
    generating tickets. If enabled, these events are displayed in:
    Vision client—Latest Events tab (map view)
    Events client—Standard tab
    NoteFor large deployments, enabling this is not recommended 
    so that Prime Network performance is not negatively 
    impacted.Disabled
    Purging data 
    from Oracle 
    databaseWhen data is purged from the Oracle database:
    Actionable events begin aging when they are archived (moved 
    to an archive partition in the Oracle database).
    Generic (non-actionable) events begin aging as soon as they 
    are saved.14 days Options Description Default Setting 
    						
    							  
    6-4
    Cisco Prime Network 4.3.2 User Guide
    Chapter 6      Setting Up Fault Management and the Events Client Default Settings
      Setting Up Your Events View
    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 4.3.2 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. Ta b l e 6 - 1 lists the available 
    options.If You Are Using 
    Prime Network:Launch the Events client by choosing:
    As part of suiteAssure > Prime Network > Events from the REPLACE main menu bar
    As a standalone 
    applicationStart > Programs > Cisco Prime Network > gateway-IP-address> 
    Cisco Prime Network Events from your local machine
    Table 6-1 Options for Changing Events client Client
    Option Description Default
    Save  last  filter Saves a filter and its criteria so it is available the next time you log into 
    Events. Events are not filtered automatically when you next log into 
    Events client unless the Open Events with saved filter option is also 
    selected.Enabled
    Open 
    Prime Network 
    Events with 
    saved filterWhen enabled, applies the previous filter to the events as soon as you 
    log into Events. While this option is enabled, a filter remains on until 
    you manually disable it.Disabled
    Display n records 
    per pageSpecifies the number of events to be displayed per page. 50
    Export n records 
    in totalSets the maximum number of events to be exported to a file. 1000
    Run auto refresh 
    every n secsAutomatically refreshes the Events client display after the specified 
    number of seconds. 
    NoteThis option uses rapid refresh from the database, which can 
    affect the performance of other vital database options.60 
    						
    							  
    6-5
    Cisco Prime Network 4.3.2 User Guide
    Chapter 6      Setting Up Fault Management and the Events Client Default Settings
      Creating Ticket and Event Filters for Vision and Events Client Users
    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.Display data for 
    the last n hoursDisplays past events for the number of hours specified here. For 
    example, if you specify 4 in this field, then events received over the 
    past 4 hours are displayed in the Events client. The default value is 
    two hours, but you can specify up to 10 hours. The higher the value, 
    the longer it takes for the events to be displayed.2
    Find mode (No 
    automatic data 
    retrieval)Operates the Events client window in Find mode. In this mode, no 
    events will be retrieved from the Oracle database when you open the 
    application or switch between tabs. You can click the Find button in 
    the toolbar to search for the events you need.
    When in Find mode, the status bar in the Events client window shows 
    “Find Mode (no automatic data retrieval).”Disabled
    Table 6-1 Options for Changing Events client Client (continued)
    Option Description Default
    Client To create a filter that uses this criteria: See:
    Vision 
    clientAll devices in a map:
    Tickets
    Incoming syslogs and traps
    Service events generated by Prime NetworkViewing Tickets and 
    Latest Events for All 
    Devices in a Map, 
    page 11-3
    A specific device:
    Tickets
    Incoming syslogs and traps (including events not handled 
    by Prime Network, if enabled)
    Service events generated by Prime Network
    Configuration changes Viewing Tickets and 
    Events for a Specific 
    Device, page 11-4 
    						
    							  
    6-6
    Cisco Prime Network 4.3.2 User Guide
    Chapter 6      Setting Up Fault Management and the Events Client Default Settings
      Creating Ticket and Event Filters for Vision and Events Client Users
    Viewing Investigation Ticket Information
    Prerequisite
    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
    Events 
    clientAll devices managed by Prime Network:
    Active and archived Tickets
    Active and archived Trap, Syslog, and Service events
    Active and archived Trap and Syslog events (standard 
    events) not handled by Prime Network (if enabled)
    Device configuration changes (including who made the 
    changes)Creating and Saving 
    Filters for Tickets and 
    Events, page 12-6
    Trap events and Syslog events from unmanaged devices (if 
    enabled)
    Prime Network internal system and security events Client To create a filter that uses this criteria: See: 
    						
    All Cisco manuals Comments (0)