Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual

Page of 314
Cisco MeetingServer 5.1 System Manager’s Guide   
 
                  102 
 
Cisco Systems 
 
March 2003 
Network Management Information controls high level access to the 
MeetingPlace SNMP module and allows MeetingPlace to exchange SNMP 
data with the rest of your network. 
To ensure the SNMP system manager contacts the right person for any issues 
related to the MeetingPlace system, enter data in the System contact and 
System location fields. 
 
Note: The MeetingPlace system contact and location can also 
be set from the SNMP management station. 
Under the Network Management Information topic in the Configure tab, 
configure the following information: 
 
IP “port number”—The port on which MeetingPlace can find incoming 
SNMP messages. Port 161 is most commonly used. 
 
System contact—The name of the MeetingPlace system manager. 
 
System location—The physical location of the MeetingPlace system. 
Setting up Community Information 
The Network Management Communities topic on the Configure tab allows you 
to define SNMP communities for controlling access to MeetingPlace through 
SNMP. The Network Management Communities topic also shows you the 
network information available from the SNMP module. 
You can configure two types of network management communities: 
 
A trap community—Defines a host to which MeetingPlace sends 
standard MIB II traps. 
 
A non-trap community—Controls the type of access that is provided in 
response to an SNMP message: read-write, read only, or no access. 
Under the Network Mgmt Communities topic in the Configure tab, configure 
the following information: 
 
Name—The name of the network management community. Standard 
“public” and “private” communities are predefined. You may use these 
values or replace them with your own. 
 
IP address—The IP address to which traps are sent for trap communities. 
This parameter is ignored for non-trap communities. 
 
Read-write?—When set to Yes, SNMP messages for this community can 
modify stored SNMP data. (Ignored for trap communities.) Typically, 
managers choose read-only in the “public” community; “private” 
communities are often used for read-write access.