McDATA 316095-B21, StorageWorks 2/140, StorageWorks 2/24 User Manual
E/OS SNMP Support Manual
P/N 620-000131-630
REV A
E/OS SNMP Support Manual
ii
Record of Revisions and Updates
Copyright © 2005 McDATA Corporation. All rights reserved.
Printed June 2005
Ninth Edition
McDATA, the McDATA logo, McDATA Eclipse, Fabricenter, HotCAT, Intrepid, Multi-Capable Storage
Network Solutions, Networking the World's Business Data, nScale, nView, OPENready, SANavigator,
SANtegrity, SANvergence, SecureConnect and Sphereon are trademarks or registered trademarks of
McDATA Corporation. OEM and Reseller logos are the property of such parties and are reprinted with limited
use permission. All other trademarks are the property of their respective companies. All specifications subject
to change.
No part of this publication may be reproduced or distributed in any form or by any means, or stored in a
database or retrieval system, without the prior written consent of McDATA Corporation.
The information contained in this document is subject to change without notice. McDATA Corporation
assumes no responsibility for any errors that may appear.
All computer software programs, including but not limited to microcode, described in this document are
furnished under a license, and may be used or copied only in accordance with the terms of such license.
McDATA either owns or has the right to license the computer software programs described in this document.
McDATA Corporation retains all rights, title and interest in the computer software programs.
McDATA Corporation makes no warranties, expressed or implied, by operation of law or otherwise, relating
to this document, the products or the computer software programs described herein. McDATA
CORPORATION DISCLAIMS ALL IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR
A PARTICULAR PURPOSE. In no event shall McDATA Corporation be liable for (a) incidental, indirect,
special, or consequential damages or (b) any damages whatsoever resulting from the loss of use, data or
profits, arising out of this document, even if advised of the possibility of such damages.
Revision Date Description
620-000131-000 6/2001 Initial release of Manual
620-000131-100 11/2001 Update to manual
620-000131-200 5/2002 Update to manual
620-000131-300 9/2002 Update to support EFCM 6.1and 6.2
620-000131-400 10/2002 Update to support EFCM 6.1, 6.2, & 6.3
620-000131-500 2/2003 Update to support E/OS 5.1 and EFCM 7.0
620-000131-600 8/2003 Update to support E/OS 5.2 and EFCM 7.2
620-000131-610 11/2003 Update to support E/OS 6.0
620-000131-620 2/2005 Update to support E/OS 7.0
620-000131-630 6/2005 Update to support E/OS 8.0
Contents
iii
Preface............................................................................................................................ vii
Chapter 1 Introduction to SNMP
Network Management using SNMP..............................................1-1
SNMP Features ..........................................................................1-2
SNMP Commands.....................................................................1-2
Why Variables exist In a Managed Device ............................1-3
How SNMP Changes Variables in a Managed Device ........1-3
SNMPv3 ......................................................................................1-4
SNMP Community co-existence..............................................1-5
Security Features........................................................................1-5
E/OS SNMPv3 Configuration .................................................1-6
Standard MIBs............................................................................1-7
Private Enterprise MIBs............................................................1-8
Traps and Their Purpose ..........................................................1-9
Chapter 2 McDATA SNMP Support
Overview............................................................................................2-1
E/OS Trap Overview .......................................................................2-2
E/OS Trap summary table.......................................................2-3
MIB Definitions: MIB-II..................................................................2-20
System Group...........................................................................2-20
Interfaces Group .....................................................................2-22
Address Translation Group ..................................................2-29
IP Group...................................................................................2-30
IP Routing group ....................................................................2-36
ICMP Group ............................................................................2-42
TCP Group...............................................................................2-47
Contents
E/OS SNMP Support Manual
iv
Contents
UDP Group..............................................................................2-52
SNMP Group...........................................................................2-53
Fabric Element Management MIB................................................2-60
Predefined types......................................................................2-60
Fibre Alliance MIB..........................................................................2-96
Type definitions.......................................................................2-96
Trap Types..............................................................................2-146
Appendix A Fibre Alliance MIB
FA MIB ..............................................................................................A-1
Textual conventions for this MIB...........................................A-4
Connectivity unit group ..........................................................A-6
Event group.............................................................................A-34
SNMP trap registration group..............................................A-65
Related traps............................................................................A-68
Conformance definitions.......................................................A-69
Conformance units .................................................................A-70
Appendix B FC Management MIB
FCMGMT-MIB Definitions ............................................................ B-1
Connectivity unit group ................................................................. B-4
Sensor table.............................................................................. B-19
Port Table........................................................................................ B-23
Event Group ................................................................................... B-35
Link Table ................................................................................ B-39
Port Statistics........................................................................... B-46
FC Simple Name Server Table.............................................. B-64
SNMP Trap Registration Group.................................................. B-69
Related Traps.................................................................................. B-73
Appendix C McDATA Private Enterprise MIB
FCEOS.MIB.......................................................................................C-1
Textual conventions for this MIB...........................................C-3
Enterprise Specific Object Identifiers.....................................C-5
Fibre Channel product lines....................................................C-5
Groups in FCEOS MIB.............................................................C-5
System Group............................................................................C-6
Fibre Channel FRU Group ....................................................C-10
Fibre Channel Port Group.....................................................C-13
NPIV Information...................................................................C-39
Fibre Channel Zoning Group ...............................................C-42
v
Contents
Contents
Fibre Channel Threshold Alert Group................................ C-47
FCEOS Enterprise-specific Trap Definitions............................. C-51
Appendix D Fabric Element Management MIB
FCFE.MIB .........................................................................................D-1
Configuration group................................................................D-6
Operation group.....................................................................D-18
F_Port Fabric Login table...................................................... D-21
FxPort Fabric Login table......................................................D-25
Error group ............................................................................. D-30
Accounting Groups................................................................ D-35
Class 2 Accounting table.......................................................D-40
Class 3 Accounting Group....................................................D-43
Capability Group ................................................................... D-46
Appendix E MIB II
Groups in MIB II...............................................................................E-1
System group.............................................................................E-2
Interfaces group ........................................................................E-5
Address Translation group....................................................E-14
IP group....................................................................................E-16
ICMP group .............................................................................E-33
TCP group................................................................................E-40
SNMP group ............................................................................E-50
Appendix F SNMP Framework MIB
SNMP Framework MIB...................................................................F-1
Textual Conventions.................................................................F-2
The snmpEngine Group...........................................................F-7
Appendix G SNMPv3 MIB
SNMPv3 MIB ...................................................................................G-1
User based SM MIB ................................................................. G-1
SNMP View Based Acm MIB Definitions .......................... G-21
MIB views................................................................................ G-32
SNMP-COMMUNITY-MIB .................................................. G-40
Appendix H MIB Objects Listing
MIB Objects Listed by OID ...........................................................H-1
E/OS SNMP Support Manual
vi
Contents
MIB Objects Listed Alphabetically ............................................ H-45
MIB Objects Listed Alphabetically ............................................ H-82
Index ................................................................................................................................i-1
vii
Preface
This publication is part of the documentation suite that supports the
McDATA
®
Sphereon™ 3016 Fabric Switch, Sphereon 3032 Fabric
Switch, Sphereon 3216 Fabric Switch, Sphereon 3232 Fabric Switch,
Sphereon 4300 Fabric Switch, Sphereon 4400 Fabric Switch, Sphereon
4500 Fabric Switch, Sphereon 4700 Fabric Switch, ES-1000 Switch,
ED-5000 Director, Intrepid
®
6064 Director, and Intrepid 6140
Director.
Who Should Use This Manual
Use this publication if you are planning to use SNMP to manage any
of the McDATA switching products listed above.
The publications listed in Related Publications provide considerable
information about both concepts and McDATA products
.Organization of This Manual
This publication is organized as follows:
Chapter 1, Introduction to SNMP, provides an introduction and
overview of Simple Network Management (SNMP) and its
operation.
Chapter 2, McDATA SNMP Support, describes specific
information available through SNMP, especially the Management
Information Bases (MIBs) that are supported and the SNMP traps
generated by the McDATA directors and switches.
Appendix A, Fibre Alliance MIB lists the MIB definitions of Fibre
Alliance MIB.
viii
E/OS SNMP Support Manual
Preface
Appendix B, FC Management MIB, lists the FC Management MIB
3.0.
Appendix C, McDATA Private Enterprise MIB, lists the McDATA
private enterprise MIBs.
Appendix D, Fabric Element Management MIB, lists the SNMP
Framework MIB.
Appendix E, MIB II lists the MIB-II, the RFC1213.mib renamed.
Appendix F, SNMP Framework MIB lists the definitions of
managed objects for the Fabric Element in Fibre Channel
Standard.
Appendix G, SNMPv3 MIB contains the listing of MIB objects by
OID and alphabetically.
Appendix H, MIB Objects Listing lists the definitions of managed
objects for SNMPv3.
An Index is also provided.
Manual Updates
Check the McDATA web site at www.mcdata.com for possible
updates or supplements to this manual.
Related Publications
Other publications that provide additional information about the
products mentioned in this manual are:
• E/OS Command Line Interface User Manual (620-000134-740)
• McDATA Enterprise Fabric Connectivity Manager User Manual
(620-005001)
• McDATA Products in a SAN Environment -Planning Manual
(620-000124)
•Intrepid 6140 and 6064 Directors Element Manager User Manual
(620-000172).
• McDATA Intrepid 6064 Director Installation and Service Manual
(620-000108)
• McDATA Intrepid 6140 Director Installation and Service Manual
(620-000157)
• McDATA Sphereon 3016 and 3216 Fabric Switch Element Manager
User Manual (620-000174)
Preface
ix
Preface
• McDATA Sphereon 3032 and 3232 Fabric Switch Element Manager
User Manual (620-000173)
• McDATA Sphereon 3016 and 3216 Switch Installation and Service
Manual (620-000154)
• McDATA Sphereon 3032 and 3232 Switch Installation and Service
Manual (620-000155)
• McDATA Sphereon 4500 Switch Installation and Service Manual
(620-000159)
• McDATA Sphereon 4500 Fabric Switch Element Manager User
Manual (620-000175)
• McDATA Sphereon 4400 Fabric Switch Installation and Service
Manual (620-000238)
• McDATA Sphereon 4400 Switch Element Manager User Manual
(620-000241)
• EFCM Basic User Manual (620-000240)
• McDATA Sphereon 4700 Fabric Switch Installation and Service
Manual (620-000239)
• McDATA Sphereon 4700 Fabric Switch Element Manager User
Manual (620-000242)
• McDATA Sphereon 4300 Switch Installation and Service Manual
(620-000171)
• SANavigator User Guide (621-000013)
• SNMP Agent User Manual (621-000021)
x
E/OS SNMP Support Manual
Preface
Manual Conventions The following notational conventions are used in this document.
Where to Get Help For technical support, McDATA® end-user customers should call the
phone number located on the service label attached to the front or
rear of the hardware product.
McDATA’s “Best in Class” Solution Center provides a single point of
contact for customers seeking help. The Solution Center will research,
explore, and resolve inquires or service requests regarding McDATA
products and services. The Solution Center is staffed 24 hours a day,
7 days a week, including holidays.
NOTE: To expedite warranty entitlement, please have your product serial
number available.
McDATA Corporation
380 Interlocken Crescent
Broomfield, CO 80021
Phone: (800) 752-4572 or (720) 558-3910
Fax: (720) 558-3851
E-mail: support@mcdata.com
Convention Meaning
Italic Outside book references, names of user interface
windows, panels, buttons, and dialog boxes
Bold Keyboard keys
Click. As in “click the icon on
the navigation control panel.”
Click with the left mouse button on the object to activate a
function.
Right-click. As in “right click
the product icon.”
Click with the right mouse button on the object to activate
a function.
Select. As in “select the log
entry.”
Click once on the object to highlight it.
Preface
xi
Preface
NOTE: Customers who purchased the hardware product from a company
other than McDATA should contact that company’s service representative
for technical support.
Forwarding
Publication
Comments
We sincerely appreciate any comments about this publication. Did
you find this manual easy or difficult to use? Did it lack necessary
information? Were there any errors? Could its organization be
improved?
Please send your comments via e-mail, our home page, or FAX.
Identify the manual, and provide page numbers and details. Thank
you.
Ordering Publications To order a paper copy of this manual, submit a purchase order as
described in Ordering McDATA Documentation Instructions, which is
found on McDATA’s web site, http://www.mcdata.com. To obtain
documentation CD-ROMs, contact your sales representative.
Trademarks The following terms, indicated by a registered trademark symbol (®)
or trademark symbol (™) on first use in this publication, are
trademarks of McDATA Corporation in the United States, other
countries, or both:
Registered Trademarks
Trademarks
Fabricenter
®
E/OS™
HotCAT
®
Eclipse™
Intrepid
®
Fibre Channel Director™
McDATA
®
OPENconnectors™
OPENready
®
SANvergence™
SANavigator
®
Sphereon™
SANtegrity
®
All other trademarked terms, indicated by a registered trademark
symbol (®) or trademark symbol (™) on first use in this publication,
E-mail: pubsmgr@mcdata.com
Home Page: http://www.mcdata.com
FAX: Technical Communications Manager
(720) 558-8999
xii
E/OS SNMP Support Manual
Preface
are trademarks of their respective owners in the United States, other
countries, or both.
Introduction to SNMP
1-1
1
Introduction to SNMP
The Simple Network Management Protocol (SNMP) is a complete but
simple mechanism for network management. Network management
is a broad term, including workstation configuration, assignment of
IP addresses, network design, architecture, network security, and
topologies. All this can fall within the scope of a network manager.
Any protocol for managing networks must allow virtually all
network devices and systems to communicate statistics and status
information to network management stations (network managers).
This communication must be independent of the primary network
transmission medium and impose little effect on the efficiency of the
network. Network managers must be able to obtain status
information from managed devices, and make changes in the way the
managed devices handle network traffic. SNMP is one way of
meeting these requirements.
Network Management using SNMP
SNMP is designed on the manager-agent paradigm, with the agent
residing in the managed device. Information is exchanged between
agents (devices on the network being managed) and managers
(devices on the network through which management is done).
Administrators can use SNMP to manage the switch configuration,
faults, performance, accounting, and security from remote SNMP
management stations.
There are many possible transactions between agents and managers.
These transactions vary widely with the different types of devices
1
1-2
E/OS SNMP Support Manual
Introduction to SNMP
that can be managed. In such a case, the list of commands a manager
must be able to issue is overwhelming, and every new manageable
device increases the list. SNMP was created to simplify the task of
managing and meeting the demands of any growing network.
SNMP operates on a simple fetch-store concept. With SNMP, the
available transactions between manager and agent are limited to a
handful. The manager can request information from the agent or
modify variables on the agent. The agent can respond to a request by
sending information, or if enabled to do so, voluntarily notify the
manager of a change of status on the agent (issue a trap).
SNMP Features
SNMP is the only network management protocol that is widely
available from many vendors of TCP/IP networks and
internetworks.
Features of SNMP:
• Simple set of commands for network management.
• Minimal intervention required to manage new devices added to a
network.
• Adequate for many basic network management needs.
• Generalized for application to networks other than TCP/IP, such
as IPX and OSI.
• Considerable versatility for managing many types of devices.
• Same method of management can be used for all networks.
• Addresses security threats through authentication, data
encryption and access control.
SNMP Commands
The main SNMP commands are Get, GetNext, GetResponse, GetBulk,
Inform, Trap and Set.
• Get – The manager uses this command to fetch the value of a
specified variable from the agent.
• GetNext –The manager uses this command to fetch the value of
the variable next to the one specified in the command. This
command is used to retrieve lists and tables of management data.
• GetResponse –An agent sends the requested information to the
manager using this PDU.
1
Network Management using SNMP
1-3
Introduction to SNMP
• Set–A manager can change the variables in the agent by sending
this single command. This command is used to change the
management data.
• GetBulk–This command is used by the manager to retrieve
voluminous data from a large table in the agent.
• Trap–An Agent uses this command to inform the manager about
some unusual events. Refer to Traps and Their Purpose on page 1-9.
• Inform– This command is used by a manager to send alert to
another manager.
Figure 1-1 SNMP Commands and Responses
Why Variables exist
In a Managed
Device
Variables are the means by which devices like switches and directors
keep track of and control their performance apart from providing
access about their performance to network managers. A simple
example of a variable’s use is to set a port offline and turn the port
back on. Some variables just hold values that indicate status (for
example error counts). SNMP allows the network managers to have
access to some of the same variables for network management.
For purposes of the following explanation, an object is a data variable
that represents an attribute of a managed device.
How SNMP Changes
Variables in a
Managed Device
An agent has an interface to the actual object being managed
(Figure 1-2 on page 1-4). The agent understands SNMP and translates
between the manager and the object. Each SNMP element manages
specific objects. Each object has an identifier, OID. Objects may be
Ge
tRes
pons
ePD
U
G
et
R
e
qu
e
st
P
D
U
Get Values
NMS Switch
Se
tRes
pons
ePD
U
S
et
R
e
qu
e
st
P
D
U
Set Values
GetR
espo
nse
PDU
GetNextR
equest PDU
Get Next Values
NMS Switch
Tr
ap P
DU
Send Trap
1
1-4
E/OS SNMP Support Manual
Introduction to SNMP
retrieved and/or modified by the manager, and it is the agent’s job to
return the requested object’s value.
Within the agent is at least one, maybe several, collections of
definitions called Management Information Bases (MIBs). MIB
provides each OID with a readable label and other parameters. The
MIB acts as a dictionary that is used to assemble or interpret the
SNMP messages.
When an agent supports a standard MIB, it agrees to provide and
make available the variables listed in the MIB.
A MIB is an hierarchical tree of groups and variables. Operators at a
network management station enter a command with supported
groups and variables from the MIB.
Figure 1-2 Retrieving or Setting Values Using MIBs
SNMPv3
The E/OS provides additional level of security in the existing SNMP
framework by supporting the SNMPv3, which supplements the
SNMPv2c framework by providing security for messages and explicit
access control. The E/OS also supports SNMP versions 1 and 2,
Variable a
Variable b
Variable c
Variable d
Variable e
Variable f
Variable g
-
-
-
Agent
(Use MIB to
identify variable)
Managed
Device
Read status information
with GetRequest command
or
Set a variable to a value
with SetRequest command
NMS
MIB
Actual
Variable (object)
(x)y
(x)y
(x)y
(x)y
(x)y
1
Network Management using SNMP
1-5
Introduction to SNMP
which authenticate the SNMP requests based on the “community”
string.
ATTENTION!Before enabling SNMPv3, ensure all desired communities are
configured for SNMPv3 access. If existing community strings are not
configured for SNMPv3, then existing SNMP access will be lost.
SNMP Community co-existence
When SNMPv3 is enabled, SNMP Community Coexistence table
provides a way to use the earlier versions such as SNMPv1 and
SNMPv2c. The SNMP Community Coexistence table maps the
community names for SNMPv1 and SNMPv2 to a Security Name.
After retrieving the user name (security name) for the community
string, message processing occurs in the same way as that for
SNMPv3 packets.
Security Features
SNMPv3 provides the User-based Security Model (USM) and View-based
Access Control Model (VACM) features to address authentication, data
encryption, and access control.
User-based Security Model (USM)
The main security threats to an SNMP message are modification of
information, masquerading, disclosure, and message stream
modification. The User-based Security Model (USM) protects
SNMPv3 packets from these threats by utilizing the concept of
multiple users where each user has to specify a key for authentication
and privacy. The USM deals with authenticating/encrypting/
decrypting SNMP packets. The authentication protocols supported
are HMAC-MD5-96 and HMAC-SHA-96. The privacy protocol
supported is CBC-DES.
The SNMP agent recognizes up to 32 user names that can have one of
the following security levels:
• No authentication and no privacy (none)
• Authentication only (auth only)
• Authentication and privacy (authpriv)
1
1-6
E/OS SNMP Support Manual
Introduction to SNMP
Authentication can be used to restrict communication between two
authorized entities. Users cannot save messages and replay them
with altered content. Only authorized users can change
configurations of network devices.
View-based Access Control Model (VACM)
The View-based Access Control Model defines a set of services that
an application can use for checking access rights. It determines the
access rights of a group.
A group defines the access rights afforded to all the security names
(user names) which belong to that group. The combination of a
security model and a security name maps to at most one group
identified by a group name. The access rights that can be given to a
group are read-view, write-view and notify-view.
E/OS SNMPv3 Configuration
The security and access features for SNMPV3 provided by the
User-based Security Model (USM) and View-based Access Control
Model (VACM) require using multiple tables: User Table, Access
Table, Security-to-Group Table, and Target Table. The following
sections describe how SNMPv3 has been implemented in the E/OS.
USM Message Processing
The following steps describe how SNMPv3 messages are processed
in the User-based Security Model:
1. User table contains information such as user name, authentication
protocol, authentication key, privacy protocol, and encryption
key. Based on the user name field in the received packet, the
SNMP engine finds out the user entry from the table.
2. Flags are checked to see if authentication or security is needed.
3. If authentication is needed, the hash value is calculated using the
authentication protocol and authentication key, and matched
against the header.
1
Network Management using SNMP
1-7
Introduction to SNMP
4. If privacy is needed, the message is decrypted using the private
key; it is encrypted again before sending back.
NOTE: The authentication/privacy key (password) configured for an
SNMPv3 user on a switch is not localized. Therefore, the
authentication/privacy key configured in the SNMP management
application must be configured as a non-localized authentication/privacy
key in ASCII format. For more information on localization, refer to
http://www.ietf.org/rfc/rfc3414.txt?number=3414.
VACM Message Access Control
The following steps describe how SNMPv3 messages are processed
in the View-based Access Control Model:
1. A security name and security model pair are mapped to a group
name string. On receiving the packet, the agent checks for the
user name and security model and extracts the group name from
the security-to-group name table.
2. The vacmContextTable is used to store all locally available contexts.
The contextName found in the scoped PDU is then searched in
this table. If the search is successful, it gives an index of the
context in the table. Otherwise a noSuchContext error is returned.
3. The vacmAccessTable is used get the view name of the MIB to be
referenced. This decision is based on the group name, context
name, security model and security level. The security model and
security level are derived from the received packet.
4. The derived view name is used to index into the
vacmFamilyTreeTable for access checking. The OID of a managed
object is then checked against this MIB view. If the OID is part of
the current MIB view, then access is granted; otherwise
errorIndication (notInView) is returned.
Currently, you can configure SNMPv3 only through the command
line interface (CLI) of the switch. Refer to the E/OS Command Line
Interface User Manual for detailed information about the commands
and their respective parameters.
Standard MIBs
Standard MIBs are those created and approved by the Internet
Engineering Task Force (IETF) and other Internet standards bodies
and are readily available for use with SNMP network management
stations. The standard MIBs provide a baseline of common
1
1-8
E/OS SNMP Support Manual
Introduction to SNMP
operations across a wide variety of managed devices. Chapter 2
describes the standard MIBs used by the various McDATA products.
Standard MIBs supported by McDATA products are:
• MIB-II (Internet MIB) as described in RFC1213: supported by all
switches and directors.
• User-based Security Model (USM) as described in RFC2574
• View-based Access Control Model (VACM) as described in
RFC2575
• SNMP Community MIB as described in RFC2576
• Fibre Alliance (FCMGMT) MIB, version 3.0: supported by EFC
Server, Sphereon™ 3016 Fabric Switch, Sphereon 3032 Fabric
Switch, Sphereon 3216 Fabric Switch, Sphereon 3232 Fabric
Switch, Sphereon 4300 Fabric Switch, Sphereon 4400 Fabric
Switch, Sphereon 4500 Fabric Switch, Sphereon 4700 Fabric
Switch, Intrepid
®
6064 Director, and Intrepid 6140 Director.
• Fibre Alliance (FCMGMT) MIB, version 3.1: supported by EFC
Server, Sphereon 3016 Fabric Switch, Sphereon 3032 Fabric
Switch, Sphereon 3216 Fabric Switch, Sphereon 3232 Fabric
Switch, Sphereon 4300 Fabric Switch, Sphereon 4400 Fabric
Switch, Sphereon 4500 Fabric Switch, Sphereon 4700 Fabric
Switch, Intrepid 6064 Director, and Intrepid 6140 Director.
• Fibre Channel Fabric Element (FCFE), version 1.10: supported by
all switches and directors.
Private Enterprise
MIBs
Private MIBs are those provided by the manufacturer of the managed
devices to allow management of device-specific items. Chapter 2
describes the McDATA private MIBs in more detail.
The McDATA private enterprise MIBs are:
• es1000 MIB, used by the ES-1000 switch
• ed5000 MIB, used by the ED-5000 director
• fcEos MIB, used by the supported by Sphereon 4500 switch,
Sphereon 4300 switch, Sphereon 3016 switch, Sphereon 3216
switch, Sphereon 3232 switch, Sphereon 4400 switch, Sphereon
4700 switch, Intrepid 6064 Director, and Intrepid 6140 Director
(updated to support zoning, port binding, threshold alerts, and
open trunking).
1
Network Management using SNMP
1-9
Introduction to SNMP
Traps and Their
Purpose
Traps are unsolicited status reports, or status change indicators a
managed object sends to a network manager. The destination address
and UDP port number for traps can be configured for each managed
agent. If no specific value is configured for UDP port number it takes
the default value. The default value for UDP port number is 162.
1
1-10
E/OS SNMP Support Manual
Introduction to SNMP
McDATA SNMP Support
2-1
2
McDATA SNMP
Support
Overview
SNMP is a protocol that uses the User Data Protocol (UDP) to
exchange messages between an SNMP agent (in a managed device)
and a management station residing on a network. Although SNMP
can be made available over other protocols, McDATA only supports
UDP.
To be monitored and managed remotely by a network management
station, each switch or director is equipped with an SNMP agent. This
agent is a software process within the switch that receives
management requests and generates corresponding responses by
accessing the data specified for the MIB-II, Fabric Element MIB, Fibre
Alliance MIB, and FCEOS enterprise specific MIB. In addition, the
agent gives each switch the ability to notify a management station
when an important event occurs by sending a trap to the
management station.
Seven MIBs are supported:
• A subset of the Standard MIB-II for TCP/IP –based Internet as
specified in RFC1213.
• Fabric Element MIB containing support for FL ports as specified
in Fibre Channel standards.
• Fibre Alliance MIB (also referred to as the FC Management MIB).
• Fibre Alliance MIB, version 3.0
2
2-2
E/OS SNMP Support Manual
McDATA SNMP Support
• FCEOS MIB, the McDATA enterprise specific MIB supporting the
McDATA switch and director firmware.
•SNMP Framework MIB.
•SNMPv3 MIB.
E/OS Trap Overview
NOTE: E/OS traps support SNMP V1/V2c/V3 format regardless of MIB
definition syntax.
SNMP traps are specific types of SNMP messages enclosed in UDP
packets as shown:
[ IP Packet [ UDP Packet [ SNMP Message ] ] ]
The SNMP message format is:
[ Version | Community | SNMP PDU ]
There are different formats for the SNMP PDUs, including trap
PDUs, for SNMPv1 and SNMPv2. These are summarized here:
SNMPv1 Trap PDU:
[ Enterprise | Agent address | Generic trap type | Specific trap code
| Time stamp | Object/Value 1 | Object/Value 2…. ]
The following descriptions summarize these fields:
Enterprise—Identifies the type of managed object generating the
trap.
Agent address—Provides the address of the managed object
generating the trap.
Generic trap type—Indicates one of a number of generic trap types.
Specific trap code—Indicates one of a number of specific trap codes.
Time stamp—Provides the amount of time that has elapsed between
the last network reinitialization and generation of the trap.
Variable bindings—The data field of the SNMPv1 Trap PDU. Each
variable binding associates a particular object instance with its
current value.
2
E/OS Trap Overview
2-3
McDATA SNMP Support
The following descriptions summarize the fields illustrated below for
the SNMPv2 PDU format:
PDU type—Identifies the type of PDU transmitted (Get, GetNext,
Inform, Response, Set, or Trap).
Request ID—Associates SNMP requests with responses.
Error status—Indicates one of a number of errors and error types.
Only the response operation sets this field. Other operations set this
field to zero.
Error index—Associates an error with a particular object instance.
Only the response operation sets this field. Other operations set this
field to zero.
Variable bindings—Serves as the data field of the SNMPv2 PDU.
Each variable binding associates a particular object instance with its
current value (with the exception of Get and GetNext requests, for
which the value is ignored).
Get, GetNext, Inform, Response, Set, and Trap PDUs Contain the
Same Fields:
[PDU type | Request ID | Error status | Error index | Object/Value
1 | Object/Value 2]
For the SNMPv2 trap PDU, the first and second variable bindings
contain the uptime and the trap OID respectively. Following the
uptime and trap OID are all the variable bindings specified in the
MIB for that particular trap.
E/OS Trap summary
table
This table shows the different kinds of traps supported by the switch
E/OS firmware.
Trap Severity Sent because MIB Tr a p O I D E/OS EFCM
Generic Authentication
Failure
N/A SNMP request from
an invalid community
is received
RFC-1157 YES YES
Generic Link Up N/A RFC-1157 YES NO
Generic Warm Start N/A Software reset RFC-1157 YES NO
Generic Cold Start N/A Power up RFC-1157 YES NO
2
2-4
E/OS SNMP Support Manual
McDATA SNMP Support
ES port change N/A A change in port
status
FCEOS 1.3.6.1.4.1.289.1 YES NO
ES FRU change N/A A change in FRU
status
FCEOS 1.3.6.1.4.1.289.2 YES NO
ES invalid attachment N/A Invalid attachment to
a port.
FCEOS 1.3.6.1.4.1.289.3 YES NO
ES threshold alert N/A Threshold specified in
threshold table has
been exceeded for a
port.
FCEOS 1.3.6.1.4.1.289.4 YES NO
ES FRU removed* N/A A FRU has been
removed or
transitioned to
unknown status.
FCEOS 1.3.6.1.4.1.289.5 YES NO
ES FRU active* N/A A FRU transitioned to
the active state.
FCEOS 1.3.6.1.4.1.289.6 YES NO
ES FRU backup* N/A A FRU transitioned to
the backup state.
FCEOS 1.3.6.1.4.1.289.7 YES NO
ES FRU update* N/A A FRU transitioned to
the update/busy
status.
FCEOS 1.3.6.1.4.1.289.8 YES NO
ES FRU failed* N/A A FRU failed. FCEOS 1.3.6.1.4.1.289.9 YES NO
ES link bit error event* N/A The bit error rate for a
link has exceeded an
allowed threshold.
FCEOS 1.3.6.1.4.1.289.10 YES NO
ES link no signal event* N/A Loss of signal or sync. FCEOS 1.3.6.1.4.1.289.11 YES NO
ES link NOS event* N/A A not operational
primitive sequence
timeout occurred.
FCEOS 1.3.6.1.4.1.289.12 YES NO
ES link failure event* N/A A primitive sequence
timeout occurred.
FCEOS 1.3.6.1.4.1.289.13 YES NO
ES link invalid event* N/A An invalid primitive
sequence is detected.
FCEOS 1.3.6.1.4.1.289.14 YES NO
Trap Severity Sent because MIB Tr a p O I D E/OS EFCM
2
E/OS Trap Overview
2-5
McDATA SNMP Support
* EOS 6.0 and later only.
The following sections describe each trap and the variables within the
traps. For each variable, the OID is expressed as a numeric value first
followed by a second line showing the symbolic object name.
Appended to the right of the OIDs are the index values for each
object. Most of the objects within traps are actually table values. (That
is, they refer to a MIB object which is part of a table defined in the
MIB). Each SNMP table value must have an index appended to
identify a specific table row.
For example, the enterprise specific port status change trap has the
variable binding for fcEosPortOpStatus, which is a table entry value.
So the OID for fcEosPortOpStatus (1.3.6.1.4.1.289.2.1.1.2.3.1.1.3)
specifies a table column – to get a value for a specific port the table
index (port_number+1) must be appended to the OID. If the trap
occurred because of a change on port 5, then the actual variable OID
would be 1.3.6.1.4.1.289.2.1.1.2.3.1.1.3.
Enterprise-specific
Port Status Change
Trap
This trap is sent for each port which has a status change. There is 1
variable binding as follows:
ES link added event* N/A A new link has been
detected. NOTE: up to
10 seconds may
elapse after link is
added before trap is
sent.
FCEOS 1.3.6.1.4.1.289.15 YES NO
Switch SCN Alert Change in switch
status.
FC-MGMNT 1.3.6.1.2.1.8888.0.1 YES YES
Switch Deletion Alert A switch is removed
from management
control.
FC-MGMNT 1.3.6.1.2.1.8888.0.2 NO YES
Event SCN Info A new system event
was generated.
FC-MGMNT 1.3.6.1.2.1.8888.0.3 YES YES
Sensor SCN Alert Change in status for
FAN/FAN2/POWER
FRUs.
FC-MGMNT 1.3.6.1.2.1.8888.0.4 YES YES
Port SCN Alert A change in port
status.
FC-MGMNT 1.3.6.1.2.1.8888.0.5 YES YES
Trap Severity Sent because MIB Tr a p O I D E/OS EFCM
2
2-6
E/OS SNMP Support Manual
McDATA SNMP Support
Enterprise-specific
FRU Status Change
Trap
This trap is sent for each FRU which has a status change. There is 1
variable binding as follows:
Enterprise-specific
Invalid Attachment
Trap
This trap is sent when an invalid attachment occurs (a device is
attached, with a WWN specifically disallowed by port binding).
There is 1 variable binding.
Binding OIB Value
1 1.3.6.1.4.1.289.2.1.1.2.3.1.1.3.port_number+1
fcEosPortOpStatus.port_number+1
New status value. See definition for
fcEosPortOpStatus
Binding OID Values
1 1.3.6.1.4.1.289.2.1.1.2.2.1.1.3.fru_code.fru_pos
fcEosFruStatus.fru_code.fru_pos
Where fru_code has one of the following values:
0x01, Backplane
0x02, Control Processor card
0x03, Serial Crossbar
0x04, Shasta 32 center fan module
0x05, Fan module
0x06, Power supply module
0x07, Reserved
0x08, Longwave, Single-Mode, LC connector, 1 Gig (Port card)
0x09, Shortwave, Multi-Mode, LC connector, 1 Gig (Port card)
0x0A, Mixed, LC connector, 1 Gig (Port card)
0x0B, SFO pluggable, 1 Gig
0x0C, SFO pluggable, 2 Gig
0x0D, Longwave, Single-Mode, MT-RJ connector, 1 Gig
0x0E , Shortwave, Multi-Mode, MT-RJ connector, 1 Gig
0x0F , Mixed, MT-RJ connector, 1 Gig
0x10 , F-Port, internal, 1 Gig
And where fru_pos is a number specific to each possible FRU
position, which varies from product to product. For example, on an
Intrepid 6140 director, there are three fans numbered 1 to 3.
New status value. See definition for
fcEosFruStatus
2
E/OS Trap Overview
2-7
McDATA SNMP Support
Enterprise-specific
Threshold Alert Trap
This trap is sent when port traffic exceeds a specified threshold.
There are 2 variable bindings.
Enterprise-specific
FRU Traps
The enterprise specific FRU traps (FRU removed, FRU active, FRU
backup, FRU update, FRU failed: type codes 5-9) share the same
bindings. There are 4 variable bindings for these traps:
Binding OID Value
1 1.3.6.1.4.1.289.2.1.1.2.4.1.1.4.port_number+1
fcEosPortAttachedWWN.port_number+1
WWN of invalid attached device. See
definition for fcEosPortAttachedWWN.
Binding OID Value
1 1.3.6.1.4.1.289.2.1.1.2.3.1.1.1.port_number+1
fcEosPortIndex.port_number+1
Port number of port with threshold alert.
2 1.3.6.1.4.1.289.2.1.1.2.6.1.1.1.threshold_number
fcEosTAIndex.threshold_number
The index of the threshold which was
triggered.
Binding OID Value
1 1.3.6.1.4.1.289.2.1.1.2.2.1.1.1.fru_code.fru_position
fcEosFruCode.fru_code.fru_position
The FRU code for this FRU. See table
below.
2 1.3.6.1.4.1.289.2.1.1.2.2.1.1.2.fru_code.fru_position
fcEosFruPosition.fru_code.fru_position
The FRU position for this FRU. The first
position is 1.
3 1.3.6.1.4.1.289.2.1.1.2.1.15.0
fcEosSysSwitchName
The ASCII name of the switch
4 1.3.6.1.4.1.289.2.1.1.2.1.16.0
fcEosSysSwitchId
The Worldwide Name of the switch.
2
2-8
E/OS SNMP Support Manual
McDATA SNMP Support
Enterprise-specific
Link Traps
The enterprise specific link traps (link bit error, link no signal, link
NOS, link failure, link invalid, link added: type codes 10 – 15) share
the same bindings. There are 5 variable bindings for these traps:
FRU Code Description
1 Backplane
2 Control Processor card
3 Serial Crossbar
4 Shasta 32 center fan module
5Fan module
6 Power supply module
7 Reserved
8 Longwave, Single-Mode, LC connector, 1 Gig
9 Shortwave, Multi-Mode, LC connector, 1 Gig
10 Mixed, LC connector, 1 Gig
11 SFO pluggable, 1 Gig
12 SFO pluggable, 2 Gig
13 Longwave, Single-Mode, MT-RJ connector, 1 Gig
14 Shortwave, Multi-Mode, MT-RJ connector, 1 Gig
15 Mixed, MT-RJ connector, 1 Gig
16 F-Port, internal, 1 Gig
17 F-Port, internal, 1 Gig - XPM
18 F-Port, internal, 1 Gig - IPM
Loading...