OID reference
1.3.6.1.4.1.248.15.4.99.2.1.3
The compliance statement for routers running PIM Dense Mode and implementing the PIM MIB.
Identification
{1 3 6 1 4 1 248 15 4 99 2 1 3}
Available source records contain 2 distinct definitions; some records may not include a definition.
hmPIMDenseV2MIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for routers running PIM Dense Mode
and implementing the PIM MIB."
MODULE -- this module
MANDATORY-GROUPS { hmPIMDenseV2MIBGroup }
OBJECT hmPIMInterfaceStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { hmPIMMIBCompliances 3 }hmPIMDenseV2MIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for routers running PIM Dense Mode
and implementing the PIM MIB."
MODULE -- this module
MANDATORY-GROUPS { hmPIMDenseV2MIBGroup }
OBJECT hmPIMInterfaceStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { hmPIMMIBCompliances 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The compliance statement for routers running PIM Dense Mode and implementing the PIM MIB.
Belden, GarrettCom and Hirschmann IT official standalone MIBsHirschmann MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: hmPIMDenseV2MIBCompliance
{
"smi_kind": "MODULE-COMPLIANCE",
"definition": [
"hmPIMDenseV2MIBCompliance",
"MODULE-COMPLIANCE",
"STATUS",
"current",
"DESCRIPTION",
"\"The compliance statement for routers running PIM Dense Mode and implementing the PIM MIB.\"",
"MODULE",
"MANDATORY-GROUPS",
"{",
"hmPIMDenseV2MIBGroup",
"}",
"OBJECT",
"hmPIMInterfaceStatus",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"Write access is not required.\"",
"::=",
"{",
"hmPIMMIBCompliances",
"3",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"The compliance statement for routers running PIM Dense Mode and implementing the PIM MIB."
],
null,
[
"ComplianceModules",
[
[
null,
[
"hmPIMDenseV2MIBGroup"
]
]
]
]
]
}Vendor MIB copy from the Observium Community archive. Hirschmann support.
Module: HIRSCHMANN-PIM-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'IpAddress', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'IPMROUTE-STD-MIB': ['ipMRouteGroup', 'ipMRouteSource', 'ipMRouteSourceMask', 'ipMRouteNextHopGroup', 'ipMRouteNextHopSource', 'ipMRouteNextHopSourceMask', 'ipMRouteNextHopIfIndex', 'ipMRouteNextHopAddress'], 'HIRSCHMANN-MULTICAST-MIB': ['hmPlatform4Multicast']}Related source files and packages:
Vendor MIB copy from the Netdisco archive.
Module: HIRSCHMANN-PIM-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'IpAddress', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'IPMROUTE-STD-MIB': ['ipMRouteGroup', 'ipMRouteSource', 'ipMRouteSourceMask', 'ipMRouteNextHopGroup', 'ipMRouteNextHopSource', 'ipMRouteNextHopSourceMask', 'ipMRouteNextHopIfIndex', 'ipMRouteNextHopAddress'], 'HIRSCHMANN-MULTICAST-MIB': ['hmPlatform4Multicast']}Related source files and packages:
Module: HIRSCHMANN-PIM-MIB
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'IpAddress', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'IPMROUTE-STD-MIB': ['ipMRouteGroup', 'ipMRouteSource', 'ipMRouteSourceMask', 'ipMRouteNextHopGroup', 'ipMRouteNextHopSource', 'ipMRouteNextHopSourceMask', 'ipMRouteNextHopIfIndex', 'ipMRouteNextHopAddress'], 'HIRSCHMANN-MULTICAST-MIB': ['hmPlatform4Multicast']}Same file in 069Qp00000juIrZIAU.
Same file in 069Qp00000juETAIA2.
Same file in 069Qp00000juDgfIAE.
Same file in 069Qp00000juDbrIAE.
Module: HIRSCHMANN-PIM-MIB
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'IpAddress', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'IPMROUTE-STD-MIB': ['ipMRouteGroup', 'ipMRouteSource', 'ipMRouteSourceMask', 'ipMRouteNextHopGroup', 'ipMRouteNextHopSource', 'ipMRouteNextHopSourceMask', 'ipMRouteNextHopIfIndex', 'ipMRouteNextHopAddress'], 'HIRSCHMANN-MULTICAST-MIB': ['hmPlatform4Multicast']}Module: HIRSCHMANN-PIM-MIB
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'IpAddress', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'IPMROUTE-STD-MIB': ['ipMRouteGroup', 'ipMRouteSource', 'ipMRouteSourceMask', 'ipMRouteNextHopGroup', 'ipMRouteNextHopSource', 'ipMRouteNextHopSourceMask', 'ipMRouteNextHopIfIndex', 'ipMRouteNextHopAddress'], 'HIRSCHMANN-MULTICAST-MIB': ['hmPlatform4Multicast']}Module: HIRSCHMANN-PIM-MIB
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'IpAddress', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'IPMROUTE-STD-MIB': ['ipMRouteGroup', 'ipMRouteSource', 'ipMRouteSourceMask', 'ipMRouteNextHopGroup', 'ipMRouteNextHopSource', 'ipMRouteNextHopSourceMask', 'ipMRouteNextHopIfIndex', 'ipMRouteNextHopAddress'], 'HIRSCHMANN-MULTICAST-MIB': ['hmPlatform4Multicast']}Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.248.15.4.99.2.1.1 | hmPIMV1MIBCompliance | 0 | 0 | |
| 1.3.6.1.4.1.248.15.4.99.2.1.2 | hmPIMSparseV2MIBCompliance | 0 | 0 |