|
ENTITY-MIB::entLogicalCommunity (1.3.6.1.2.1.47.1.2.1.1.4) is defined as:
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 may also return a community string based on the
privileges of the request used to read this object. Note
that an agent may 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 which allows more
privileges than the community string used to access this
object.
A compliant SNMP agent may wish 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' may 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 via SNMPv1 or SNMPv2C, the value
of this object is the empty string. This object may also
contain an empty string if a community string has not yet
been assigned by the agent, or no community string with
suitable access rights can be returned for a particular SNMP
request.
Note that this object is deprecated. Agents which implement
SNMPv3 access should use the entLogicalContextEngineID and
entLogicalContextName objects to identify the context
associated with each logical entity. SNMPv3 agents may
return a zero-length string for this object, or may continue
to return a community string (e.g., tri-lingual agent
support).
so an:
snmpwalk -v 1 -c 'community' hostname .1.3.6.1.2.1.47.1.2.1.1.4
should return all supported community-indexes on complient devices (mostly cisco).
cheers,
--
Alfred Reibenschuh
INFORMATIONSTECHNOLOGIE AUSTRIA GMBH
Netzwerk-Management
A-1020 Wien, Lassallestrasse 5
T: ++43-1-21717-58947
F: ++43-1-21717-58979
E: alfred.reibenschuh AT it-austria DOT com
W: http://www.it-austria.com
------------------------------------------
> -----Original Message-----
> From: Jane Curry [mailto:jane.curry AT skills-1st.co DOT uk]
> Sent: Tuesday, November 22, 2005 8:27 PM
> To: nv-l AT lists.us.ibm DOT com
> Subject: RE: [nv-l] ITSA and 6509
>
>
> Thanks Alfred,
> The OID for the switch part of the 6509, 1.3.6.1.4.1.9.1.283
> , is in the
> l2_oids.cfg file - it seems to be in that and NetView's
> oid_to_type file
> by default.
>
> Not sure what syntax you are suggesting below for the
> ENTITY-MIB snmpwalk
> - could you give me a few more clues....
>
> Cheers,
> Jane
>
> >> Also not sure whether these 6509s support Community String Indexing
> >> (CSI)?? I have tried snmpwalk commands with a "-c
> >> <community@VLAN>" but
> >> not got any responses so I am guessing that they don't play
> >> at CSI?? If
> >> anyone has any good examples of configuring for CSI, I would
> >> love a quick
> >> example.
> >
> > try to snmpwalk: ENTITY-MIB::entLogicalCommunity
> >
> > --
> > Alfred Reibenschuh
> > INFORMATIONSTECHNOLOGIE AUSTRIA GMBH
> > Netzwerk-Management
> > A-1020 Wien, Lassallestrasse 5
> > T: ++43-1-21717-58947
> > F: ++43-1-21717-58979
> > E: alfred.reibenschuh AT it-austria DOT com
> > W: http://www.it-austria.com
> > ------------------------------------------
> >
> >
> >
>
>
> --
> Tivoli Certified Consultant & Instructor
> Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
> Tel: +44 (0) 1628 782565
> Coptright (c) 2004 Jane Curry jane.curry AT skills-1st.co DOT uk . All rights
> reserved.
>
| 