HP StorageWorks 2/64 HP StorageWorks Fabric OS 5.x MIB Reference Guide (AA-RVH - Page 124

entLogicalCommunity, entLogicalTAddress, entLogicalTDomain

Page 124 highlights

entLogicalCommunity OID 1.3.6.1.2.1.47.1.2.1.1.4 Description 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. For agents not accessible through SNMPvl or SNMPv2C, the value of this object is the empty string. This object might also contain an empty string if a community string has not yet been assigned by the agent; otherwise, no community string with suitable access rights can be returned for a particular SNMP request. Note that this object is deprecated. Agents that implement SNMPv3 access should use the entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical entity. SNMPv3 agents might return a zero-length string for this object or might continue to return a community string (for example, tri-lingual agent support). entLogicalTAddress OID Description 1.3.6.1.2.1.47.1.2.1.1.5 The transport service address by which the logical entity receives network management traffic, formatted according to the corresponding value of entLogicalTDomain. For snmpUDPDomain, a TAddress is 6 octets long, the initial 4 octets containing the IP-address in network-byte order and the last 2 containing the UDP port in network-byte order. Consult Transport Mappings for Version 2 of the Simple Network Management Protocol (RFC1906) for further information on snmpUDPDomain. entLogicalTDomain OID Description 1.3.6.1.2.1.47.1.2.1.1.6 Indicates the kind of transport service by which the logical entity receives network management traffic. Possible values for this object are currently found in the Transport Mappings for SNMPv2 document (RFC1906). 124 Entity MIB objects

  • 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

124
Entity MIB objects
entLogicalCommunity
OID
1.3.6.1.2.1.47.1.2.1.1.4
Description
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.
For agents not accessible through SNMPvl or SNMPv2C, the value of this object is the
empty string. This object might also contain an empty string if a community string has not
yet been assigned by the agent; otherwise, no community string with suitable access
rights can be returned for a particular SNMP request.
Note that this object is deprecated. Agents that implement SNMPv3 access should use the
entLogicalContextEngineID and entLogicalContextName objects to identify the context
associated with each logical entity. SNMPv3 agents might return a zero-length string for
this object or might continue to return a community string (for example, tri-lingual agent
support).
entLogicalTAddress
OID
1.3.6.1.2.1.47.1.2.1.1.5
Description
The transport service address by which the logical entity receives network management
traffic, formatted according to the corresponding value of entLogicalTDomain.
For snmpUDPDomain, a TAddress is 6 octets long, the initial 4 octets containing the
IP-address in network-byte order and the last 2 containing the UDP port in network-byte
order. Consult
Transport Mappings for Version 2 of the Simple Network Management
Protocol
(RFC1906) for further information on snmpUDPDomain.
entLogicalTDomain
OID
1.3.6.1.2.1.47.1.2.1.1.6
Description
Indicates the kind of transport service by which the logical entity receives network
management traffic. Possible values for this object are currently found in the
Transport
Mappings for SNMPv2
document (RFC1906).