HP StorageWorks 2/16V Brocade Fabric OS MIB Reference - Supporting Fabric OS 5 - Page 125

entLogicalIndex 1.3.6.1.2.1.47.1.2.1.1.1

Get HP StorageWorks 2/16V - SAN Switch PDF manuals and user guides View all HP StorageWorks 2/16V manuals
Add to My Manuals
Save this manual to your list of manuals

Page 125 highlights

entLogicalEntry 1.3.6.1.2.1.47.1.2.1.1 4 entLogicalEntry 1.3.6.1.2.1.47.1.2.1.1 Index Information about a particular logical entity. Entities might be managed by this agent or other SNMP agents in the same chassis. entLogicalIndex entLogicalIndex 1.3.6.1.2.1.47.1.2.1.1.1 The value of this object uniquely identifies the logical entity. The value should be a small positive integer; index values for different logical entities are not necessarily contiguous. entLogicalDescr 1.3.6.1.2.1.47.1.2.1.1.2 A textual description of the logical entity. This object should contain a string that identifies the manufacturer's name for the logical entity and should be set to a distinct value for each version of the logical entity. entLogicalType 1.3.6.1.2.1.47.1.2.1.1.3 An indication of the type of logical entity. This is typically the Object Identifier name of the node in the SMI's naming hierarchy that represents the major MIB module, or the majority of the MIB modules, supported by the logical entity. • a logical entity of a regular host/router -> mib-2 • a logical entity of a 802.1d bridge -> dot1dBridge • a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt If an appropriate node in the SMI's naming hierarchy cannot be identified, the value mib-2 should be used. entLogicalCommunity 1.3.6.1.2.1.47.1.2.1.1.4 An SNMPv1 or SNMPv2C community string, which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and might also return a community string based on the privileges of the request used to read this object. Note that an agent might return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string that allows more privileges than the community string used to access this object. A compliant SNMP agent might want to conserve naming scopes by representing multiple logical entities in a single default naming scope. This is possible when the logical entities represented by the same value of entLogicalCommunity have no object instances in common. For example, "bridge1" and "repeater1" might be part of the main naming scope, but at least one additional community string is needed to represent "bridge2" and "repeater2." Logical entities "bridge1" and "repeater1" would be represented by sysOREntries associated with the default naming scope. Fabric OS MIB Reference 109 53-1000439-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
Fabric OS MIB Reference
109
53-1000439-01
entLogicalEntry 1.3.6.1.2.1.47.1.2.1.1
4
entLogicalEntry 1.3.6.1.2.1.47.1.2.1.1
Information about a particular logical entity.
Entities might be managed by this agent or other
SNMP agents in the same chassis.
Index
entLogicalIndex
entLogicalIndex 1.3.6.1.2.1.47.1.2.1.1.1
The value of this object uniquely identifies the logical entity. The value should be a small positive
integer; index values for different logical entities are not necessarily contiguous.
entLogicalDescr 1.3.6.1.2.1.47.1.2.1.1.2
A textual description of the logical entity.
This object should contain a string that identifies the
manufacturer’s name for the logical entity and should be set to a distinct value for each version of
the logical entity.
entLogicalType 1.3.6.1.2.1.47.1.2.1.1.3
An indication of the type of logical entity.
This is typically the Object Identifier name of the node in
the SMI’s naming hierarchy that represents the major MIB module, or the majority of the MIB
modules, supported by the logical entity.
•
a logical entity of a regular host/router -> mib-2
•
a logical entity of a 802.1d bridge -> dot1dBridge
•
a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt
If an appropriate node in the SMI’s naming hierarchy cannot be identified, the value mib-2 should
be used.
entLogicalCommunity 1.3.6.1.2.1.47.1.2.1.1.4
An SNMPv1 or SNMPv2C community string, which can be used to access detailed management
information for this logical entity.
The agent should allow read access with this community string
(to an appropriate subset of all managed objects) and might also return a community string based
on the privileges of the request used to read this object.
Note that an agent might return a community string with read-only privileges, even if this object is
accessed with a read-write community string. However, the agent must take care not to return a
community string that allows more privileges than the community string used to access this object.
A compliant SNMP agent might want to conserve naming scopes by representing multiple logical
entities in a single default naming scope.
This is possible when the logical entities represented by
the same value of entLogicalCommunity have no object instances in common.
For example,
“bridge1” and “repeater1” might be part of the main naming scope, but at least one additional
community string is needed to represent “bridge2” and “repeater2.”
Logical entities “bridge1” and “repeater1” would be represented by sysOREntries associated with
the default naming scope.