Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual
4-34 Managing
Cisco MeetingPlace Audio Server System Manager’s Guide
February 27, 2004
3.
You must delete the private community and rename the public and trap
communities. Use the information in the following table.
communities. Use the information in the following table.
4.
Restart the MeetingPlace 8112 or 8106 server for these changes to take
effect.
effect.
N
OTES
•
If a problem exists, contact the administrator of hosting.
•
The SNMP agent does not accept queries on trap communities. So, for
example, to make queries using the public community, do not designate
public to be a trap community.
example, to make queries using the public community, do not designate
public to be a trap community.
Traps appear on SNMP management tools as events with a trap code. Because
most SNMP management tools permit configuration of both the event
message and the alarm severity, it is recommended that system managers
configure T1 and Gateway SIM traps so that they are easy to spot and
understand. For a list of generic codes, see
most SNMP management tools permit configuration of both the event
message and the alarm severity, it is recommended that system managers
configure T1 and Gateway SIM traps so that they are easy to spot and
understand. For a list of generic codes, see
To
Do this
Delete the private
community
community
Click the
Query
button, then click the
<
or
>
button to
find the private community. Click
Delete
, then click
Save Changes
.
Rename the public
community
community
Click the
Query
button, and click the
<
or
>
button to
find the public community. Type the following name
exactly as shown (it is case sensitive):
exactly as shown (it is case sensitive):
rwcHP1
Then click
Save Changes
.
N
OTE
This value is the same on all servers; it does not
change.
Rename the trap
community
community
Set the IP address to the current server value. Then
click
click
Save Changes
.