The router implementation of the RFC 1657 MIB variables listed in Table: SR OS and IETF MIB variations differs from the IETF MIB specification.
| MIB variable | Description | RFC 1657 allowed values | SR OS allowed Values |
|---|---|---|---|
bgpPeerMinRouteAdvertisementInterval |
Time interval in seconds for the MinRouteAdvertisementInterval timer. The suggested value for this timer is 30. |
1 to 65535 |
1 to 255 A value of 0 is supported when the rapid-update command is applied to an address family that supports it. |
If SNMP is used to set a value of X to the MIB variable in Table: SR OS and IETF MIB variations , there are three possible results:
| Condition | Result |
|---|---|
X is within IETF MIB values and X is within SR OS values |
SNMP set operation does not return an error MIB variable set to X |
X is within IETF MIB values and X is outside SR OS values |
SNMP set operation does not return an error MIB variable set to ‟nearest” SR OS supported value (for example, SR OS range is 2 - 255 and X = 65535, MIB variable is set to 255) Log message generated |
X is outside IETF MIB values and X is outside SR OS values |
SNMP set operation returns an error |
When the value set using SNMP is within the IETF allowed values and outside the SR OS values as specified in Table: SR OS and IETF MIB variations and Table: MIB variable with SNMP , a log message is generated.
The log messages that display are similar to the following log messages:
Sample Log Message for setting bgpPeerMinRouteAdvertisementInterval to 256
535 2006/11/12 19:40:53 [Snmpd] BGP-4-bgpVariableRangeViolation: Trying to set
bgpPeerMinRouteAdvInt to 256 - valid range is [2-255] - setting to 255
Sample Log Message for setting bgpPeerMinRouteAdvertisementInterval to 1
566 2006/11/12 19:44:41 [Snmpd] BGP-4-bgpVariableRangeViolation: Trying to set
bgpPeerMinRouteAdvInt to 1 - valid range is [2-255] - setting to 2