2.13 Discovering Avaya Communication Server Resources

Use the Discovery_NortelCS Knowledge Script to discover the various components of an Avaya CS1000 IP telephony system installation: Call Server, Signaling Server, Media Gateway Controller, Network Routing Server, MC32S, Enterprise Common Manager, Voice Gateway Media Card, and SIP Line Gateway.

The Discovery_NortelCS Knowledge Script also discovers co-resident Call Servers, Signaling Servers, and Element Managers. When co-resident, these components are installed on a single processor.

For CS1000 version 6.0 and later environments, the script discovers Bandwidth Management Zone (BMZ) objects on the Call Server. For earlier versions of CS1000, BMZ objects are discovered on the Signaling Server.

By default, Discovery_NortelCS runs weekly, on Sunday at 3 AM. The default schedule allows the discovery process to run at a time that is probably less busy for your Call Server.

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_NortelCS Knowledge Script again to update your list of resource objects. In addition, if you are running this module on AppManager 8 and 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 parameters on the Values tab as needed:

Parameter	How to Set It
Event Notification
Raise event if discovery fails?	Select Yes to raise an event if discovery fails for any reason. The default is Yes.
Event severity if discovery fails	Set the event severity level, from 1 to 40, to reflect the importance when discovery fails. The default is 5.
Raise event if discovery partially succeeds?	Select Yes to raise an event if discovery is partially successful. A partially successful discovery is one in which, for example, AppManager can discover devices but cannot create an inventory report. Or one in which, for example, AppManager can discover all Signaling Servers, but not the Bandwidth Management Zones. The default is Yes.
Event severity if discovery partially succeeds	Set the event severity level, from 1 to 40, to reflect the importance when discovery is partially successful. The default is 15.
Raise event if discovery succeeds?	Select Yes to raise an event if discovery succeeds. The default is unselected.
Event severity if discovery succeeds	Set the event severity level, from 1 to 40, to reflect the importance when discovery succeeds. The default is 25.
Call Server	Provide the hostname or IP address of the CS1000 Call Server, such as CS1000_CS. Do not enter the IP address or hostname of the Call Server that is part of the Media Gateway. Important Provide only one Call Server hostname or IP address. Discovery is meant to discover only one CS environment.
List of NortelCS devices	Use this parameter if you know which CS1000 devices you want to discover. Type a list of the devices you want to discover. Use a comma to separate the names in the list; for example: CS1000_VGMC,CS1000_SS. You can type hostnames (if you use DNS in your environment) or ELAN IP addresses. Notes Leave this field blank to discover only the Call Server, which you identified in the previous parameter. The community string information for each device you list in this field must be configured in Security Manager before you run this script. For more information, see Section 2.6, Configuring SNMP Community Strings.
List of NortelCS device ranges	Type a list of ELAN IP address ranges for the CS1000 devices you want to discover. Spaces are invalid in the list; only numbers, dashes, periods, and commas are allowed. For example: 10.0.1.1-10.0.1.254,10.0.4.1-10.0.4.254. Notes Leave this field blank to discover only the Call Server, which you identified in the Call Server parameter. 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 NortelCS devices	Instead of listing each CS1000 device separately, you can specify the full path to a file on the proxy agent computer that contains a device name on each line of the file. Notes Leave this field blank to discover only the Call Server, which you identified in the Call Server parameter. The community string information for each device listed in the file must be configured in Security Manager before you run this script. For more information, see Section 2.6, Configuring SNMP Community Strings.
Discovery timeout	Specify the maximum amount of time (no more than 60 minutes) the script should attempt discovery before stopping as an unsuccessful discovery. The default is 10 minutes.
Discover phones using the Call Server’s Entity MIB?	Select Yes to use the Entity MIB (management information base) to count IP phones for the inventory report. AppManager will perform an SNMP query of this Call Server MIB to retrieve the inventory results. This parameter is applicable only for CS1000 4.0 and later. Disable this option if you use CS1000 3.0. For more information, see Section 4.6.5, Configuring the Call Server to Count IP Phones.