Extreme Networks 200 Series Using SNMP

62 Summit 200 Series Switch Installation and User Guide

Managing the Switch

You can specify a TCP port number to be used for SSH2 communication. By default the TCP port

number is 22.

The supported cipher is 3DES-CBC. The supported key exchange is DSA.

For additional information on the SSH protocol refer to [FIPS-186] Federal Information Processing

Standards Publication (FIPSPUB) 186, Digital Signature Standard, 18 May 1994. This can be downloaded

from: ftp://ftp.cs.hut.fi/pub/ssh. General technical information is also available from

http://www.ssh.fi.

After you obtain the SSH2 key value, copy the key to the SSH2 client application. Also, ensure that the

client is configured for any nondefault TCP port information that you have configured on the switch.

Once these tasks are accomplished, you may form an SSH2-encrypted session with the switch.

Using SNMP

Any Network Manager running the Simple Network Management Protocol (SNMP) can manage the

switch, provided the Management Information Base (MIB) is installed correctly on the management

station. Each Network Manager provides its own user interface to the management facilities.

The following sections describe how to get started if you want to use an SNMP manager. It assumes

you are already familiar with SNMP management. If not, refer to the following publication:

The Simple Book

by Marshall T. Rose

ISBN 0-13-8121611-9

Published by Prentice Hall.

To have access to the SNMP agent residing in the switch, at least one VLAN must have an IP address

assigned to it.

In addition to private MIBs, the switch supports the standard MIBs listed in Appendix C.

The following SNMP parameters can be configured on the switch:

• Authorized trap receivers—An authorized trap receiver can be one or more network management

stations on your network. The switch sends SNMP traps to all trap receivers. You can have a

maximum of 16 trap receivers configured for each switch. Entries in this list can also be created,

modified, and deleted using the RMON2 trapDestTable MIB variable, as described in RFC 2021.

• Community strings—The community strings allow a simple method of authentication between the

switch and the remote Network Manager. There are two types of community strings on the switch.

Read community strings provide read-only access to the switch. The default read-only community

string is public. Read-write community strings provide read and write access to the switch. The

default read-write community string is private. A total of eight community strings can be configured

on the switch. The community string for all authorized trap receivers must be configured on the