Hp LASERJET 5000 User Manual [pl]

Reference

Guide

hp StorageWorks

SNMP Reference for Directors

and Edge Switches

Product Version: FW v06.xx/HAFM SW v08.02.00

Fifth Edition (July 2004)

Part Number: AA–RQ7BE–TE

This guide introduces simple network management protocol (SNMP) and the associated commands to manage a network. It also explains SNMP management support for HP StorageWorks Directors, Edge Switches, and the HA-Fabric Manager (HAFM) server.

the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information contained in this document is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information is provided “as is” without warranty of any kind and is subject to change without notice. The warranties for Hewlett-Packard Company products are set forth in the express limited warranty statements for such products. Nothing herein should be construed as constituting an additional warranty.

Printed in the U.S.A.

SNMP Reference for Directors and Edge Switches Fifth Edition (July 2004) Part Number: AA–RQ7BE–TE

Contents

About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Text Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Equipment Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Rack Stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

HP Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

HP Storage Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

HP Authorized Reseller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1 Introduction to SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

SNMP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

SNMP Simplified. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

SNMP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Why Variables Exist in a Managed Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

How SNMP Changes Variables (Objects) in a Managed Device . . . . . . . . . . . . . . . . . . 18

Standard MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Private Enterprise MIBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Traps and Their Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Contents

2 SNMP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

SNMP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

EOS Trap Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

EOS Trap Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Enterprise-specific Port Status Change Trap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3SNMP Reference for Directors and Edge Switches

Contents

Enterprise-specific FRU Status Change Trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Enterprise-specific Invalid Attachment Trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Enterprise-specific Threshold Alert Trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

FA MIB Switch Status Change Trap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

FA MIB Event Trap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

FA MIB Sensor Trap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

FA MIB Port Status Change Trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

MIB Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

MIB-II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Interfaces Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Interfaces Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Address Translation Group/Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

IP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

IP Address Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

IP Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

IP Address Translation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Additional IP Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

ICMP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

TCP Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

TCP Connection Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Additional TCP Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

UDP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

UDP Listener Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

SNMP Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Fabric Element Management MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Fabric Element Management MIB Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

MIB objects defined in the Fabric Element MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Module Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Fx_Port Configuration Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Fx_Port Operation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Fx_Port Physical Level Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Fx_Port Fabric Login Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Fx_Port Error Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Class 1 Accounting Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Class 2 Accounting Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Class 3 Accounting Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Fx_Port Capability Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4 SNMP Reference for Directors and Edge Switches

Contents

Fibre Alliance MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Type Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Connectivity Unit Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

fcConnUnitTable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Firmware Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Sensor Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Port Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

The Event Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Link Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

fcConnUnitPortStatTable - Port Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Name Server Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

SNMP Trap Registration Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

The TrapRegTable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Trap Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Private (Enterprise-specific) FCEOS MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

System Group MIB Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

FRU Table (Module Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Port Table (Port Group). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Port Binding Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Zoning Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Active Zone Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Active Member Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Threshold Alert Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Enterprise Specific Traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Port State Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Protocol Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

A MIB Objects Sorted by OID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

B MIB Objects Sorted Alphabetically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201

Figures

1 SNMP commands and responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 Retrieving or setting values using MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Tables

1 Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5SNMP Reference for Directors and Edge Switches

Contents

6 SNMP Reference for Directors and Edge Switches

About This

Guide

This reference guide provides information to help you:

■ Understand management capabilities for HP StorageWorks Directors and

About this Guide

Edge Switches using the simple network management protocol (SNMP).

■ Utilize SNMP support for Directors, Edge Switches, and the High

Availability Fabric Manager (HAFM) server.

■ Obtain information about Management Information Bases (MIBs).

“About this Guide” topics include:

■ Overview, page 8

■ Conventions, page 9

■ Rack Stability, page 12

■ Getting Help, page 13

7SNMP Reference for Directors and Edge Switches

About this Guide

Overview

This section covers the following topics:

■ Intended Audience

■ Related Documentation

Intended Audience

This book is intended for use by administrators who are experienced with the following:

■ Fibre Channel technology.

■ StorageWorks Fibre Channel switches by Hewlett-Packard.

■ Simple network management protocol.

Conventions

Conventions consist of the following:

■ Document Conventions

■ Text Symbols

■ Equipment Symbols

Document Conventions

This document follows the conventions in Tab le 1.

Table 1: Document conventions

Blue text: Figure 1 Cross-reference links Bold Menu items, buttons, and key, tab, and

Italics

Monospace font User input, commands, code, file and

Monospace, italic font Command-line and code variables Blue underlined sans serif font text

(

http://www.hp.com

About this Guide

Convention Element

box names Text emphasis and document titles in

body text

directory names, and system responses (output and messages)

Web site addresses

)

Text Symbols

The following symbols may be found in the text of this guide. They have the following meanings:

WARNING: Text set off in this manner indicates that failure to follow

directions in the warning could result in bodily harm or death.

Caution: Text set off in this manner indicates that failure to follow directions

could result in damage to equipment or data.

SNMP Reference for Directors and Edge Switches

About this Guide

Tip: Text in a tip provides additional help to readers by providing nonessential or

optional techniques, procedures, or shortcuts.

Note: Text set off in this manner presents commentary, sidelights, or interesting points

of information.

Equipment Symbols

The following equipment symbols may be found on hardware for which this guide pertains. They have the following meanings:

Any enclosed surface or area of the equipment marked with these symbols indicates the presence of electrical shock hazards. Enclosed area contains no operator serviceable parts.

WARNING: To reduce the risk of personal injury from electrical shock

hazards, do not open this enclosure.

Any RJ-45 receptacle marked with these symbols indicates a network interface connection.

WARNING: To reduce the risk of electrical shock, fire, or damage to the

equipment, do not plug telephone or telecommunications connectors into this receptacle.

Any surface or area of the equipment marked with these symbols indicates the presence of a hot surface or hot component. Contact with this surface could result in injury.

WARNING: To reduce the risk of personal injury from a hot component,

allow the surface to cool before touching.

10 SNMP Reference for Directors and Edge Switches

About this Guide

Power supplies or systems marked with these symbols indicate the presence of multiple sources of power.

WARNING: To reduce the risk of personal injury from electrical

shock, remove all power cords to completely disconnect power from the power supplies and systems.

Any product or assembly marked with these symbols indicates that the component exceeds the recommended weight for one individual to handle safely.

WARNING: To reduce the risk of personal injury or damage to the

equipment, observe local occupational health and safety requirements and guidelines for manually handling material.

SNMP Reference for Directors and Edge Switches

About this Guide

Rack Stability

Rack stability protects personnel and equipment.

WARNING: To reduce the risk of personal injury or damage to the

equipment, be sure that:

■ The leveling jacks are extended to the floor.

■ The full weight of the rack rests on the leveling jacks.

■ In single rack installations, the stabilizing feet are attached to the rack.

■ In multiple rack installations, the racks are coupled.

■ Only one rack component is extended at any time. A rack may become

unstable if more than one rack component is extended for any reason.

12 SNMP Reference for Directors and Edge Switches

Getting Help

If you still have a question after reading this guide, contact an HP authorized service provider or access our web site:

HP Technical Support

Telephone numbers for worldwide technical support are listed on the following HP web site: of origin.

Note: For continuous quality improvement, calls may be recorded or monitored.

Be sure to have the following information available before calling:

■ Technical support registration number (if applicable)

■ Product serial numbers

■ Product model names and numbers

■ Applicable error messages

http://www.hp.com

http://www .hp.com/support/

About this Guide

. From this web site, select the country

■ Operating system type and revision level

■ Detailed, specific questions

HP Storage Web Site

The HP web site has the latest information on this product, as well as the latest drivers. Access storage at:

storage.html

. From this web site, select the appropriate product or solution.

HP Authorized Reseller

For the name of your nearest HP authorized reseller:

■ In the United States, call 1-800-345-1518

■ In Canada, call 1-800-263-5868

■ Elsewhere, see the HP web site for locations and telephone numbers:

http://www .hp .com

SNMP Reference for Directors and Edge Switches

http://www .hp.com/country/us/eng/prodserv/

About this Guide

14 SNMP Reference for Directors and Edge Switches

Introduction to SNMP

Network management is a broad term, including workstation configuration, assignment of IP addresses, network design, architecture, 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 not degrade 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.

Network managers must be able to do this without knowing anything about the managed device itself. Management using the simple network management protocol (SNMP) is one way of meeting these requirements.

15SNMP Reference for Directors and Edge Switches

Introduction to SNMP

SNMP Management

SNMP management is a mechanism for network management that is complete, but simple. It 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).

There are many possible transactions between agents and managers. These transactions vary widely with the different types of devices that can be managed. With so many varied requirements for reporting and management, the list of commands a manager must be able to issue is overwhelming, and every new manageable device can increase the list. SNMP was created to allow all these things to be easily done on 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, automatically notify the manager of a change of status on the agent (issue a trap).

With SNMP, administrators can manage Director and Edge Switch configurations, faults, performance, accounting, and security from remote SNMP management stations.

SNMP Simplified

SNMP is the only protocol for managing networks that is widely available from many vendors of Transmission Control protocol/Internet protocol (TCP/IP) networks and internetworks. SNMP:

■ Allows network management with a simple set of commands.

■ Allows new devices added to a network to be easily managed, with minimal

intervention.

■ Is adequate for many basic network management needs.

■ Is generalized for application to networks other than TCP/IP, such as IPX and

OSI.

■ Provides considerable versatility for managing a great many types of devices.

■ Allows all networks to employ the same method for management.

16 SNMP Reference for Directors and Edge Switches

SNMP Commands

A manager requests information from an agent by sending a single command, the Get command. The Get command also has a variation (GetNextRequest) that permits more efficient operation:

■ GetRequest – Requests the value of a specified variable on the agent. This

command is used to retrieve management data.

■ GetNextRequest – Requests the value of the next variable after the one

specified in the command. This command is used to retrieve lists and tables of management data.

An agent responds to a request by sending a single command, the GetResponse command. This command contains the requested information.

A manager changes information (variables) in the agent by sending a single command, the SetRequest command. This command is used to manipulate management data.

A trap is used by an agent to report extraordinary events. Refer to “Traps and

Their Purpose” on page 19. Figure 1 illustrates SNMP commands and responses:

Introduction to SNMP

Figure 1: SNMP commands and responses

Why Variables Exist in a Managed Device

Variables are the means by which a Director or Edge Switch (and other devices) keep track of their performance, control their own performance, and provide access to information about their performance for 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 network managers to have access to some of the same variables for network management.

17SNMP Reference for Directors and Edge Switches

Introduction to SNMP

Note: For purposes of the following explanation, an object is a data variable that

represents an attribute of a managed device.

How SNMP Changes Variables (Objects) in a Managed Device

An agent is the entity that interfaces to the object being managed (Figure 2). The agent understands the language of SNMP and translates between the manager and the object. Objects may be 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, possibly several, collections of definitions called Management Information Bases (MIBs). When an agent supports a standard MIB, it agrees to provide and make available the variables listed in the MIB.

A MIB is a hierarchical tree of groups and variables. Operators at a network management station enter a command with supported groups and variables from the MIB.

Figure 2: Retrieving or setting values using MIBs

Standard MIBs

Standard MIBs are those available with SNMP and designed for standard operation with a wide variety of managed devices. “SNMP Support” on page 21 describes the standard MIBs used by HP StorageWorks Directors, Edge Switches, and the HA-Fabric Manager (HAFM) application.

18 SNMP Reference for Directors and Edge Switches

Standard MIBs are:

■ MIB-II (Internet MIB), as described in RFC 1213: supported by all Directors

and Edge Switches.

■ Fibre Alliance (FCMGMT) MIB, version 3.1: supported by all Directors and

Edge Switches.

■ Fibre Channel Fabric Element (FCFE), version 1.10: supported by all

Directors, Edge Switches, and HAFM.

Private Enterprise MIBs

Private MIBs are those provided by the manufacturer of the managed devices to allow management of device-specific items. “SNMP Support” on page 21 describes the private MIBs in more detail.

The private enterprise MIB is the FCEOS MIB, which is used by Directors and Edge Switches to support zoning, port binding, threshold alerts, and trunking.

Traps and Their Purpose

Traps are unsolicited status reports, or status change indicators, that a managed object sends to a network manager. The destination address for traps is a configuration item for each managed agent.

Introduction to SNMP

19SNMP Reference for Directors and Edge Switches

Introduction to SNMP

20 SNMP Reference for Directors and Edge Switches

SNMP Support

This chapter describes SNMP support for HP StorageWorks Directors, Edge Switches, and the HA-Fabric Manager (HAFM) server.

21SNMP Reference for Directors and Edge Switches

SNMP Support

SNMP Management

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, HP StorageWorks Directors, Edge Switches, and the HA-Fabric Manager (HAFM) application only support UDP.

Overview

To be monitored and managed remotely by a network management station, each Edge 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, or 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.

Six MIBs are supported:

■ A subset of the Standard MIB-II for TCP/IP-based Internet, as specified in

RFC 1213.

■ 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), v3.0.

■ Fibre Alliance MIB (also referred to as the FC Management MIB), v3.1.

■ FCEOS MIB, which is the HP enterprise-specific MIB supporting HP Edge

Switch and Director firmware.

■ SNMP Framework MIB.

EOS Trap Overview

All EOS traps are SNMPv1 format, regardless of MIB definition syntax.) SNMP traps are specific types of SNMP messages enclosed in user datagram

protocol (UDP) packets as shown:

[ IP Packet [ UDP Packet [ SNMP Message ] ] ]

The SNMP message format is:

[ Version | Community | SNMP PDU ]

22 SNMP Reference for Directors and Edge Switches

SNMP Support

There are different formats for the SNMP protocol data units (PDUs), including trap PDUs, for SNMPv1 and SNMPv2. These are summarized here:

SNMPv1 Trap PDU:

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.

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:

23SNMP Reference for Directors and Edge Switches

SNMP Support

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.

EOS Trap Summary Table

This table shows the different kinds of traps supported by the switch EOS firmware.

Note: All EOS traps are SNMPv1 format, regardless of MIB definition syntax.

Sent

Trap Severity

Generic Authentication Failure

Generic Link Up N/A RFC-1157 YES NO Generic Warm

Start Generic Cold

Start ES Port Change N/A A change in

ES Fru Change N/A A change in

ES Invalid Attachment

ES Threshold Alert

N/A SNMP

N/A Software

N/A Power up. RFC-1157 YES NO

N/A Invalid

N/A Threshold

Because:

request from an invalid community is received.

reset.

port status.

FRU status.

attachment to a port.

specified in threshold table has been exceeded for a port.

MIB Trap OID EOS HAFM

RFC-1157 YES NO

FCEOS 1.3.6.1.4.1.289.1 YES NO

FCEOS 1.3.6.1.4.1.289.2 YES NO

FCEOS 1.3.6.1.4.1.289.3 YES NO

FCEOS 1.3.6.1.4.1.289.4 YES NO

24 SNMP Reference for Directors and Edge Switches

SNMP Support

Switch SCN Alert Change in

switch status.

Event SCN Info New system

event was generated.

Sensor SCN Alert Change in

status for FAN /FAN2/ POWER FRUs.

Port SCN Alert Change in

port status.

Following are sections describing 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.

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) must be appended to the OID. If the trap occurred because of a change on port 5, the actual variable OID would be 1.3.6.1.4.1.289.2.1.1.2.3.1.1.3.5.

FC-MGMNT 1.3.6.1.2.1.8888.0.1 YES YES

FC-MGMNT 1.3.6.1.2.1.8888.0.3 YES YES

FC-MGMNT 1.3.6.1.2.1.8888.0.4 YES YES

FC-MGMNT 1.3.6.1.2.1.8888.0.5 YES YES

Enterprise-specific Port Status Change Trap

This trap is sent for each port that has a status change. There is one variable binding, as follows:

Binding OID Value

1 1.3.6.1.4.1.289.2.1.1.2.3.1.1.3.port_number

fcEosPortOpStatus.port_number

New status value. See definition for “fcEosPortOpStatus” on page 133.

25SNMP Reference for Directors and Edge Switches

SNMP Support

Enterprise-specific FRU Status Change Trap

This trap is sent for each FRU that has a status change. There is one variable binding, as follows:

Binding OID Value

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, ES-3032 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

New status value. See definition for “fcEosFruStatus” on page 133.

And where fru_pos is a number specific to each possible FRU position, which varies from product to product. For example, on a Director 2/140 there are three fans, numbered 1 to 3.

26 SNMP Reference for Directors and Edge Switches

Enterprise-specific Invalid Attachment Trap

This trap is sent when an invalid attachment occurs (a device is attached, with a World Wide Name WWN specifically disallowed by port binding). There is one variable binding.

Binding OID Value

1 1.3.6.1.4.1.289.2.1.1.2.4.1.1.4.port_number

fcEosPortAttachedWWN.port_number

WWN of invalid attached device. See definition for “fcEosPortAttachedWWN” on page 139.

Enterprise-specific Threshold Alert Trap

This trap is sent when port traffic exceeds a specified threshold. There are two variable bindings.

Binding OID Value

1 1.3.6.1.4.1.289.2.1.1.2.3.1.1.1.port_number

fcEosPortIndex.port_number

2 1.3.6.1.4.1.289.2.1.1.2.6.1.1.1.threshold_number

fcEosTAIndex.threshold_number

Port number of port with threshold alert.

The index of the threshold which was triggered.

SNMP Support

FA MIB Switch Status Change Trap

This trap is sent when the switch status changes. There are two variable bindings.

Binding OID Value

1 1.3.6.1.2.1.8888.1.1.3.1.6.<unit-id>

fcConnUnitStatus.<unit-id> Where unit-id is the WWN of the switch,

with 8 zeros appended, for a total length of

16. Example:

1.2.3.4.5.6.7.8.0.0.0.0.0.0.0.0

2 1.3.6.1.2.1.8888.1.1.3.1.5.<unit-id>

fcConnUnitState.<unit-id> Where unit-id is the WWN of the switch,

with 8 zeros appended, for a total length of

16. Example:

1.2.3.4.5.6.7.8.0.0.0.0.0.0.0.0

Unit status. See definition for “FcConnUnitStatus” on page 91.

Unit state. See definition for “FcConnUnitStatus” on page 91.

27SNMP Reference for Directors and Edge Switches

SNMP Support

FA MIB Event Trap

This trap is sent when an internal software event is generated. There are four variable bindings.

Binding OID Value

1 1.3.6.1.2.1.8888.1.1.3.1.1.<unit-id>

fcConnUnitId.<unit-id> Where unit-id is the WWN of the switch, with 8

zeros, appended for a total length of 16. Example: 1.2.3.4.5.6.7.8.0.0.0.0.0.0.0.0

The value is the same as unit-id: the WWN of the switch, with 8 zeros appended, for a total length of 16. Example:

1.2.3.4.5.6.7.8.0.0.0.0.0.0.0.0

28 SNMP Reference for Directors and Edge Switches

SNMP Support

2 1.3.6.1.2.1.8888.1.1.7.1.5.<unit-id><event-in

dex> fcConnUnitEventType.<unit-id><event-index> Where unit-id is the WWN of the switch with 8

zeros appended for a total length of 16. Example: 1.2.3.4.5.6.7.8.0.0.0.0.0.0.0.0

And where event-index is an integer index of the event table, a unique incrementing value assigned to each event. The event table always contains the most recent 200 events which met the filter criteria in place when the event occurred.

3 1.3.6.1.2.1.8888.1.1.7.1.6.<unit-id><event-in

dex> fcConnUnitEventType.<unit-id><event-index> Where unit-id is the WWN of the switch with 8

zeros appended for a total length of 16. Example: 1.2.3.4.5.6.7.8.0.0.0.0.0.0.0.0

4 1.3.6.1.2.1.8888.1.1.7.1.7.<unit-d><event-in

dex> fcConnUnitEventDescr.<unit-id><event-index> Where unit-id is the WWN of the switch, with 8

zeros appended, for a total length of 16. Example: 1.2.3.4.5.6.7.8.0.0.0.0.0.0.0.0

See definition for “FcConnUnitEventType” on page 111.

The value of this variable is the OID for fcConnUnitId:

1.3.6.1.2.1.8888.1.1.3.1.1.<unitid>

Where unit-id is the WWN of the switch, with 8 zeros appended, for a total length of 16. Example:

1.2.3.4.5.6.7.8.0.0.0.0.0.0.0.0

Event description string with a maximum length of 80 characters. This string will contain a numeric event code and other values describing the specific event.

29SNMP Reference for Directors and Edge Switches

SNMP Support

FA MIB Sensor Trap

This trap is generated whenever a status change occurs for a fan or power supply FRU. There is one variable binding.

Binding OID Value

1 1.3.6.1.2.1.8888.1.1.5.1.3.<unit-id>.<sensor-index>

fcConnUnitSensorStatus.<unit-id>.<sensor-index> Where unit-id is the WWN of the switch, with 8 zeros

appended, for a total length of 16. Example:

1.2.3.4.5.6.7.8.0.0.0.0.0.0.0.0 And where sensor-index refers to the FRU in the sensor

table which has changed state. For example if sensor-index was 5, you could look at the 5 the sensor table to determine which FRU was affected.

entry in

See description for “FcConnUnitSensorStatus” on page 96.

FA MIB Port Status Change Trap

This trap occurs whenever a port status change occurs. There are two variable bindings.

Binding OID Value

1 1.3.6.1.2.1.8888.1.1.6.1.6.<port-index>

fcConnUnitPortStatus.<port-index> Where port-index is the port number

normalized to the range 1-140.

2 1.3.6.1.2.1.8888.1.1.6.1.5.<port-index>

fcConnUnitPortState.<port-index> Where port-index is the port number

normalized to the range 1-140.

See definition for “FcConnUnitPortStatus” on page 101.

Example

Interpretation of trap information from HP OpenView The output from HP OpenView for a series of traps is shown below:

- Minor Thu May 02 09:29:30 10.235.4.111 NO TRAPD.CONF FMT FOR .1.3.6.1.2.1.8888.0.1 ARGS(2): [1] mgmt.mib-2.fcMgmtMIB.fcMgmtObjects.fcMgmtConfig.fcC onnUnitTable.fcConnUnitEntry.fcConnUnitStatus.3.2.0 .0.0.0.0.0.0.0.0.0.0.0.0.0 (Integer): ok [2]

30 SNMP Reference for Directors and Edge Switches

+ 173 hidden pages