Step 9: Configuring The Topology-Dependent Parameters - Cisco SCE 2000 4/8xFE Quick Start Manual

E :
XAMPLE
Following is a sample SNMP configuration, configuring one trap manager, one GET community, and one SET
community, and enabling the authentication failure trap, as well as all enterprise traps.
Would you like to enter the SNMP configuration menu? [no]: y
Enable SNMP management? [no]: y
Enter SNMP GET community name[]: public
Enter Access list number allowing access with this community string, use '0' to allow
all: 0
Would you like to add another SNMP GET community? [no]:
Enter SNMP SET community name[]: private
Enter Access list number allowing access with this community string, use '0' to allow
all: 2
Would you like to add another SNMP SET community? [no]:
Would you like to configure SNMP trap managers? [no]: y
Enter SNMP trap manager IP address: 10.1.1.253
Enter SNMP trap manager community string: public
Enter trap manager SNMP version: 2c
Would you like to add another SNMP trap manager? [no]:
Enable the 'Authentication Failure' trap [no]: y
Enable SCE enterprise traps []: y
Enter system administrator contact name []: John Smith

Step 9: Configuring the Topology-Dependent Parameters

The topology configuration menu is a series of guided questions relating to the deployment of the SCE 2000 in the
network and its mode of operation. Values for the parameters are configured based on the user answers.
The correct value for each parameter must be ascertained before configuring the system to make sure that the system will
function in the desired manner. (See Topology for a comprehensive discussion of topology and the related parameters.)
Values may not be requested for all topology-dependent parameters, as certain parameters do not apply to all topologies.
Note
There are six topology-related parameters:
Connection mode — Can be either of the following, depending on the physical installation of the SCE 2000.
•
Inline
•
• Receive-only
Type of deployment — Can be one of the following, depending on the actual deployment:
•
Single-SCE Platform — a single SCE 2000 is deployed on one or two FE links
•
Cascade — two cascaded SCE 2000s are deployed on two FE links, working as a fully redundant solution.
•
Physically connected link (cascade topology only) — In a cascade topology, the user must assign an index to each
•
of the links. This index is used to identify the services per link.
In a single-SCE platform deployment, the indices of the links cannot be changed by the user and are:
link-0 — the link connected to ports 1 and 2
•
• link-1 — the link connected to ports 3 and 4
In a cascade deployment, the user must define which link is connected to which SCE 2000. The index must be
different for each SCE 2000. In this case the user can choose one of the following:
31