CISCO-DEVICE-LOCATION-MIB
This MIB is used for managing location information
of end point devices(Telepresence, IP Camera, Digital media
player etc) connected to switches/routers.
This location information is then carried from the switch/router
to the end point via Cisco Discovery protocol (CDP) or
Link Layer Discovery protocol (LLDP).
The location information can be used by applications such as
Cisco Video Surveillance Manager, digital media manager.
Civic location information as described in RFC 4676, identifies
the exact location information like state, city, building,
floor that helps identify the exact location of the devices.
Definitions:
============
LocationTarget: This is identified by a target type
(interface, IP session) and target identifier
(ifIndex, IP address).
MIB Table Overview:
===================
This MIB consists of five tables:
1) cdlLocationTable
2) cdlCivicAddrLocationTable
3) cdlCustomLocationTable
4) cdlGeoLocationTable
5) cdlLocationPreferWeightTable
The cdlLocationTable provides information about
location information of LocationTarget.
cdlCivicAddrLocationTable provides the
details about the civic address types like state,
county, city for a given LocationTarget.
cdlCustomLocationTable provides the ability to
associate arbitrary name/value pairs with a
LocationTarget. This allows for specification of
information which is not currently included into the
standard definition of Civic address types.
cdlGeoLocationTable provides Geolocation (GPS)
coordinate information for a LocationType.
cdlLocationPreferWeightTable provides information about,
and a method for configuring, the order in which
the system makes use of location information which is
provided by different sources.
The following provides a sample view of
the contents of the table and the relationship
between them.
cdlLocationTable
------------------------------------------------
Location Sub Country Target Target
Index TypeCap Code Type Identifier
-------------------------------------------------
- 1 Civic Addr 01 Interface 1
| 2 Civic Addr 01 Interface 2
|
|
| cdlCivicAddrLocationTable
| ----------------------------------------
| Location Location Location
| Index Type Index Value
| -----------------------------------------
|_ _ _ _ 1 1 - State Karnataka
|_ _ _ _ 1 2 - County Bangalore District
|_ _ _ _ 1 3 - city Bangalore
2 1 - State Kerala
2 2 - County Waynad District
2 3 - city Waynad
- Source file
CISCO-DEVICE-LOCATION-MIB- Last revised
- Identity
ciscoDeviceLocationMIB- Base OID
1.3.6.1.4.1.9.9.732
Imported Objects
| CISCO-SMI | ciscoMgmt |
| CISCO-TC | CountryCode |
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | RowStatus StorageType |
Net-SNMP examples using the cisco MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-DEVICE-LOCATION-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-DEVICE-LOCATION-MIB::ciscoDeviceLocationMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-DEVICE-LOCATION-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-DEVICE-LOCATION-MIB::ciscoDeviceLocationMIB'
Objects (43)
Showing 43 of 43 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.9.9.732 |
||
.1.3.6.1.4.1.9.9.732.0 |
||
.1.3.6.1.4.1.9.9.732.1 |
||
.1.3.6.1.4.1.9.9.732.1.1 |
||
|
|
OctetString
|
.1.3.6.1.4.1.9.9.732.1.1.1 |
.1.3.6.1.4.1.9.9.732.1.2 |
||
.1.3.6.1.4.1.9.9.732.1.2.1 |
||
.1.3.6.1.4.1.9.9.732.1.2.1.1 |
||
|
Bits
|
.1.3.6.1.4.1.9.9.732.1.2.1.2 |
|
.1.3.6.1.4.1.9.9.732.1.2.1.3 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.732.1.2.1.4 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.732.1.2.1.5 |
|
.1.3.6.1.4.1.9.9.732.1.3 |
||
.1.3.6.1.4.1.9.9.732.1.3.1 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.732.1.3.1.1 |
|
.1.3.6.1.4.1.9.9.732.1.3.1.2 |
||
.1.3.6.1.4.1.9.9.732.1.3.1.3 |
||
.1.3.6.1.4.1.9.9.732.1.3.1.4 |
||
.1.3.6.1.4.1.9.9.732.1.4 |
||
.1.3.6.1.4.1.9.9.732.1.4.1 |
||
|
OctetString
|
.1.3.6.1.4.1.9.9.732.1.4.1.1 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.732.1.4.1.2 |
|
.1.3.6.1.4.1.9.9.732.1.4.1.3 |
||
.1.3.6.1.4.1.9.9.732.1.4.1.4 |
||
.1.3.6.1.4.1.9.9.732.1.5 |
||
.1.3.6.1.4.1.9.9.732.1.5.1 |
||
|
|
OctetString
|
.1.3.6.1.4.1.9.9.732.1.5.1.1 |
|
|
.1.3.6.1.4.1.9.9.732.1.5.1.10 |
|
.1.3.6.1.4.1.9.9.732.1.5.1.2 |
||
|
|
OctetString
|
.1.3.6.1.4.1.9.9.732.1.5.1.3 |
.1.3.6.1.4.1.9.9.732.1.5.1.4 |
||
|
|
OctetString
|
.1.3.6.1.4.1.9.9.732.1.5.1.5 |
|
Enumeration
|
.1.3.6.1.4.1.9.9.732.1.5.1.6 |
|
.1.3.6.1.4.1.9.9.732.1.5.1.7 |
||
|
|
.1.3.6.1.4.1.9.9.732.1.5.1.8 |
|
.1.3.6.1.4.1.9.9.732.1.5.1.9 |
||
.1.3.6.1.4.1.9.9.732.1.6 |
||
.1.3.6.1.4.1.9.9.732.1.6.1 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.732.1.6.1.1 |
|
.1.3.6.1.4.1.9.9.732.1.6.1.2 |
||
.1.3.6.1.4.1.9.9.732.2 |
||
.1.3.6.1.4.1.9.9.732.2.1 |
||
.1.3.6.1.4.1.9.9.732.2.2 |
Dependencies (6) 6 direct Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- CISCO-SMIcisco
- SNMPv2-TCrfc
- CISCO-TCcisco
- SNMPv2-CONFrfc
- SNMP-FRAMEWORK-MIBrfc
- CISCO-DEVICE-LOCATION-MIBciscoselected
Conformance Groups (5)
|
cdlLocationSubTypeCapability cdlLocationCountryCode cdlLocationTargetType cdlLocationTargetIdentifier cdlKey
A collection of location objects.
|
.1.3.6.1.4.1.9.9.732.2.2.1
|
|
|
A collection of civic address location objects.
|
.1.3.6.1.4.1.9.9.732.2.2.2
|
|
|
A collection of Custom location information objects.
|
.1.3.6.1.4.1.9.9.732.2.2.3
|
|
|
cdlGeoLatitude cdlGeoLatitudeResolution cdlGeoLongitude cdlGeoLongitudeResolution cdlGeoAltitude cdlGeoAltitudeType cdlGeoAltitudeResolution cdlGeoResolution cdlGeoStatus cdlGeoStorageType
A collection of Geographic location information objects.
|
.1.3.6.1.4.1.9.9.732.2.2.4
|
|
|
A collection of location source preference objects.
|
.1.3.6.1.4.1.9.9.732.2.2.5
|
Compliance Statements (2)
OID
.1.3.6.1.4.1.9.9.732.2.1.1The compliance statement for entities which implement
the CISCO-DEVICE-LOCATION-MIB.
the CISCO-DEVICE-LOCATION-MIB.
Required groups
| mandatory | cdlLocationGroup | |
| mandatory | cdlCivicAddrLocationGroup |
Object refinements
| Object | Access | Syntax | Description |
|---|---|---|---|
| cdlCivicAddrLocationValue | readonly | An implementation is required to support only read access. |
|
| cdlLocationCountryCode | readonly | An implementation is required to support only read access. |
|
| cdlCivicAddrLocationStatus | readonly | An implementation that is required to support write access would need to support only three of the six enumerated values of the RowStatus textual convention, specifically: 'active', 'createAndGo' and 'destroy'. An implementation that is required to support read only access would need to support only 'active'. |
|
| cdlCivicAddrLocationStorageType | readonly | Write access is not required and 'non-volatile' is the only value supported. |
OID
.1.3.6.1.4.1.9.9.732.2.1.2The compliance statement for entities which implement
the CISCO-DEVICE-LOCATION-MIB.
the CISCO-DEVICE-LOCATION-MIB.
Required groups
| mandatory | cdlLocationGroup | |
| optional | cdlCivicAddrLocationGroup |
This group is optional and, if present, contains standardized Civic Address information. |
| optional | cdlCustomLocationGroup |
This group is optional and, if present, contains Cisco Custom Location information. |
| optional | cdlGeoLocationGroup |
This group is optional and, if present, contains Geographic (GPS) Address information. |
| optional | cdlLocationPreferWeightGroup |
This group is optional and, if present, contains Preference Weight configuration information. |
Object refinements
| Object | Access | Syntax | Description |
|---|---|---|---|
| cdlCivicAddrLocationValue | readonly | An implementation is required to support only read access. |
|
| cdlLocationCountryCode | readonly | An implementation is required to support only read access. |
|
| cdlCivicAddrLocationStatus | readonly | An implementation that is required to support write access would need to support only three of the six enumerated values of the RowStatus textual convention, specifically: 'active', 'createAndGo' and 'destroy'. An implementation that is required to support read only access would need to support only 'active'. |
|
| cdlCivicAddrLocationStorageType | readonly | Write access is not required and 'non-volatile' is the only value supported. |
|
| cdlCustomLocationValue | readonly | An implementation is required to support only read access. |
|
| cdlCustomLocationStatus | readonly | An implementation that is required to support write access would need to support only three of the six enumerated values of the RowStatus textual convention, specifically: 'active', 'createAndGo' and 'destroy'. An implementation that is required to support read only access would need to support only 'active'. |
|
| cdlCustomLocationStorageType | readonly | Write access is not required and 'non-volatile' is the only value supported. |
|
| cdlGeoLatitude | readonly | An implementation is required to support only read access. |
|
| cdlGeoLatitudeResolution | readonly | An implementation is required to support only read access. |
|
| cdlGeoLongitude | readonly | An implementation is required to support only read access. |
|
| cdlGeoLongitudeResolution | readonly | An implementation is required to support only read access. |
|
| cdlGeoAltitude | readonly | An implementation is required to support only read access. |
|
| cdlGeoAltitudeType | readonly | An implementation is required to support only read access. |
|
| cdlGeoAltitudeResolution | readonly | An implementation is required to support only read access. |
|
| cdlGeoResolution | readonly | An implementation is required to support only read access. |
|
| cdlGeoStatus | readonly | An implementation that is required to support write access would need to support only three of the six enumerated values of the RowStatus textual convention, specifically: 'active', 'createAndGo' and 'destroy'. An implementation that is required to support read only access would need to support only 'active'. |
|
| cdlGeoStorageType | readonly | Write access is not required and 'non-volatile' is the only value supported. |
|
| cdlLocationPreferWeightValue | readonly | An implementation is required to support only read access. |