Users Guide
Table Of Contents
- Introduction
- Setup and Administration
- Security Management
- Assigning User Privileges
- Disabling Guest and Anonymous Accounts in Supported Windows Operating Systems
- Configuring the SNMP Agent
- Configuring the SNMP Agent for Systems Running Supported Windows Operating Systems
- Configuring the SNMP Agent on Systems Running Supported Red Hat Enterprise Linux
- Configuring the SNMP Agent on Systems Running Supported SUSE Linux Enterprise Server
- Configuring the SNMP Agent on Systems Running Supported VMware ESX 4.X Operating Systems to Proxy VMware MIBs
- Configuring the SNMP Agent on Systems Running Supported VMware ESXi 4.X Operating Systems
- Firewall Configuration on Systems Running Supported Red Hat Enterprise Linux Operating Systems and SUSE Linux Enterprise Server
- Using Server Administrator
- Server Administrator Services
- Working With Remote Access Controller
- Overview
- Viewing Basic Information
- Configuring the Remote Access Device to use a LAN Connection
- Configuring the Remote Access Device to use a Serial Port Connection
- Configuring the Remote Access Device to use a Serial Over LAN Connection
- Additional Configuration for iDRAC
- Configuring Remote Access Device Users
- Setting Platform Event Filter Alerts
- Server Administrator Logs
- Setting Alert Actions
- Setting Alert Actions for Systems Running Supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server Operating Systems
- Setting Alert Actions in Microsoft Windows Server 2003 and Windows Server 2008
- Setting Alert Action Execute Application in Windows Server 2008
- BMC/iDRAC Platform Events Filter Alert Messages
- Understanding Service Names
- Troubleshooting
- Frequently Asked Questions
- Index
Setup and Administration 31
The second change is to modify the default access line to give read-only
access to the entire MIB tree for the public community. Server Administrator
looks for the following line:
access notConfigGroup "" any noauth exact systemview
none none
If Server Administrator finds the line above, it modifies the line so that it reads:
access notConfigGroup "" any noauth exact all none none
These changes to the default SNMP agent configuration give read-only access
to the entire MIB tree for the public community.
NOTE: To ensure that Server Administrator is able to modify the SNMP agent
configuration for providing proper access to systems management data, it is
recommended that any other SNMP agent configuration changes be made after
installing Server Administrator.
Server Administrator SNMP communicates with the SNMP agent using the
SNMP Multiplexing (SMUX) protocol. When Server Administrator SNMP
connects to the SNMP agent, it sends an object identifier to the SNMP agent
to identify itself as a SMUX peer. Because that object identifier must be
configured with the SNMP agent, Server Administrator adds the following
line to the SNMP agent configuration file, /etc/snmp/snmpd.conf, during
installation if it does not exist:
smuxpeer .1.3.6.1.4.1.674.10892.1
Changing the SNMP Community Name
Configuring the SNMP community names determines which systems are able
to manage your system through SNMP. The SNMP community name used by
management applications must match an SNMP community name configured
on the Server Administrator system so that the management applications can
retrieve management information from Server Administrator.
To change the SNMP community name used for retrieving management
information from a system running Server Administrator, edit the SNMP agent
configuration file, /etc/snmp/snmpd.conf, and perform the following steps:
book.book Page 31 Tuesday, July 6, 2010 12:01 PM