Setting Up
5-70
9161-A2-GH30-40
April 1999
Setting Up for SNMP Management
Use the General SNMP Management Options (see Table 5-15) to specify what is
needed to allow the system to be managed as an SNMP agent by an NMS
supporting the SNMP protocol.
Configuration Edit/Display
→
Management and Communication
→
General
SNMP Management
Table 5-15.
General SNMP Management Options (1 of 2)
SNMP Management
Possible Settings: Enable, Disable
Default Setting: Disable
Determines whether SNMP can be used for management of the T1 access unit.
Enable – The T1 access unit can be managed as an SNMP agent by an SNMP
compatible NMS.
Disable – The T1 access unit will not respond to SNMP messages or send SNMP
traps.
Community Name 1
Possible Settings: ASCII text entry, Clear
Default Setting: [public] in ASCII text entry
Specifies the first of two names that are allowed to access the objects in the unit’s
Management Information Base (MIB). The community name must be supplied by an
external SNMP manager whenever that manager tries to access an object in the MIB.
ASCII Text Field – Adds to or changes the Community 1 name (maximum
255 characters).
Clear – Clears the Community Name 1 field.
Name 1 Access
Possible Settings: Read, Read/Write
Default Setting: Read
Specifies the type of access allowed for community name 1. This is the type of access
allowed for external SNMP managers accessing objects in the MIB using the
Community Name 1 configuration option.
Read – Allows read-only access to the objects in the MIB for the NAM when using the
Community Name 1 configuration option. This includes all objects specified as either
read-only or read/write in the MIB RFCs.
Read/Write – Allows read and write access to the objects in the MIB for the NAM when
using the Community Name 1 configuration option. Allows access for all objects
specified as read/write in the MIB RFCs. However, access for all read-only objects is
specified as read-only.
Summary of Contents for 9261
Page 1: ...MODEL 916x 926x T1 ACCESS MUX TECHNICAL REFERENCE Document No 9161 A2 GH30 40 April 1999 ...
Page 34: ...Management and Control 2 6 9161 A2 GH30 40 April 1999 This page intentionally left blank ...
Page 54: ...User Interface 4 10 9161 A2 GH30 40 April 1999 This page intentionally left blank ...
Page 92: ...Setting Up 5 38 9161 A2 GH30 40 April 1999 Example Channel Allocation ...
Page 142: ...Security 6 10 9161 A2 GH30 40 April 1999 This page intentionally left blank ...
Page 252: ...IP Addressing B 8 9161 A2 GH30 40 April 1999 This page intentionally left blank ...