Home » HP Manuals » Storage Devices » HP StorageWorks 2/140 » Manual Viewer

HP StorageWorks 2/140 FW 08.01.00 McDATA E/OS SNMP Support Manual (620-000131- - Page 19

Standard MIBs

View all HP StorageWorks 2/140 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 19 highlights

Standard MIBs Introduction to SNMP 1 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 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 Network Management using SNMP 1-7

Section	Page
Cover	1
Preface	7
Introduction to SNMP	13
Network Management using SNMP	13
SNMP Features	14
SNMP Commands	14
Why Variables exist In a Managed Device	15
How SNMP Changes Variables in a Managed Device	15
SNMPv3	16
SNMP Community co-existence	17
Security Features	17
E/OS SNMPv3 Configuration	18
Standard MIBs	19
Private Enterprise MIBs	20
Traps and Their Purpose	21
McDATA SNMP Support	23
Overview	23
E/OS Trap Overview	24
E/OS Trap summary table	25
MIB Definitions: MIB-II	42
System Group	42
Interfaces Group	44
Address Translation Group	51
IP Group	52
IP Routing group	58
ICMP Group	64
TCP Group	69
UDP Group	74
SNMP Group	75
Fabric Element Management MIB	82
Predefined types	82
Fibre Alliance MIB	118
Type definitions	118
Trap Types	168
Fibre Alliance MIB	171
FA MIB	171
Textual conventions for this MIB	174
Connectivity unit group	176
Event group	204
SNMP trap registration group	235
Related traps	238
Conformance definitions	239
Conformance units	240
FC Management MIB	249
FCMGMT-MIB Definitions	249
Connectivity unit group	252
Sensor table	267
Port Table	271
Event Group	283
Link Table	287
Port Statistics	294
FC Simple Name Server Table	312
SNMP Trap Registration Group	317
Related Traps	321
McDATA Private Enterprise MIB	325
FCEOS.MIB	325
Textual conventions for this MIB	327
Enterprise Specific Object Identifiers	329
Fibre Channel product lines	329
Groups in FCEOS MIB	329
System Group	330
Fibre Channel FRU Group	334
Fibre Channel Port Group	337
NPIV Information	363
Fibre Channel Zoning Group	366
Fibre Channel Threshold Alert Group	371
FCEOS Enterprise-specific Trap Definitions	375
Fabric Element Management MIB	381
FCFE.MIB	381
Configuration group	386
Operation group	398
F_Port Fabric Login table	401
FxPort Fabric Login table	405
Error group	410
Accounting Groups	415
Class 2 Accounting table	420
Class 3 Accounting Group	423
Capability Group	426
MIB II	433
Groups in MIB II	433
System group	434
Interfaces group	437
Address Translation group	446
IP group	448
ICMP group	465
TCP group	472
SNMP group	482
SNMP Framework MIB	491
SNMP Framework MIB	491
Textual Conventions	492
The snmpEngine Group	497
SNMPv3 MIB	501
SNMPv3 MIB	501
User based SM MIB	501
SNMP View Based Acm MIB Definitions	521
MIB views	532
SNMP-COMMUNITY-MIB	540
MIB Objects Listing	551
MIB Objects Listed by OID	551
MIB Objects Listed Alphabetically	595
MIB Objects Listed Alphabetically	632

Match case Limit results 1 per page

Network Management using SNMP

1-7

Introduction to SNMP

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:

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.

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.

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.

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