Use the Discovery_NetworkDevice Knowledge Script to discover network resources, such as routers, switches, and gateways, using SNMP GET commands over proxy architecture. Upon successful discovery, the following devices can be monitored:
Chassis resources: CPU, memory, Flash memory, backplane, power supplies, fans, temperature sensors, and voltage sensors
IP subsystem
Interfaces: IP address and queue
Host Resource
WAN links, serial links, frame relay links, and ATM links
The Discovery_NetworkDevice script also tracks, displays, and provides various alerts about AppManager for Network Devices services.
The Discovery job also discovers NetIQ SNMP Trap Receiver resources. For more information, see Section 3.44.4, Working with NetIQ SNMP Trap Receiver.
Only one computer should act as a proxy for any given network device. Therefore, run the Discovery_NetworkDevice Knowledge Script on only one Microsoft Windows server at a time.
Ensure that all devices you want to discover have unique names. AppManager cannot differentiate between two IP addresses that have the same value for the sysName object, which is a name for a managed node assigned by an administrator, usually the hostname. When two devices have the same sysName object, AppManager assumes the two devices are the same single device. The list of devices you can monitor will be inaccurate if you do not assign unique names to your devices.
Configure AppManager Security Manager with the community string and version information for each device you want to discover. For more information, see Section 2.6, Configuring SNMP Permissions.
If you delete or add a resource object, or if you make any other kind of change that might affect the monitoring of your resources, run the Discovery_NetworkDevice Knowledge Script again to update your list of resource objects. In addition, if you are running this module on AppManager 8 or later, you can use the delta discovery feature in Control Center to run discovery on a schedule to more quickly detect changes to your environment.
Set the Values tab parameters as necessary:
|
Parameter |
How to Set It |
|---|---|
|
Auto Discovery |
|
|
Default gateway router |
Specify the IP network address of the gateway (router) to query during discovery. Note Use this parameter if you are uncertain of all the relevant subnets that should be scanned during discovery. If you enter an IP address here, AppManager queries the gateway for its routing tables and then attempts to discover every device in the tables. |
|
Maximum number of hops |
Specify the maximum number of hops that you want discovery to make during auto-discovery. The default is 1 hop. Discovery considers the gateway router itself to be the first hop. Therefore, a Maximum number of hops setting of 1 means you discover only the networks directly connected to the gateway router, and no other routers. |
|
Walk subnets for layer-2 devices? |
Set to n to discover all routers (Layer-3 devices) and all Cisco switches (Layer-2 devices), within the number of Maximum number of hops you have set, by means of routing tables and Cisco Discovery Protocol (CDP). Set to y to also discover all non-Cisco switches and other network devices, within the number of Maximum number of hops you have set, by means of a range discovery on all discovered subnets. Caution Set this parameter to y only with the understanding that walking the subnets for Layer-2 devices is a time- and resource-intensive undertaking that can have a negative impact on network performance. The default is n. |
|
List of network devices |
Provide a list of the network devices you want to discover. You must specify at least one network device. Use a comma to separate the names in the list. For example: raldbellijm02,raldattixlm You can enter hostnames, if you use DNS in your environment, or IP addresses. NOTE:Before running this script, configure the SNMP permissions for each device that you list in this field into Security Manager. For more information, see Section 2.6, Configuring SNMP Permissions. |
|
List of network device ranges |
Provide a list of IP address ranges for the network devices you want to discover. Spaces are invalid in the list. Only numbers, dashes, and commas are allowed. For example: 1.2.3.4-5.6.7.8,10.9.8.7-10.10.10.10 Note Limit the number of IP addresses in each range to no more than 256. To scan more than 256 IP addresses, break a range into multiple ranges, each with no more than 256 IP addresses. |
|
Full path to file with list of network devices |
Instead of identifying each network device separately, you can specify the full path to a file on the agent computer that contains a device name on each line of the file. The file must be located on the computer on which you run the Discovery script. NOTE:Before running this script, configure the SNMP permissions for each device that you list in this field into Security Manager. For more information, see Section 2.6, Configuring SNMP Permissions. |
|
Discover IP addresses that belong to the same device? |
Set to y to discover all IP addresses for a single device. The same device will appear in the TreeView once for each different associated IP address. Set to n to discover a device only once, regardless of the number of associated IP addresses. Note that the number of discovered devices directly affects the number of licenses required for the AppManager for Network Devices module. The default is n. |
|
Discovery Details |
|
|
Discover individual … … interfaces? … LAN links? … WAN links? … frame relay links? … ATM links? … FXS ports? … FXO ports? … ISDN channels? |
This script automatically discovers interfaces, links, and ports when these parameters are set to y. The default is y. Note Set these parameters to n for any device you do not want to monitor. By not discovering these resources, you will significantly speed the discovery process and improve the performance of the TreeView. |
|
Trap Receiver Discovery |
|
|
Discover Trap Receiver? |
Set to y to discover NetIQ SNMP Trap Receiver. The default is y. |
|
Trap Receiver IP address |
Specify the IP address of the computer on which Trap Receiver is installed. The default is localhost. |
|
Trap Receiver TCP port |
Specify the TCP port number through which Trap Receiver will communicate with AppManager. The default is port 2735. |
|
Discovery timeout |
Specify the number of minutes that the script should attempt discovery before stopping as unsuccessful. The default is 10 minutes. The maximum is 60 minutes. |
|
Raise event when discovery succeeds? |
This script always raises an event when discovery fails for any reason. In addition, you can set this parameter to y to raise an event when discovery succeeds. The default is n. |
|
Event severity when discovery succeeds |
Set the event severity level, from 1 to 40, to reflect the importance of an event in which discovery succeeds. The default is 25. |
|
Event severity when discovery fails |
Set the event severity level, from 1 to 40, to reflect the importance of an event in which discovery fails. The default is 5. |