Paradyne 7112 manual Controlling Snmp Access, Assigning Snmp Community Names and Access Levels

Models: 7112

1 156
Download 156 pages 11.03 Kb
Page 34
Image 34

Security

Table 4-2. ATI Access Conditions (2 of 2)

If access to the ATI is through the . . .

Then . . .

What to do now?

Terminal port and the ATI is already in use with a Telnet session

User Interface Already In Use message appears with the active user's IP address and Login ID.

Try again later.

When the ATI is available, the message User Interface Idle appears. Press Enter for the Main Menu.

Telnet session and the

Connection Failed

Try again later.

ATI is currently in use

message appears. The

 

 

DSU/CSU allows only

 

 

one ATI session.

 

 

 

 

Controlling SNMP Access

There are three methods for limiting SNMP access.

HDisable the SNMP management option.

HAssign SNMP community names and access levels. The DSU/CSU supports SNMP Version 1, which provides limited security through the use of community names.

HLimit SNMP access through validation of the IP address of each allowed SNMP manager.

Assigning SNMP Community Names and Access Levels

The DSU/CSU can be managed by an SNMP manager supporting the SNMP protocol. The community name must be supplied by an external SNMP manager accessing an object in the MIB.

To define SNMP community names, follow this menu selection sequence:

Main Menu Configuration (Load Configuration From)

SNMP General SNMP Management

Refer to Table A-8,General SNMP Management Options, to:

HEnable SNMP Management.

HAssign the SNMP community names of the SNMP Managers that are allowed to access the DSU/CSU's Management Information Base (MIB).

HSpecify read or read-write access for each SNMP community name.

4-6

March 1998

7112-A2-GB20-20

Page 34
Image 34
Paradyne 7112 manual Controlling Snmp Access, Assigning Snmp Community Names and Access Levels, Connection Failed