User guide

2-24
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Chapter 2 Basic Concepts
What Are the General Features of Cisco MGM?
By configuring user access, you can:
• Provide user-access profiles that can be customized for each user. The user-access profile is a list
of operations or actions a user can perform coupled with assigned access privileges for each action.
• Assign access privileges to read, create (write), modify, and delete profiles.
By default, only the root user can start and stop the Cisco MGM core processes. The root user has
sufficient access privileges to launch all Cisco MGM applications and administer security.
Other users are assigned access privileges that enable them to perform operations within
security-controlled applications. Depending on the setting of access privileges by those who administer
security management, the operations are limited. Without the proper access privileges, users cannot
launch security-controlled applications.
Note For detailed information about user access, see Chapter 8, “Managing Security.”
2.3.5.5 NE Access Control
NE access control includes the ability to:
• Configure the username and password used by the Cisco MGM server and Cisco MGM
GateWay/CORBA to access NEs and retrieve alarms, configuration, and inventory information.
Note Each username and password specified must exist on the selected NE in order for Cisco
MGM to manage it. A new or modified password takes effect at the next reconnection.
• Configure the username and password on multiple NEs by using the bulk NE authentication feature.
With a single operation, you can specify the same username and password for NEs that belong to
the same group or are assigned to the same user.
• Manage NE user accounts by using the NE User Access Administration table. This feature supports
the ability to view, add, modify, and delete NE user accounts on one or more NEs.
• Monitor active NE users and log out selected users.
• Add predefined users on a selected NE.
2.3.5.6 Audit Log
The Audit Log contains information about significant events (user-initiated changes and activities) that
occurred on the Cisco MGM server during a specific time period for the purposes of establishing
accountability. It also helps in identifying remedial actions to correct an improper activity. The Audit
Log is implemented in the Cisco MGM database, where each record has a time stamp, record type, and
message string.
Tip See Chapter 8, “Managing Security” for a list of runtime-affecting operations that the Audit Log records
for monitoring purposes.