The default version of the SL1 includes several vendor-specific PowerPacks that enable you to discover and monitor routers, switches, and firewalls from those vendors. It also includes a Generic Switch/Router MIB Support PowerPack that can collect additional data from your network devices.
The following sections describe the Dynamic Applications that are included in these PowerPacks:
PowerPack: Generic Switch/Router MIB Support
If the SL1 does not include vendor-specific Dynamic Applications for your routers and switches, you can use the following Dynamic Applications to collect additional data from your routers and switches.
CAUTION: Some of the Dynamic Applications in this section are not automatically aligned to devices. You must manually align these Dynamic Applications to devices. Do not align these Dynamic Applications to device that include more than 200 indexes (either more than 200 peers or more than 200 interfaces, depending on the Dynamic Application. Doing so will significantly slow the performance of your SL1 system. For details on manually aligning a Dynamic Application with a device, see the
| Dynamic Application | Required MIB | Collected Data Points | Frequency | Applied Automatically During Discovery? |
|---|---|---|---|---|
| BGP Peer Statistics | BGP4-MIB | Number of inbound updates | 5 Minutes |
Yes This Dynamic Application can collect and report data for up to 200 peers by default. The Dynamic Application will not collect and report data for peers beyond the threshold. If the threshold is exceeded, a device log entry will be generated. To change the threshold from the default, go to the Device Thresholds page (Registry > Devices > Device Manager > wrench icon > Thresholds), update the Maximum BGP Peer Statistics value, and then click . |
| Number of outbound updates | ||||
| Total inbound messages | ||||
| Total outbound messages | ||||
| FSM Transitions | ||||
| BGP Peers | BGP4-MIB | Remote IP Address | 5 minutes |
Yes |
| Remote Port | ||||
| Remote AS | ||||
| Local Port | ||||
| Local IP Address | ||||
| Peer State | ||||
| Peer Admin Status | ||||
| BGP Peer Version | ||||
| BGP Last Error | ||||
| FSM Established Time | ||||
| Alerts will be generated when the Peer state is not established and the admin state is "start" | ||||
| Interface Extended Statistics | IF-MIB | Multicast Packets In | 15 minutes |
No This Dynamic Application must be manually aligned to each device. CAUTION: Do not align this Dynamic Application to devices that include more than 200 interfaces. Doing so will significantly slow performance of your SL1 system. |
| Multicast Packets Out | ||||
| Unicast Packets In | ||||
| Unicast Packets Out | ||||
| Broadcast Packets In | ||||
| Broadcast Packets Out | ||||
| The ifName is used as the label | ||||
| OSPF Neighbors Configuration | OSPF-MIB | Neighbor IP | 5 minutes | Yes |
| Neighbor Priority | ||||
| Neighbor Router ID | ||||
| Neighbor State | ||||
| Neighbor State Changes | ||||
| Retx Q Len | ||||
| Alerts will be generated when the Neighbor State is not 'full'. | ||||
| OSPF Type | ||||
| Designated Router | ||||
| Backup Designated Router |
PowerPack: Cisco: Base Pack
If your network includes Cisco devices, you can use the following Dynamic Applications to collect additional data from your routers and switches.
CAUTION: Some of the Dynamic Applications in this section are not automatically aligned to devices. You must manually align these Dynamic Applications to devices. Do not align these Dynamic Applications to device that include more than 200 indexes (either more than 200 peers or more than 200 interfaces, depending on the Dynamic Application. Doing so will significantly slow the performance of your SL1 system. For details on manually aligning a Dynamic Application with a device, see the
| Dynamic Application | Required MIB | Collected Data Points | Frequency | Applied Automatically During Discovery? |
|---|---|---|---|---|
| Cisco: BGP Peer Stats | CISCO-BGP4-MIB | Number of time the BGP FSM transitioned | 5 minutes |
Yes This Dynamic Application includes a threshold that limits the collection to a default of 200 BGP Peers to keep from slowing the performance of your SL1 system. |
| Label for the peer | ||||
| Number of accepted route prefixes | ||||
| Number of route prefixes that have been advertised | ||||
| Number of route prefixes that have been denied | ||||
| Number of route prefixes that have been suppressed | ||||
| Number of route prefixes that have been withdrawn | ||||
| Number of messages received | ||||
| Number of messages sent | ||||
| Number of BGP updates received | ||||
| Number of BGP updates sent | ||||
| Cisco: BGP Peers | CISCO-BGP4-MIB | Most recent error code and subcode | 5 minutes |
Yes This Dynamic Application includes a threshold that limits the collection to a default of 200 BGP Peers to keep from slowing the performance of your SL1 system. |
| Label for peer | ||||
| Version of BGP running between two peers | ||||
| Amount of time peer has been in established state | ||||
| BGP identifiers | ||||
| Local IP address | ||||
| Local port | ||||
| Administrative status of peer | ||||
| Status of peer | ||||
| Remote autonomous system number | ||||
| Remote IP address | ||||
| Remote port | ||||
| Cisco: CPU |
CISCO-PROCESS_MIB, CISCO-SYSTEM-EXT-MIB, or OLD-CISCO-CPU-MIB |
CPU busy percentage in the last five minutes | 5 minutes | Yes |
| Label for the CPU | ||||
| Cisco: Environmental Entity Status | CISCO-ENTITY-SENSOR-MIB | Description of the fan | 15 minutes |
Yes
|
| State of the fan | ||||
| Label for the fan | ||||
| Index for the fan | ||||
| Description of the power supply | ||||
| State of the power supply | ||||
| Label for the power supply | ||||
| Index for the power Supply | ||||
| Description of temperature test point | ||||
| Status of temperature test point | ||||
| Label for temperature test point | ||||
| Index for temperature test point | ||||
| Cisco: Environmental Status | CISCO-ENVMON-MIB | Description of the fan | 30 minutes | Yes |
| State of the fan | ||||
| Label for the fan | ||||
| Label for the power supply | ||||
| Description of the power supply | ||||
| State of the power supply | ||||
| Description of temperature test point | ||||
| Status of temperature test point | ||||
| Label for temperature test point | ||||
| Cisco: Fan Configuration | CISCO-ENVMON-MIB | Description of the fan | 30 minutes | Yes |
| State of the fan | ||||
| Status configuration of the fan | ||||
| Percentage of fans in a Critical or Shutdown state | ||||
| Cisco: FCoE Configuration | CISCO-FCOE-MIB | Ethernet interface name | 15 minutes | Yes |
| FCoE information | ||||
| Ethernet interface admin status | ||||
| VFC bind MAC address | ||||
| Ethernet interface operational status | ||||
| VFC bind type | ||||
| VFC name | ||||
| VFC failure cause | ||||
| VFC admin status | ||||
| VFC FCF priority | ||||
| VFC operational state | ||||
| VCF interface index | ||||
| Ethernet interface index | ||||
| Cisco: Feature Set Configuration | CISCO-FEATURE-CONTROL-MIB | Feature name | 1 hour | Yes |
| Feature information | ||||
| Current operating status | ||||
| Reason for current operating status | ||||
| Last action triggered | ||||
| Last action result | ||||
| Reason for last action failure | ||||
| Cisco: FEX Configuration | CISCO-ETHERNET-FABRIC-EXTENDER-MIB | Extender name | 15 minutes | Yes |
| Fabric port name | ||||
| Creation time | ||||
| Identify serial number string | ||||
| Pinning max links | ||||
| Fabric port admin status | ||||
| Pinning mode | ||||
| Fabric port interface index | ||||
| Row status | ||||
| Fabric port operational status | ||||
| Enable serial number check | ||||
| FEX information | ||||
| Cisco Ethernet Fabric Extender Binding Extender Index | ||||
| Cisco: Fibre Channel Configuration | CISCO-FC-FE-MIB | Interface name | 1 hour | Yes |
| Current port operating FEC state | ||||
| Administrative FEC state | ||||
| Current interface operating state | ||||
| Administrative port mode | ||||
| Current port operating status cause | ||||
| Administrative port speed | ||||
| Current port operating status cause description | ||||
| Administrative trunking mode | ||||
| Current port trunking mode | ||||
| BB_Credit model | ||||
| Port channel name | ||||
| Beacon mode | ||||
| Interface service state | ||||
| Port connector module type | ||||
| Port World-Wide name | ||||
| Interface label | ||||
| Cisco: Fibre Channel Performance | CISCO-FC-FE-MIB | 8b10b disparity errors | 5 minutes | Yes |
| Framing errors | ||||
| Address ID errors | ||||
| b2b credit transition to zero | ||||
| b2b credit transition from zero | ||||
| Interface name | ||||
| Class 2 frames discarded | ||||
| Invalid CRCs | ||||
| Class 2 frames received | ||||
| Invalid transmission words | ||||
| Class 2 frames sent | ||||
| Frames received that were too long and had a CRC error | ||||
| Class 2 frame octets received | ||||
| Link failures | ||||
| Class 2 frame octets sent | ||||
| Link reset protocol errors received | ||||
| Class 3 frames received | ||||
| link reset protocol errors sent | ||||
| Class 3 frames sent | ||||
| F8 LIP errors received | ||||
| Class 3 frame octets received | ||||
| F8 LIP errors sent | ||||
| Class 3 frame octets sent | ||||
| Link reset responses received | ||||
| Cisco: Fibre Channel Performance (continued) | Class F frames received | |||
| Link reset responses sent | ||||
| Class F frames sent | ||||
| Non-F8 LIP errors received | ||||
| Class F frame octets received | ||||
| Non-F8 LIP errors sent | ||||
| Class F frame octets sent | ||||
| Non-operational sequences received | ||||
| Link resets due to unavailable credits | ||||
| Non-operational sequences sent | ||||
| Delimiter errors | ||||
| Offline sequence errors received | ||||
| Egress packets discarded | ||||
| Offline sequence errors sent | ||||
| EISL frames discarded | ||||
| Primitive sequence protocol errors | ||||
| ELP failures | ||||
| Frames received that were too short, regardless of CRC status | ||||
| Frames with EOF aborts | ||||
| Signal losses | ||||
| Blocks corrected by FEC decoder | ||||
| Cisco: Fibre Channel Performance (continued) | Fragmented frames received | |||
| Loss of synchronization failures | ||||
| Blocks not corrected by FEC decoder | ||||
| Packets dropped due to timeouts | ||||
| Wait times due to lack of transmission credits | ||||
| Frames discarded | ||||
| Credit transitions to zero for 100 ms | ||||
| Frames received that were too long | ||||
| Unknown class frames | ||||
| Frames received that were too short | ||||
| Cisco: FRU Control Configuration | CISCO-ENTITY-FRU-CONTROL-MIB | Status of the FRU | 5 minutes | Yes |
| Name of module | ||||
| Administrative status of the FRU | ||||
| Name of FRU | ||||
| Amount of current drawn for inline operation | ||||
| Name of fan | ||||
| Amount of current drawn for system operation | ||||
| Operational status of module | ||||
| Fan label | ||||
| Operational status of FRU | ||||
| Current supplied by the FRU | ||||
| Operational status of fan | ||||
| Model name of FRU | ||||
| Power label | ||||
| Model name of fan | ||||
| Total current available from FRU for inline operation | ||||
| Module label | ||||
| Total current available from FRU for system operation | ||||
| Cause of last module state change | ||||
| sysUpTime value | ||||
| Cisco: Interface Errors Performance | CISCO-IF-EXTENSION-MIB | Number of times carrier signal transitioned | 15 minutes |
No This Dynamic Application must be manually aligned to each device. CAUTION: Do not align this Dynamic Application to devices that include more than 200 interfaces. Doing so will significantly slow performance of your SL1 system. |
| Number of framing errors per interface | ||||
| Number of packets dropped due to large size | ||||
| Interface label | ||||
| Number of times interface was reset | ||||
| Number of input packets dropped | ||||
| Number of output packets dropped | ||||
| Number of packets dropped due to small size | ||||
| Cisco: IPSEC Global Ph1 Performance | CISCO-IPSEC-FLOW-MONITOR-MIB | Number of currently active IPsec Phase-1 IKE tunnels | 5 minutes | Yes |
| Number of previously active IPsec Phase-1 IKE tunnels | ||||
| Number of IPsec Phase-1 IKE tunnels which were locally initiated | ||||
| Number of IPsec Phase-1 IKE tunnels that were locally initiated and failed to activate | ||||
| Number of IPsec Phase-1 IKE tunnels that were remotely initiated and failed to activate | ||||
| Number of authentications that ended in failure | ||||
| Number of decryptions that ended in failure | ||||
| Cisco: IPSEC Global Ph1 Performance (continued) | Number of hash validations that ended in failure | |||
| Number of packets received | ||||
| Number of packets dropped during receive processing | ||||
| Number of packets sent | ||||
| Number of packets dropped during send processing | ||||
| Number of notifications received | ||||
| Number of notifications sent | ||||
| Number of octets received | ||||
| Number of octets sent | ||||
| Number of IPsec Phase-2 exchanges received | ||||
| Number of IPsec Phase-2 exchanges received and rejected | ||||
| Number of IPsec Phase-2 exchanges received and found to be invalid | ||||
| Number of IPsec Phase-2 exchanges sent | ||||
| Number of IPsec Phase-2 exchanges sent and rejected | ||||
| Number of IPsec Phase-2 exchanges sent and found to be invalid | ||||
| Number of IPsec Phase-2 security association delete requests | ||||
| Cisco: IPSEC Global Ph1 Performance (continued) | Number of non-existent security association inbound failures that occurred during processing | |||
| Number of system capacity failures that occurred during processing | ||||
| Cisco: Old Interface Details | OLD-CISCO-INTERFACES MIB | Count for ARP protocol input, in octets | 15 minutes |
No This Dynamic Application must be manually aligned to each device. CAUTION: Do not align this Dynamic Application to devices that include more than 200 interfaces. Doing so will significantly slow performance of your SL1 system. |
| Count for ARP protocol output, in octets | ||||
| Count for ARP protocol input, in packets | ||||
| Count for ARP protocol output, in packets | ||||
| Number of times carrier signal transitioned | ||||
| Number of packets with cyclic redundancy checksum errors | ||||
| Number of packets dropped due to large size | ||||
| Interface label | ||||
| Number of times interface was reset | ||||
| Number of input packets dropped | ||||
| Number of output packets dropped | ||||
| Number of packets dropped due to small size | ||||
| Cisco: Physical Memory |
CISCO-ENHANCE_MEMPOOL- MIB or CISCO-MEMORY-POOL-MIB |
Unused I/O memory, in bytes | 5 minutes | Yes |
| Used I/O memory, in bytes | ||||
| I/O memory accuracy | ||||
| Memory label | ||||
| Unused processor memory, in bytes | ||||
| Used processor memory, in bytes | ||||
| Processor memory accuracy | ||||
| Sum of all unused memory, in bytes | ||||
| Sum of all used memory, in bytes | ||||
| Cisco: Port Channel Configuration | CISCO-PORT-CHANNEL-MIB | Interface name | 15 minutes | Yes |
| Last action status | ||||
| Admin channel mode | ||||
| Last action time | ||||
| Channel add compatibility check | ||||
| Member port | ||||
| Channel creation time | ||||
| Forwarding status of member port | ||||
| Interface index | ||||
| Port operating channel mode | ||||
| Index | ||||
| Port channel information and channel member list | ||||
| Last action cause | ||||
| Row status | ||||
| Cisco: Swap | CISCO-MEMORY-POOL MIB | Unused swap, in bytes | 15 minutes |
No This Dynamic Application must be manually aligned to each device. CAUTION: Do not align this Dynamic Application to devices that include more than 200 interfaces. Doing so will significantly slow performance of your SL1 system |
| Used swap, in bytes | ||||
| Cisco: Temperature Sensor Performance | CISCO-ENTITY-SENSOR-MIB | Temperature Sensor Index | 5 minutes | Yes |
| Major severity threshold value | ||||
| Temperature sensor name | ||||
| Minor severity threshold value | ||||
| Operational status | ||||
| Most recent value | ||||
| Cisco: VLAN Configuration | CISCO-VTP-MIB | VLAN ID | 24 hours | Yes |
| Number of errors for revision numbers | ||||
| Number of errors for revision numbers | ||||
| Number of advert requests received | ||||
| Number of subset adverts received | ||||
| Number of summary adverts received | ||||
| Maximum number of VLANs after reboot | ||||
| Number of advert requests sent | ||||
| Number of subset adverts sent | ||||
| Number of summary adverts sent | ||||
| MTU size | ||||
| Name of VLAN | ||||
| VLAN type | ||||
| VTP version | ||||
| Cisco: VRF BGP Peers | CISCO-BGP4-MIB | Most recent error code and subcode | 5 minutes |
No This Dynamic Application must be manually aligned to each device. |
| Label for peer | ||||
| Version of BGP running between two peers | ||||
| Amount of time peer has been in established state | ||||
| BGP identifiers | ||||
| Local IP address | ||||
| Local port | ||||
| Administrative status of peer | ||||
| Status of peer | ||||
| Remote autonomous system number | ||||
| Remote identifier | ||||
| Remote IP address | ||||
| Remote port | ||||
| TCP state | ||||
| Cisco: VSAN Configuration | CISCO-VSAN-MIB | VSAN name | 5 minutes | Yes |
| VSAN administrative status | ||||
| VSAN operational status | ||||
| InorderDelivery guarantee flag | ||||
| Interoperability | ||||
| Load balancing type | ||||
| Network media type | ||||
| Interface name | ||||
| Number of subset adverts sent | ||||
| Number of summary adverts sent | ||||
| MTU size | ||||
| VSAN ID | ||||
| VSAN index label | ||||
| VSAN interface ifIndex | ||||
| Device Software Version | ENTITY-MIB | IOS version | 24 hours | Yes |
PowerPack: Juniper Base Pack
If your network includes Juniper devices, you can use the following Dynamic Applications to collect additional data from your routers and switches.
| Dynamic Application | Required MIB | Collected Data Points | Frequency | Applied Automatically During Discovery? |
|---|---|---|---|---|
| Juniper: Chassis MIB Configuration | JUNIPER-MIB | FRU name | 5 minutes | Yes |
| FRU current state | ||||
| FRU type | ||||
| Box name, model, or description | ||||
| Box revision | ||||
| Box serial number | ||||
| Chassis description | ||||
| Chassis identifier | ||||
| CLEI code | ||||
| Contents description | ||||
| sysUptime during last installation | ||||
| Container's level 1 index | ||||
| Container's level 2 index | ||||
| Container's level 3 index | ||||
| Contents part number | ||||
| Content revision | ||||
| Juniper: Chassis MIB Configuration (continued) | Content serial number | |||
| Content type | ||||
| FRU sysUptime when last powered off | ||||
| FRU sysUptime when last powered on | ||||
| FRU offline reason | ||||
| FRU slot number | ||||
| FRU uptime | ||||
| Operating description | ||||
| Operating level 1 index | ||||
| Operating level 2 index | ||||
| Operating level 3 index | ||||
| Operating state | ||||
| Juniper: Chassis MIB Performance | JUNIPER-MIB | CPU load average | 5 minutes | Yes |
| CPU utilization, in percent | ||||
| FRU power voltage | ||||
| Heap utilization, in percent | ||||
| CPU utilization in interrupt service routine | ||||
| Chassis description | ||||
| Object temperature, in degrees Celsius | ||||
| Juniper: CPU | JUNIPER-MIB | CPU usage, in percent | 5 minutes | Yes |
| Juniper: DOM Performance | JUNIPER-SMI | Module temperature | 5 minute | Yes |
| Receiver laser power | ||||
| Transmitter laser bias current | ||||
| Transmitter laser output power | ||||
| Juniper: FRU MIB Configuration | JUNIPER-SMI | FRU administrative state | 5 minutes | Yes |
| FRU level 1 index | ||||
| FRU level 2 index | ||||
| FRU level 3 index | ||||
| FRU operational state | ||||
| FRU object ID | ||||
| Juniper: Memory | JUNIPER-MIB | Buffer pool utilization, in percent | 5 minutes | Yes |
| Juniper: Process Count | JUNIPER-MIB | Number of processes running | 5 minutes | Yes |
| Juniper: Temperature Stats | JUNIPER-MIB | Object name | 5 minutes | Yes |
| Object temperature, in degrees Celsius | ||||
| Juniper: VPN MIB Configuration | JUNIPER-VPN-MIB | Interface VPN name | 15 minutes | Yes |
| Route Target VPN name | ||||
| Interface VPN type | ||||
| Pseudo-Wire VPN name | ||||
| Route Target VPN type | ||||
| VPN description string | ||||
| Interface status | ||||
| Pseudo-Wire VPN index | ||||
| Pseudo-Wire VPN type | ||||
| Route Target index | ||||
| Route Target type | ||||
| VPN name | ||||
| VPN type | ||||
| Remote PE address | ||||
| Remote PE address type | ||||
| Associated Pseudo-Wire index | ||||
| Maximum bandwidth in, in kilobytes | ||||
| Maximum bandwidth out, in kilobytes | ||||
| VPN interface index | ||||
| VPN interface protocol | ||||
| Juniper: VPN MIB Configuration (continued) | Interface row status | |||
| Interface storage type | ||||
| Next VPN interface index | ||||
| Next Pseudo-Wire index | ||||
| Next Route Target index | ||||
| Number of active sites | ||||
| Number of active VPNs | ||||
| Number of configured sites | ||||
| Number of configured VPNs | ||||
| Number of local addresses | ||||
| Pseudo-Wire associated interface VPN index | ||||
| Pseudo-Wire local site identifier | ||||
| Pseudo-Wire LR octets received | ||||
| Pseudo-Wire LR octets sent | ||||
| Pseudo-Wire LR packets received | ||||
| Pseudo-Wire LR packets sent | ||||
| Pseudo-Wire octets received | ||||
| Pseudo-Wire octets sent | ||||
| Pseudo-Wire packets received | ||||
| Pseudo-Wire packets sent | ||||
| Juniper: VPN MIB Configuration (continued) | Pseudo-Wire received packets demultiplexor | |||
| Pseudo-Wire remote site identifier | ||||
| Pseudo-Wire remote site status | ||||
| Pseudo-Wire row status | ||||
| Pseudo-Wire status | ||||
| Pseudo-Wire storage type | ||||
| Pseudo-Wire uptime | ||||
| Pseudo-Wire state transitions | ||||
| Pseudo-Wire sent packets demultiplexor | ||||
| Pseudo-Wire tunnel name | ||||
| Pseudo-Wire tunnel status | ||||
| Pseudo-Wire tunnel type | ||||
| Route Target | ||||
| Route Target export distribution type | ||||
| Route Target row status | ||||
| Route Target storage type | ||||
| VPN RIB total addresses | ||||
| VPN age | ||||
| VPN identifier | ||||
| VPN row status | ||||
| VPN type identifier |