Use this Knowledge Script to monitor the physical connection between network interface adapters and the network. If the cable for a network interface card is disconnected from the network, AppManager raises an event.
If the computer where you run this Knowledge Script has only one network interface card and that interface card is unplugged, the event cannot be relayed to the AppManager repository until the network interface card is back in service. Therefore, you should only run this script on computers that have more than one network interface card.
On Solaris computers, the UNIX agent must run as root or as a user with root-level authority to retrieve counters associated with the UX Networking performance object. Before running this Knowledge Script, configure the UNIX agent to run as root or as a user that has been given root‑level authority using the sudo configuration file.
Network Interface icon on Solaris computers (not supported on Linux, HP-UX, or AIX).
The default interval for this script is Asynchronous. Once you start the Knowledge Script job, its runs continuously on the monitored system and reports events or data as they occur.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Raise event if network interface card is disconnected? (y/n) |
Set to y to raise an event if the cable for a network interface card is unplugged. The default is y. |
|
Event severity when network interface card has lost connectivity |
Set the event notification level, from 1 to 40, to indicate the importance of the event. The default severity level is 8. |
If you run this Knowledge Script on a computer with multiple network interface cards and at least one of them is available and allows the NetIQ UNIX agent to communicate with the management server, an event is raised if any of the network interface cards is disconnected from the network.
NOTE:This Knowledge Script does not alert you if all network interfaces are disconnected until after network communication is restored. The Knowledge Script job still raises the event, but stores the event in the UNIX agent’s local repository until communication with the management server resumes.