Task-specific discovery agents

The AlteonSwitch agent retrieves layer 2 connectivity information from Alteon load balancers and Ethernet switch modules.

You must run this agent if you are running a layer 2 discovery. This agent is optional if you are running a layer 3 discovery. However, it can be more efficient to use the ARP Cache discovery agent because in most network environments the ARP helper can only run on one subnet at a time.

• Oracle
• Apache
• Microsoft SQL Server
• Microsoft Exchange
• Microsoft Internet Information Server (IIS)
• Microsoft Active Directory
• IBM® WebSphere®
• BEA WebLogic
• SAP
• Sybase ASE
• IBM Lotus Notes/Domino Server

The ASM agent determines whether an application is running by querying ASM-specific MIBs for the device. These MIBs are installed by default when you install Network Manager.

The ASM agent can only retrieve this information from network devices on which ASM is deployed. Typically, you would deploy a ASM sub-agent on each commercial server and database product which is running on a device and whose performance you wish to monitor.

BGPPeerNextHopInterface

All PE to CE interfaces are added to a members list and an event on any of the interfaces in this members list causes the system to generate a synthetic MPLS VPN SAE.

This agent, which is off by default, enables the generation of MPLS VPN service-affected events (SAEs) based on interfaces dependencies deeper in the core network. This agent calls the AddLayer3VPNInterfaceDependency.stch stitcher.

This stitcher determines all PE to core provider router (P) interfaces and P to PE interfaces involved in a VPN. These PE -> P and P ->PE interfaces are added to a dependency list. An event on any of the interfaces in this dependency list causes the system to generate a synthetic MPLS VPN SAE. If an MPLS VPN SAE has already been generated based on an event on any of the interfaces in the members list, then any events in interfaces in the dependency list will be added as related events to that already generated MPLS VPN SAE.

CiscoNexusVdc

The CiscoVoIPHttp agent is a Perl-based agent that extracts device data and network information about the Cisco VOIP device.

The agent uses a Network Manager-specific Perl module to retrieve the information from the following pages of the device:

• http://IP ADDRESS/CGI/Java/Serviceability?adapter=device.statistics.device
• http://IP ADDRESS/CGI/Java/Serviceability?adapter=device.statistics.configuration

Note: If activated, this agent retrieves a large amount of information. Activating this agent may therefore place a heavy load on memory. You should only activate this agent if specific cable modem information is required beyond that provided by other agents.

Note: If activated, this agent retrieves a large amount of information. Activating this agent may therefore place a heavy load on memory. You should only activate this agent if specific cable modem information is required beyond that provided by other agents.

• sysDescr
• sysLocation
• sysUpTime
• sysServices
• ifNumber

The MACFromArpCache agent is optionally activated in phase 3 of Discovery. It uses the ArpCache information retrieved by the ArpCache agent to retrieve the MAC address of the device. The agent is useful as it does not require SNMP access to the device to obtain the MAC address.

MACFromTDWDatabase

This agent queries the Tivoli Data Warehouse. The agent retrieves the mapping of MAC address to IP address for each server. Run this agent if the connectivity of servers is not represented properly in the network topology due to incomplete mapping of MAC address to IP address of the servers. The IBM Tivoli Monitoring (ITM) Operating System (OS) Agent must be running on the servers in the network for which you want to retrieve information. You must also have access to the Tivoli Data Warehouse database in order to access the information retrieved by the ITM OS agents.

Before running this agent, add the access details for the Tivoli Data Warehouse database to the DbLogins.cfg file. Edit the DbLogins.cfg file and add an insert similar to the following example:

insert into config.dbserver
(
    m_DbId,
    m_Server,
    m_DbName,
    m_Schema,
    m_Hostname,
    m_Username,
    m_Password,
    m_PortNum,
    m_EncryptedPwd,
    m_OracleService
)
values
(
    "TDW",
    "oracle",
    "someDbName",
    "someSchema",
    "serverHostName",
    "username",
    "password",
    port,
    [0|1],
    1
);

NetScreenArpCache

The NetScreenArpCache agent retrieves information from ARP tables configured in Netscreen devices and processes the tables to obtain the IP to MAC translation. The agent then sends the ARP information to the ARP Helper. After further processing, the ARP Helper sends the IP and MAC address mapping to the ARPHelperTable.

The NetScreenArpCache agent uses the SNMPv2-SMI Standard MIB.

NMAPScan

The NMAPScan agent is a Perl agent that runs the NMAP scanner against devices discovered by Network Manager. By default, the agent runs against devices that do not have SNMP access, or devices that have SNMP access but return sysObjectIds of devices from Apple, Compaq, IBM, Microsoft, Sun, Network Harmoni, UC David, Net-SNMP, and HP.

The agent retrieves the following data:

• Operating System Fingerprint details
• TCP/UDP port and application information including port number, name, state, type, and service

You must install NMAP version 4.85 or later on the same server where the Network Manager core components are installed. You must then edit the NMAPScan.pl file and specify the path to the NMAP binary in the my $nmapBinary line, and remove the comment from the beginning of the line. NMAP is available at http://nmap.org.

The following options are set by default for NMAP:

• -sS: Perform a TCP SYN scan
• -sV: Enable service version identification
• -PN: Do not ping each target (Network Manager already uses the ping or file finder, or both)
• -O: Enable Operating System fingerprinting
• -oX: Enable XML output
  Important: Do not change this value.

• OSType
• OSVersion
• OSImage

The SSM agent can only retrieve this information from network devices on which the SSM Agent is deployed. Typically, you would deploy a SSM Agent on devices whose performance you wish to monitor.

The SSMOracle agent retrieves MIB information by SNMP from devices running SSM agents. This agent retrieves information such as the Oracle database names, fields, and database sizes.

The SSMOracle agent can only retrieve this information from network devices on which the SSM Agent is deployed. Typically, you would deploy a SSM Agent on devices whose performance you wish to monitor.

TunnelAgent

Template for a Perl agent to retrieve information about all tunnels, including IPv6 over IPv4 tunnels, present in the network. This agent works in conjunction with the IPv6Interface agent.