Compliance |
RFC 4292
Switch families indicted in the Abstract section of the Basic Operations Guide enjoy full conformance of the RFC 4292.
RFC defines a portion of the Management Information Base (MIB) for use in managing objects related to the forwarding of Internet Protocol (IP) packets in an IP version-independent manner. It is to be noted that the MIB definition described herein does not support multiple instances based on the same address family type. However, it does support an instance of the MIB per address family.
RFC 4292 supported operations
Both GET and SET operations are now supported on switches. RFC 4292 is supported in the following ways:
The set operation can create IPv4 and IPv6 static routes which include the functions for Reject, Remote, and Blackhole.
A column of any existing row with RowStatus “Active” will not be allowed for modification.
Rowstatus will not support “Create-and-wait”.
There is an existing HPE proprietary MIB,
hpicfIpStaticRouteTable, which is used to configure IPv4 and IPv6 static routes. Currently CLI commands use this proprietary MIB for configuration. This will remain unchanged.The SET functions for
inetCidrRouteTable(k_test, k_ready, k_setDefaults and k_set) are implemented. The implementation maps to the existing SET routines ofhpicfIpStaticRouteTablewith the necessary changes. Index ofInetCidrRouteTablehasRoutePolicywhereashpicfIpStaticRouteTablehasIfIndex. Both MIBs have 6 objects as index.The current GET implementation of
inetCidrRouteTableis directly accessing the Gated Routing table to retrieve all the routes which include Static and Dynamic. The SET routines will have to go through thehpicfIpStaticRouteTableSET functions as these routes are of type Static.Creation, modification, or deletion of Dynamic route entry is not allowed. This can be achieved by validating the MIB column
inetCidrRouteProtofor Static or Dynamic protocol.gateD(routing stack) does not discard any routes, so the value of
inetCidrRouteDiscardsMIB will always be 0.
RFC 4292 MIB operations
To make the switch software fully compliant to RFC 4292, both GET and SET operations are supported as indicated in the table below.
GET and SET operations
| inetCidrRouteTable | Type | Access |
|---|---|---|
| inetCidrRouteDestType* | InetAddressType, |
Not-accessible |
| inetCidrRouteDest* | InetAddress, |
Not-accessible |
| inetCidrRoutePfxLen* | InetAddressPrefixLength, |
Not-accessible |
| inetCidrRoutePolicy* | OBJECT IDENTIFIER, |
Not-accessible |
| inetCidrRouteNextHopType* | InetAddressType, |
Not-accessible |
| inetCidrRouteNextHop* | InetAddress |
Not-accessible |
| inetCidrRouteIfIndex | InterfaceIndexOrZero, |
Read-Create |
| inetCidrRouteType | INTEGER, |
Read-Create |
| inetCidrRouteProto | IANAipRouteProtocol, |
Read-Only |
| inetCidrRouteAge | Gauge32, |
Read-Only |
| inetCidrRouteNextHopAS | InetAutonomousSystemNumber, |
Read-Create |
| inetCidrRouteMetric1 | Integer32, |
Read-Create |
| inetCidrRouteMetric2 | Integer32, |
Read-Create |
| inetCidrRouteMetric3 | Integer32, |
Read-Create |
| inetCidrRouteMetric4 | Integer32, |
Read-Create |
| inetCidrRouteMetric5 | Integer32, |
Read-Create |
| inetCidrRouteStatus | RowStatus |
Read-Create |
* INDEX OBJECTS |