ipForwardFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"When this MIB is implemented for read-create, the
implementation can claim full compliance.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT inetCidrRouteDestType
-- SYNTAX InetAddressType (ipv4(1), ipv6(2),
-- ipv4z(3), ipv6z(4))
-- DESCRIPTION
-- This MIB requires support for global and
-- non-global ipv4 and ipv6 addresses.
--
-- OBJECT inetCidrRouteDest
-- SYNTAX InetAddress (SIZE (4 | 8 | 16 | 20))
-- DESCRIPTION
-- This MIB requires support for global and
-- non-global IPv4 and IPv6 addresses.
--
-- OBJECT inetCidrRouteNextHopType
-- SYNTAX InetAddressType (unknown(0), ipv4(1),
-- ipv6(2), ipv4z(3)
-- ipv6z(4))
-- DESCRIPTION
-- This MIB requires support for global and
-- non-global ipv4 and ipv6 addresses.
--
-- OBJECT inetCidrRouteNextHop
-- SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20))
-- DESCRIPTION
-- This MIB requires support for global and
-- non-global IPv4 and IPv6 addresses.
"
MODULE -- this module
MANDATORY-GROUPS { inetForwardCidrRouteGroup }
OBJECT inetCidrRouteStatus
SYNTAX RowStatus { active(1), notInService (2) }
WRITE-SYNTAX RowStatus { active(1), notInService (2),
createAndGo(4), destroy(6) }
DESCRIPTION "Support for createAndWait is not required."
View at oid-info.com
The compliance statement for systems which have routing
tables. XXX is this right?
Parsed from file IP-FORWARD-MIB.mib.txt
Company: None
Module: IP-FORWARD-MIB
When this MIB is implemented for read-create, the
implementation can claim full compliance.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
Parsed from file IP-FORWARD-MIB.mib
Module: IP-FORWARD-MIB
Automatically extracted from RFC4292
ipForwardCompliance2 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for systems which have routing tables. XXX is this right?" MODULE MANDATORY-GROUPS { inetForwardCidrRouteGroup } ::= { ipForwardCompliances 3 }
ipForwardFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB is implemented for read-create, the implementation can claim full compliance. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: " MODULE MANDATORY-GROUPS { inetForwardCidrRouteGroup } OBJECT inetCidrRouteStatus SYNTAX RowStatus { active(1), notInService (2) } WRITE-SYNTAX RowStatus { active(1), notInService (2), createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait is not required." ::= { ipForwardCompliances 3 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.4.24.5.2.1 | ipForwardCompliance | 0 | 0 | The compliance statement for SNMPv2 entities which implement the ipForward MIB. |
| 1.3.6.1.2.1.4.24.5.2.2 | ipForwardOldCompliance | 0 | 0 | The compliance statement for SNMP entities that implement the ipForward MIB. |
| 1.3.6.1.2.1.4.24.5.2.4 | ipForwardReadOnlyCompliance | 0 | 0 | When this MIB is implemented without support for read- create (i.e., in read-only mode), the implementation can claim read-only c… |