Integración de la tecnología de Red CISCO-ROUTER

ServicePilot network-cisco-router

# Cisco Router


This package is designed to monitor a Cisco Router using SNMP. Statistics are collected for a single device , in order to provide an overall view of the status and health of the different system and board components of the device.


This package automatically configures the ServicePilot Manager to collect statistics from the Cisco Router on which SNMP Service has been configured. The statistics gathered in this way include:

  • CPU
  • Memory and Buffer creation failure
  • Interfaces (will be automatically discovered)
  • Fans (will be automatically discovered)
  • Temperature sensors and Power Supplies (will be automatically discovered)


  • SNMP service must be configured and started on the targeted Cisco Router (Security: read-only SNMP community and allowed host must be set).

  • Network Flows - It is necessary to ensure network connectivity between ServicePilot and the monitored device. In case of a network infrastructure with a firewall, all of the following flows must be opened:

    • UDP/161 (SNMP): Between ServicePilot Manager and Cisco Router
    • ICMP/Echo Request (Ping): Between ServicePilot Manager and Cisco Router
    • UDP/162 (SNMP Trap): (Optional) Between Cisco Router and ServicePilot Agent
  • ServicePilot Requirements

    • ServicePilot Manager minimum version: 8.5


Before adding a resource to monitor, make certain that all pre-requisites are in place and if a ServicePilot Agent is required, that it is communicating correctly with the ServicePilot Manager.

Add resource using Views Configuration web interface

  1. As an administrative user of ServicePilot, open the ServicePilot web interface.
  2. Navigate to Administration. The Configuration > Views web page will open.
  3. Click on the view in which to place the new resource in the Views hierarchy on the left of the interface. The View editor section will show the existing view contents.
  4. From the Packages list on the right of the interface, click and drag the network-cisco-router package into the View editor and let go.
  5. The Resource properties dialog box will open to allow resource configuration.
  6. Click OK to close the Resource properties dialog box. Note that the dialog box will not close if required parameters are not set.
  7. Click Save to apply the new resource to ServicePilot configuration.


Object TypeLicense object ConsumedCondition
System Information1If System enabled
Ping1If ICMP Ping enabled
Temperature1If Temperature enabled
Fans1If Fans enabled
Power Supplies1If Power Supplies enabled
OSPF1 per OSPF table entryIf OSPF enabled
BGP Peers1 per BGP Peers table entryIf BGP enabled
Virtual Routing and Forwarding1 per VRF table entryIf VRF enabled
Network Interfaces1 per interface monitoredIf Auto-Discover Interfaces enabled and interfaces selected

Key field notes

In the Monitoring Policies tab, specify the policy or policies to apply to the resource

  1. Basic Parameters tab:

    1. IP address: Specify the IP address of the Cisco Router, as resolvable by the machine on which ServicePilot Manager is running
  2. Interfaces tab:

    1. Interfaces: tick to get details about interfaces.
    2. Use Interface filter instead of Addressing Information: Set it on to get statistics for a specified list on interfaces only. Set it off to get statistics for all available interfaces.
    3. {Optional} Ignored Interfaces names separated with '|': Specify name(s) of interface(s) NOT to be monitored
    4. {Optional} Allowed Interfaces names separated with '|': Specify name(s) of interface(s) to be monitored
    5. {Optional} Custom interface speed separated with '|': Specify maximum speed of interface
  3. Monitoring Options tab:

    1. ICMP Ping: tick to get Ping status.
    2. Fans: tick to get statistics for all fans.
    3. Power Supplies: tick to get statistics for all power supplies.
    4. Temperature Sensors: tick to get statistics for all temperature sensors.
    5. System: tick to get system statistics.
  4. Routing Protocols tab:

    1. OSPF: tick to dicover and monitor OSPF
    2. BGP: tick to dicover and monitor BGP Peers
    3. VRF: tick to monitor Virtual Routing and Forwarding role

Note: Each element of the ignored/allowed interface lists is a regular expression as defined by Like Operator (Visual Basic)


MIBs Used:

  • RFC1213-MIB2


Cómo podemos ayudarle ?

O llámenos a +33 2 40 60 13 30