Technical Configuration Guide for SNMP v2.0 December 2006
Nortel is a recognized leader in delivering communications capabilities that enhance the human
experience, ignite and power global commerce, and secure and protect the world’s most critical
information. Serving both service provider and enterprise customers, Nortel delivers innovative
technology solutions encompassing end-to-end broadband, Voice over IP, multimedia services
and applications, and wireless broadband designed to help people solve the world’s greatest
challenges. Nortel does business in more than 150 countries. For more information, visit Nortel
on the Web at nortel.com.
NORTEL NETWORKS CONFIDENTIAL: This document contains material considered to be
proprietary to Nortel. No part of it shall be disclosed to a third party for any reason except after
receiving express written permission from Nortel and only after securing agreement from the third
party not to disclose any part of this document. Receipt of this document does not confer any
type of license to make, sell or use any device based upon the teachings of the document.
Receipt of the document does not constitute a publication of any part hereof and Nortel explicitly
retains exclusive ownership rights to all proprietary material contained herein. This restriction
does not limit the right to use information contained herein if it is obtained from any other source
without restriction.
Nortel Business Made Simple, Nortel, the Nortel logo, and the Globemark are trademarks of
Nortel Networks.
Nortel Networks. All rights reserved. Information in this document is subject to
change without notice. Nortel assumes no responsibility for any errors that may appear in this
document.
Disclaimer
This engineering d ocument contains the best inform ation available at the t ime of publication in
terms of supporting the application and engineering of Nortel products in the customer
environment. They are solely for use by Nortel customers and meant as a guide for network
engineers and planners from a network engineering perspective. All information is subject to
interpretation based on internal Norte l test methodol ogies which wer e used to derive th e various
capacity and equipment performance criteria and should be reviewed with Nortel engineering
primes prior to implementation in a live environment.
______________________________________________________________________________________________________
NORTEL External Distribution
1
Technical Configuration Guide for SNMP v2.0 December 2006
Abstract
This document provi des an overvie w on how to config ure SNMP on the Norte l Ethernet Routin g
Switch (ERS) 8600.
______________________________________________________________________________________________________
NORTEL External Distribution
2
Technical Configuration Guide for SNMP v2.0 December 2006
Table 1: New Default Password Settings ......................................................................................19
Table 2: New Default Community Settings....................................................................................19
______________________________________________________________________________________________________
NORTEL External Distribution
4
Technical Configuration Guide for SNMP v2.0 December 2006
1. SNMPv3 Overvie w
SNMPv3 is the third version of the Internet-Standard Management Framework and is derived
from and builds u pon b oth the original Internet-Standard M ana gement Framework ( SNM Pv 1) a nd
the second Internet-Stan dard Managem ent Fram ework (SNMPv2). SNM Pv3 is not a s tand-alone
replacement for SNM Pv1 and/or SNMv2. It d efines se curity capab ilities to be used in c onjuncti on
with SNMPv2 (preferr ed) or SNMPv 1. As shown in the Figure 1 belo w, SNMPv3 s pecif ies a User
Security Model (U SM) that uses a payload of either a SNMPv1 or a SNMPv2 protocol dat a unit
(PDU).
PDU Processing
(SNMPv1 or SNMPv2)
Message Processing
(SNMPv3 USM)
UDP
UDP-H
V3-MH
V3-MH
SNMP PDU
SNMP PDU
SNMP PDU
PDU = Protocol Data Unit
USM = User Based Security
Authentication with in the User-based Secur ity Model (USM) allows t he recipient of the mes sage
to verify whom the message is from and whether the message has been altered. As per RFC
2574, if authentication is used, the entire message is checked for the integrity. Authentication
uses a secret key to produc e a fingerpr int of the m essage, which is incl uded in th e mes sage. T he
receiving entity uses the same secret key to validate the fingerprint. Currently there are 2
authentication protocols defined, HMAC-MD5 and HMAC-SHA-96 for use with USM.
While the USM provides the user-name/password authentication and privacy services, control
access to management information (MIB) must be defined. The View-based Access Control
Module (VACM) is used to define a set of services that an application can use for checking
access rights (read, wr ite, notify) to a par ticular object. V ACM uses the ASN.1 n otation (3.6.1.4)
or the name of the SNM P MIB branch, i.e. Org. Dod.In ternet. Privat e. T he adm inist rator can def in e
a MIB group view for a us er to allow access to an ap propriate portion of the MIB matched to an
approved security level. The three security levels are:
• NoAuthNoPriv-Communication without authentication and privacy
• AuthNoPriv-Communication with authentication (MD5 or SHA) and without privacy
• AuthPriv-Communication with authentication (MD5 or SHA) and privacy (DES or AES)
NOTE: Please refer to the Ether net Ro uti ng S witc h 86 00 4.1 re le as e not es ( Part number 317177D Rev 01) regarding im portant inf orm ation r egardin g SNMP v3. Spec ial c onsider ati ons nee d to be
considered regarding hidden and encrypted that contains community table information.
______________________________________________________________________________________________________
NORTEL External Distribution
5
Technical Configuration Guide for SNMP v2.0 December 2006
2. SNMP Upgrade Consider ations
Please note the following when upgra di ng sof t ware on the ERS8600.
Starting in software release 3.7 and continued to software release 4.1.x, the CLI command save
config creates a hidden and encrypted file that contains the SNMP community table information.
For security purposes, the save config command also removes reference to the existing SNMP
community strings in the newly created configuration file. Please note that if you only have one
CPU, and if you swap the CPU, you must backup all hidden files or else all the password and
SNMP references will be lost. If you do not backup the hidden files, you must reconfigure your
trap receivers and community strings every time you change the CPU.
The commands to change the SNMP Community strings and trap receivers in software release
3.3 have changed in software releases 3.5, 3.7, 4.0, and 4.1.x. However, even though software
releases 3.5, 3.7, 4.0, and 4.1.x use the same commands, in software release 3.7 and 4.1.x only,
the SNMP community strings and trap receivers are stored in a hidden and encrypted file and are
not found in the configuration file. This is similar with software releases 3.5 and 4.0; however the
files are stored in a hidden non-encrypted file. Upgrades from 3.7 to 4.1.x, all files are translated
as-is. Please see section 3.3.3 for more details.
2.1 Hidden File Details
Backup the following configuration files to either via FTP, a TFTP server or a PCMCIA card:
• shadov.txt
• snmp_usm.txt
• snmp_comm.txt
• password.txt
______________________________________________________________________________________________________
NORTEL External Distribution
6
Technical Configuration Guide for SNMP v2.0 December 2006
3. Blocking SNMP
By default, SNMP access is enabled. You can disable SNMP; this includes SNMPv1/v2 and
SNMPv3, access to the ERS 8600 by using the following commands:
If you wish to allow only SNMPv3 access, you c an d isa ble SNMPv1/2 by configur ing the SNMPv3
MIB view. Portions of the MIB can be conf igured to either include or exclude access at an MIB
OID level. This is explained in section 5.5 . For SNMPv3, this can be done on a per-user bas ic.
For SNMPv1/v2, it can be d one o n a g lob al/c om munity basis. By defau lt, SNM Pv 1/ v2 is p er mitted
access to all MIB OIDs un der 1.3 in the MIB O ID tree with the except ion with sections r elated to
the SNMP USM, VACM, and Community MIBs. This cannot be altered, but, if an additional
exclusion statement is added, the entire usable MIB can be disabled through SNMPv1/v2.
Specifically, if the entire MIB tree under 1.3.6 (iso org dod) is excluded, none of the switches
public or private MIBs will b e acces s ibl e.
To disable SNMPv1/v2 only, enter the following command:
• PP8600-B:6# config snmp-v3 mib-view create v1v2only 1.3.6 type exclude
At this point, SNMPv1/v2 will be disabled and only SNMPv3 will be allowed.
3.2 Blocking SNMP via an Access Policy – prior to
software release 3.7.9 or 4.1
You can also ena ble or disable SN MP via an Acces s Policy. Over all, the Acces s Policy feature
on the ERS 8600 supports the following feature:
•Access level: Specifies th e access level of the trust ed as hostreadOnly (ro), readW rite
(rw), or readWriteAll (rwa)
•Mode: Indic ates whether a packet having a so urce IP address that matches t his entry
should be permitted to enter the device or denied access.
•Service: Indicates the protocol to whic h this entry should be a pplied. Choices ar e telnet,
snmp, tftp, ftp, http, rlogin, and/or ssh.
•Precedence: Indicates the precedence of the policy. T he lower the number, the higher
the precedence (1 to 128).
•Network Address and Network Mask: Indicates the source network IP address and
mask. An address of 0.0.0.0 specifies any address on the network.
•Host: Indicates the trusted IP addres s of the hos t perf or ming rlogin or rsh into the dev ic e.
Applies only to rlogin and rsh.
•Access-strict: Sets the access level strictly.
______________________________________________________________________________________________________
NORTEL External Distribution
7
Technical Configuration Guide for SNMP v2.0 December 2006
To add an access polic y, you must first enable the ac cess policy feature gl obally by enter ing the
following command:
3.3 SNMP Group Access Policy – Release 3.7.9, 4.1 or
higher
In release 3.7.9 or 4.1, a new policy enhancem ent was added that allows the administrator to
specify a group or groups for SNMPv3 access. With SNMPv3, the community name is not
mapped to an access level, but det ermined only thr ough VACM. T his allows the administrator to
create separate policies for SNMP users based on USM or community and associate them to
groups.
The following items where added high-lighted in red below.
ERS-8610:5# config sys access-policy policy 1 ?
______________________________________________________________________________________________________
NORTEL External Distribution
9
Technical Configuration Guide for SNMP v2.0 December 2006
3.3.1 SNMPv3 Group Access Policy: Configuration Example
For this example, we wish to create a policy for read-writ e-all access and only allow teln et and
SNMPv3 access onl y for SNMPv3 usm group named grou p_example. Please see Section 5 in
regards to how to configure SNMPv3.
• ERS-8610:5# show sys access-policy snmp-group-info
snmpv3-groups :
Policy 1 snmpv3-groups :
Group Name Snmp-Model
Policy 2 snmpv3-groups :
Group Name Snmp-Model
group_example usm
3.3.2 SNMPv1/2 Group Access Policy: Configuration Example
As release 3.7 and 4.1 is based on the SNMPv3, you must add the SNMPv3 group name and
model for both SNMPv1 and SNMPv2 when setting up an access policy. To view the SNMPv3
group name and model, please use the following as shown below. Note that the items highlighted in red need to be added when setting up the access policy.
• ERS8610-B:5# show snmp-v3 group-access
=========================================================================
VACM Group Access Configuration
=========================================================================
______________________________________________________________________________________________________
NORTEL External Distribution
11
Technical Configuration Guide for SNMP v2.0 December 2006