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 534

vacmViewTreeFamilyEntry, Sequence, Syntax

View all HP StorageWorks 2/140 manuals

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

Page 534 highlights

SNMPv3 MIB G Sequence object instance is not in the MIB view. If one or more match, then the object instance is included in, or excluded from, the MIB view according to the value of vacmViewTreeFamilyType in the entry whose value of vacmViewTreeFamilySubtree has the most sub-identifiers. If multiple entries match and have the same number of sub-identifiers (when wildcarding is specified with the value of vacmViewTreeFamilyMask), then the lexicographically greatest instance of vacmViewTreeFamilyType determines the inclusion or exclusion. An object instance's OBJECT IDENTIFIER X matches an active entry in this table when the number of sub-identifiers in X is at least as many as in the value of vacmViewTreeFamilySubtree for the entry, and each sub-identifier in the value of vacmViewTreeFamilySubtree matches its corresponding sub-identifier in X. Two sub-identifiers match either if the corresponding bit of the value of vacmViewTreeFamilyMask for the entry is zero (the 'wild card' value), or if they are equal. A 'family' of subtrees is the set of subtrees defined by a particular combination of values of vacmViewTreeFamilySubtree and vacmViewTreeFamilyMask. In the case where no 'wild card' is defined in the vacmViewTreeFamilyMask, the family of subtrees reduces to a single subtree. When creating or changing MIB views, an SNMP Command Generator application should utilize the vacmViewSpinLock to try to avoid collisions. See DESCRIPTION clause of vacmViewSpinLock. When creating MIB views, it is strongly advised that first the 'excluded' vacmViewTreeFamilyEntries are created and then the 'included' entries. When deleting MIB views, it is strongly advised that first the 'included' vacmViewTreeFamilyEntries are deleted and then the 'excluded' entries. If a create for an entry for instance-level access control is received and the implementation does not support instance-level granularity, then an inconsistentName error must be returned. ::= { vacmMIBViews 2 } vacmViewTreeFamilyEntry Syntax VacmViewTreeFamilyEntry G-34 E/OS SNMP Support Manual

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

G-34

E/OS SNMP Support Manual

SNMPv3 MIB

object instance is not in the MIB view.

If one or more match, then the

object instance is included in, or excluded from, the MIB view

according to the value of vacmViewTreeFamilyType in the entry

whose value of vacmViewTreeFamilySubtree has the most

sub-identifiers.

If multiple entries match and have the same number

of sub-identifiers (when wildcarding is specified with the value of

vacmViewTreeFamilyMask), then the lexicographically greatest

instance of vacmViewTreeFamilyType determines the inclusion or

exclusion.

An object instance's OBJECT IDENTIFIER X matches an active entry

in this table when the number of sub-identifiers in X is at least as

many as in the value of vacmViewTreeFamilySubtree for the entry,

and each sub-identifier in the value of vacmViewTreeFamilySubtree

matches its corresponding sub-identifier in X.

Two sub-identifiers

match either if the corresponding bit of the value of

vacmViewTreeFamilyMask for the entry is zero (the 'wild card'

value), or if they are equal.

A 'family' of subtrees is the set of subtrees defined by a particular

combination of values of vacmViewTreeFamilySubtree and

vacmViewTreeFamilyMask. In the case where no 'wild card' is

defined in the vacmViewTreeFamilyMask, the family of subtrees

reduces to a single subtree.

When creating or changing MIB views, an SNMP Command

Generator application should utilize the vacmViewSpinLock to try to

avoid collisions. See DESCRIPTION clause of vacmViewSpinLock.

When creating MIB views, it is strongly advised that first the

'excluded' vacmViewTreeFamilyEntries are created and then the

'included' entries.

When deleting MIB views, it is strongly advised that first the

'included' vacmViewTreeFamilyEntries are deleted and then the

'excluded' entries.

If a create for an entry for instance-level access control is received and

the implementation does not support instance-level granularity, then

an inconsistentName error must be returned.

Sequence

::= { vacmMIBViews 2 }

vacmViewTreeFamilyEntry

Syntax

VacmViewTreeFamilyEntry