3.22 Interface_Health

Use this Knowledge Script to monitor the parent resource for the interfaces on a network device. This script raises an event if the interface status changes or if any value exceeds a specified threshold. This script generates datastreams indicating the number of “up” interfaces and the total number of interfaces.

NOTE:Interface_Health differs from SingleInterface_Health in that it lets you monitor all interfaces for all devices of any parent resource. SingleInterface_Health allows you to monitor selected interfaces for only one device.

3.22.1 Troubleshooting Events

The table below identifies possible causes and corrective actions for events that are raised when an interface’s status changes. These events can lead to unacceptable service levels for an interface that remains down.

Narrow the usage problem to ports that have excessively high or low usage. If necessary, redistribute network traffic by segmenting your LAN with a bridge, router, or switch.

Determine usage levels on your current network. Try to locate the segments that are experiencing high or low usage levels, which are an indicator of the usage on the chassis.

Possible Cause	Corrective Action
No cable connected	Reconnect the cable on the switch to a known good device.
Wrong port	Ensure both ends of the cable are plugged into the correct ports.
Device has no power	Ensure both devices are powered on and connected to a power source.
Wrong cable type	Verify your cable selection.
Bad cable	Swap the suspect cable with a known good cable. Look for broken or missing pins on the connector.
Loose connections	Unplug a cable and reinsert it. A cable may not be as fully seated in a jack as it appears.
Patch panels	Eliminate faulty patch panel connections. If possible, bypass the patch panel to rule it out as a possible cause.
Media convertors	Eliminate faulty media convertors, such as fiber-to-copper. If possible, bypass the media convertor to rule it out as a possible cause.
Bad or wrong gigabit	Swap the suspect GBOC with a known good GBIC.
Interface convertor (GBIC)	Verify hardware and software support for this type of GBIC.
Bad port or module	Move the cable to a known good port to troubleshoot a suspect port or module.
Port, interface, or module not enabled	Use the show port command for CatOS or the show interface command for Cisco IOS to look for errdisable, disable, or shutdown status. Use the show module command to look for faulty status, which could indicate a hardware problem.

3.22.2 Resource Object

NetworkDevice Interface Folder

3.22.3 Default Schedule

By default, this script runs every 5 minutes.

3.22.4 Setting Parameter Values

Set the following parameters as needed.

Parameter	How to Set It
General Settings
Job Failure Notification
Event severity when job fails	Set the event severity level, from 1 to 40, to indicate the importance of the failure of the Interface_Health job. The default is 5.
Event severity when job returns warnings	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the job completes with warnings. The default is 25.
Event severity when monitoring fails	Set the event severity level, from 1 to 40, to indicate the importance of an event that is raised when monitoring fails. The default is 25.
SNMP Settings
SNMP timeout	Specify the length of time in milliseconds that the job should wait for the SNMP response from the monitored network device before timing out and raising a failure event. The default is 2000 milliseconds.
SNMP retries	Specify the number of times the job should attempt to get the SNMP response from the monitored network device. The default is 1 attempt.
Filter details
Interface name filter	Using regular expression, provide the name of the interface for the devices you want to monitor or the devices you do not want to monitor. Examples To monitor all interfaces, leave this parameter blank and select Include or Exclude in Include or exclude interface name filter. To monitor all interfaces, enter "" and select Include in Include or exclude interface name filter. To monitor nothing, enter "" and select Exclude in Include or exclude interface name filter. To monitor only ethernet interfaces, enter (?=Ethernet) and select Include in Include or exclude interface name filter. To monitor all interfaces EXCEPT ethernet interfaces, enter (?=Ethernet) and select Exclude in Include or exclude interface name filter.
Include or exclude interface name filter	Select Include to monitor only the devices for the interfaces you specified in Interface name filter. Select Exclude to monitor all devices except for those associated with the interfaces you specified in Interface name filter.
Collect data for operational interfaces and total interfaces?	Select Yes to collect data about the number of interfaces that are operational and the total number of interfaces for use in charts and reports. The default is No.
Event severity when interface goes down	Set the severity level, between 1 and 40, to indicate the importance of an event in which the interface’s operational status changes from Up to Down. Enter 0 if you do not want to raise an event. The default is 5. By default, this script raises one event only when the operational status changes to Down. If you want to raise an event every time the Knowledge Script runs to indicate that the interface is still down, use the Raise the “Interface down” event on every job iteration parameter.
Event severity when interface comes up	Set the severity level, between 1 and 40, to indicate the importance of an event in which the interface’s operational status changes from Down to Up. Enter 0 if you do not want to raise an event. The default is 25.
Event severity when interface goes administratively down	Set the severity level, between 1 and 40, to indicate the importance of an event in which the interface’s administrative status changes from Up to Down. The default is 15. By default, this script raises one event only when the administrative status changes to Down. If you want to raise an event every time the Knowledge Script runs to indicate that the interface is still down, use the Raise the “Interface down” event on every job iteration parameter.
Event severity when interface comes administratively and operationally back up	Set the severity level, between 1 and 40, to indicate the importance of an event in which the interface’s administrative and operational statuses change from Down to Up. The default is 30.
Raise the “Interface down” event on every job iteration	Select Yes to raise an event for each job iteration in which an interface’s operational or administrative status is Down. To raise one event only when the status changes from Up to Down, set this parameter to No. The default is No.
Ignore the administratively down interfaces	Select Yes to prevent AppManager from raising an event when an interface is down for administrative purposes. Accept the default of No if you want AppManager to raise an event when an interface is down for administrative purposes.
Raise one-time events?	Select Yes to raise an event for all one-time events. For example, if you set this parameter to Yes, then, on the first iteration of this script, AppManager raises an event when a particular performance counter cannot be found. If you do not want to see such one-time events, set this parameter to No.