|
|
The process of configuring the Cisco 90 Series DSL Management Agent is explained in this chapter.
When the Cisco 90 Series DSL Management Agent is started, a dialog box is displayed with two icons that launch two different configuration programs. The icon labeled PCTCP Config starts the IP configuration program, and the icon labeled SNMP Config starts the SNMP configuration program. Double-clicking either icon starts the program associated with that icon.
The Frame Relay switch protocol should be configured to the Frame Relay UNI (user to network interface) specification and running T1.617 Annex D local management protocol. The Frame Relay switch is set to be the network side of the Annex D link and the Cisco 90 Series DSL Management Agent is set to be the user side of the Annex D link (the agent polls the Frame Relay switch).
The first step is to configure the agent with an IP address and a subnet mask so that the SNMP agent can communicate on the local-area network using IP. If the SNMP manager application is not located on the same Ethernet subnet, the IP address for the router you are connected to should also be entered.
Perform the following steps to configure IP:
Step 1 Double-click the PCTCP Config icon to run the IP configuration program. The program displays a dialog box with various options.
Step 2 Select the option labeled Internet Addresses. This displays a dialog box with three spaces for address entry.
Step 3 In the space labeled IP Address:, enter the IP address for the Cisco 90 Series DSL Management Agent. Your IP addresses will be provided by your system administrator, and must be entered in dotted decimal format (123.45.67.890).
Step 4 In the space labeled Subnet Mask:, enter the subnet mask as 255.255.255.0 (or the one provided by your system administrator).
Step 5 In the space labeled Routers:, enter the IP address for the default router you are connected to on your Ethernet local area network. This is required if the agent and all SNMP managers are not on the same LAN.
Step 6 Close the PCTCP Config dialog by selecting Close from the File menu.
Step 7 Reboot the Cisco 90 Series DSL Management Agent by pressing and releasing the Reset switch on the front panel.
After entering the IP addresses for your system, test the configuration to verify that the Cisco 90 Series DSL Management Agent is able to transmit and receive over the TCP/IP connection, and that other hosts on the network can communicate with the agent.
Test the IP configuration by performing these steps:
Step 1 Double-click the Ping icon on the agent to run the ping program.
Step 2 In the space labeled Host, enter the IP address in dotted decimal format of another host (preferably the SNMP manager) on the network you are connected to, then send a ping to that address by clicking the Start button on the right side of the dialog.
Step 3 If the result indicates that the host you were sending the ping to is alive, the Cisco 90 Series DSL Management Agent is correctly transmitting on the network using TCP/IP.
Step 4 Go to another host and issue a ping command from that host to the Cisco 90 Series DSL Management Agent's IP address.
Step 5 If the result indicates that the Cisco 90 Series DSL Management Agent is alive, the agent is correctly receiving traffic from the network using TCP/IP.
Step 6 If the SNMP manager is not located on the same LAN as the agent, repeat Step 2 through Step 5 using the SNMP manager. This will test the default gateway.
This section is used to set the SNMP community strings, which set the access permissions and maintain security. You can also restrict use of a community string based on the IP address of the SNMP manager.
The SNMP configuration program displays the SNMP management agent configuration file. When the SNMP Config icon is double-clicked, it automatically displays the SNMP configuration file in an ASCII editor. This file is organized into three sections; the third section (labeled SECTION 3) must be edited for your system.
The format for the community strings is:
communityEntry localSnmpIDSTRING GROUP localSnmpID default MANAGER# nonVolatile.
The variable STRING is replaced with the community string to be verified by this SNMP management agent.
The sample file on the next page illustrates Section 3 of the SNMP configuration file. Note that only a few rows in Section 3 are not "commented out." Those rows are the ones that contain the SNMP community strings that are actually used in the configuration of the SNMP management agent.
####################### S E C T I O N 3 #######################
### THIS SECTION IS MODIFIED TO SET COMMUNITY STRINGS ETC. ###
###################################################################
# First we define zero or more transportEntries which define an IP
# address, mask, and MTU for an SNMP manager. These are called
# Manager1, Manager2, etc. They may be used to restrict the use
# of a particular community string to a particular manager or
# subnet, or to define which managers will receive traps.
# Edit the IP address (1.2.3.4 below) to specify the IP address of
# the manager or subnet. To define an entire subnet set the
# ReceiveMask to the subnet mask for that subnet. Leave it set to
# 255.255.255.255:0 for a single manager.
# The Index field should be a unique integer for each line 1, 2, 3, etc
# The Domain field should always be set to 'snmpUDPDomain'
# The MTU field is the maximum packet size (in bytes) that will be sent
# The MemoryType field should always be set to 'nonVolatile'
# Remove the leading '#' on the Manager2 and Manager3 lines if needed
# Add additional lines if needed
# transportLabel Index Domain IP-Address ReceiveMask MTU MemoryType
transportEntry Manager1 1 snmpUDPDomain 1.2.3.4:0 255.255.255.255:0 1500 nonVolatile
#transportEntry Manager2 2 snmpUDPDomain 1.2.3.4:0 255.255.255.255:0 1500 nonVolatile
#transportEntry Manager3 3 snmpUDPDomain 1.2.3.4:0 255.255.255.255:0 1500 nonVolatile
# Next, we define the community strings. The format for these entries is:
#communityEntry localSnmpID STRING GROUP localSnmpID default MANAGER# nonVolatile
# where STRING is the community string to be sent by the SNMP manager
# GROUP is ReadOnly or ReadWrite
# MANAGER# is a transport label (Manager1 etc) from the transportEntry above
# and all other feilds must be exactly as specified
# If the MANAGER feild is set to '-', any manager can use the defined community
# string. Otherwise only those managers defined by the transportEntry can.
# Define a read only community string of 'public' accessible from any IP address
communityEntry localSnmpID public ReadOnly localSnmpID default - nonVolatile
# Define a read/write community string of 'woof' accessible from any IP address
communityEntry localSnmpID woof ReadWrite localSnmpID default - nonVolatile
# Define a read/write community string of 'Cisco' accessible only from Manager1
communityEntry localSnmpID Cisco ReadWrite localSnmpID default Manager1 nonVolatile
# Finally, we define which managers to send traps to. The format is:
#notifyEntry INDEX snmpv1 STRING MANAGER# default All nonVolatile
# where INDEX is a unique integer for each line (1, 2, 3, etc)
# STRING is the community string to be sent with the trap
# MANAGER# is a transport label (Manager1 etc) from the transportEntry
# above to send the trap to and all other fields must be exactly as specified
# Send traps with community string public to Manager1
notifyEntry 1 snmpv1 public Manager1 default All nonVolatile
################ E N D O F S E C T I O N 3 ################
Perform the following steps to set the community string:
Step 1 Double click the SNMP Config icon to activate the configuration program.
Click in the cursor bar to scroll down until you reach Section 3 in the SNMP configuration file.
 | Time Saver The next step is required only if you want to to restrict access based on the IP address of the SNMP manager or you want to define managers to receive traps. If you do not want to do this, continue with Step 4. |
Step 3 The following line sets the default SNMP manager as manager 1:
transportEntry Manager1 1 snmpUDPDomain 1.2.3.4:0 255.255.255.255:0 1500 nonVolatile
There are lines provided directly below this setting to allow setting two additional managers (manager 2 and manager 3) if desired. To activate an additional manager, delete the # at the beginning of the line. Additional mangers can be activated by adding additional lines with the same format. You can substitute a different string for this entry, if desired.
Using your mouse, highlight the IP address entry and type in the appropriate entry for your Cisco 90 Series DSL Management Agent. Your system administrator will provide you with the correct IP address.
Step 4 Click in the cursor bar to scroll down until you reach the first line that sets a community string.
This line in Section 3 appears as follows:
# Define a read only community string of 'public' accessible from any IP address
communityEntry localSnmpID public ReadOnly localSnmpID default - nonVolatile
This line sets the read-only community string to "public," and makes it accessible from any IP address. Change the string "public" to the community string you want to to use for read-only access. If you want to restrict the use of this community string to a particular manager, change the dash (-) character following "default" to that manager's name (MANAGER1, for example).
Step 5 Click in the cursor bar to scroll down until you reach the next line that sets a community string.
This line in Section 3 appears as follows:
# Define a read/write community string of 'woof' accessible from any IP address
communityEntry localSnmpID woof ReadWrite localSnmp ID default - nonVolatile
This line sets a read-write community string to "woof," and also makes it accessible from any IP address. Change the string "woof" to the community string that you want to use for read-write access. Again, the dash (-) character following "default" can be changed to restrict the use of this community string to a particular manager.
Step 6 Click in the cursor bar to scroll down until you reach the last line that sets a community string.
This line in Section 3 appears as follows:
# Define a read/write community string of 'Cisco' accessible only from Manager1
communityEntry localSnmpID Cisco ReadWrite localSnmpID default Manager1 nonVolatile
The final line sets a read-write community string to "Cisco," and makes it accessible only from manager 1. Because the transport entry was not activated for manager 2 and manager 3 in Step 3, these entities are not activated. You can comment out this line if it is not needed by placing a pound sign (#) character at the beginning of the line.
You can replace these three community strings with your own choices to improve your system security. To replace the strings use your mouse to highlight the string, then type a new string in its place.
Step 7 You can define which managers to send SNMP traps to with the following line:
Manager1 default All nonVolatile
The default setting sends SNMP traps to manager 1. You can use another manager instead of manager 1 by editing this entry, or you can add additional managers by adding additional lines in the same format.
Step 1 Compile the Cisco 90i MIB on an SNMP manager, if it is not already capable of managing the Cisco 90i family.
Step 2 Configure the SNMP manager to recognize and communicate with the IP address of the Cisco 90 Series DSL Management Agent.
Step 3 Set the SNMP manager to use the community strings defined in the previous section. Set the SNMP type to SNMPv1, if applicable.
Step 4 Using the SNMP manager, issue a get command on the frxSys table. This displays information about the Cisco 90 Series DSL Management Agent, if the read-only community string configuration was successful.
Step 5 Test the read-write community strings by issuing a set command on the frxSysName object. This sets the name for the agent, if the community string configuration was successful.
Step 6 As a final test of the WAN link to the Frame Relay switch, perform a get command on the frxAgtChStatus object. This will return the status of the Frame Relay Annex D signaling channel and verify that the link is up (1).
Step 7 Install at least one D4 channel bank as specified in the next chapter, "Installing D4 Channel Banks and Cisco xDSL Channel Units."
The last step in installing the SNMP agent is to set the elements in the frxSys group and the frxDefault group. The system group contains such items as the system name and the real time clock (needed to support BRITE cards). The default group contains the initial condition when a new channel unit is installed. You should set the default group to the configuration you expect will be used by the largest number of circuits. If the default group is changed at a later date, cards installed before the change will not be affected. You are now ready to install your first D4 channel bank.
|
|