---
oid: "1.3.6.1.4.1.562.2.4.1.40.2.10.1.3"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 562 magellan(2) passport(4) components(1) rtg(40) rtgRs(2) rtgRsSelectedRouteTable(10) rtgRsSelectedRouteEntry(1) rtgRsBumpingPriority(3)}"
description: "rtgRsBumpingPriority OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2017-12-20"
---

## OID : `1.3.6.1.4.1.562.2.4.1.40.2.10.1.3`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 562 magellan(2) passport(4) components(1) rtg(40) rtgRs(2) rtgRsSelectedRouteTable(10) rtgRsSelectedRouteEntry(1) rtgRsBumpingPriority(3)}
```

### Description

```asn1
rtgRsBumpingPriority OBJECT-TYPE
SYNTAX Unsigned32 (0..4)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This attribute indicates the priority at which a route has been
selected, or a value of 4 for manual routes since no route selection
was made. Since RouteSelector does not verify manual routes the
value of 4 for routeBumpingPriority symbolizes an unknown value
for manual routes. The remainder of the description is not
applicable to manual routes.

The bumping priority of a route specifies a priority at which a path
along that route can be established. The lowest bumping priority is
4, the highest bumping priority is equal to a setup priority contained
in the route request data. If a route is selected at bumping priority 4,
then no paths will be bumped since there appears to be enough free
bandwidth on selected trunks, and also since this bumping priority
is not better than the lowest holding priority (4) of any path.

If a route cannot be selected at bumping priority 4 and a setup
priority is 3 or better, then a route may be selected at bumping
priority 3. This means that paths at holding priority 4 may be
bumped if currently there is not enough free bandwidth on selected
trunks to establish the new path with setup priority 3.

If a route cannot be selected at bumping priority 3 and a setup
priority is 2 or better, then a route may be selected at bumping
priority 2. In this case paths with holding priority 4 and 3 may be
bumped if there is not enough free bandwidth on selected trunks to
establish the new path with setup priority 2.

If a route cannot be selected at bumping priority 2 and a setup
priority is 1 or better, then a route may be selected at bumping
priority 1. In this case paths with holding priority 4, 3, and 2 may be
bumped if there is not enough free bandwidth on selected trunks to
establish the new path with setup priority 1.

If a route cannot be selected at bumping priority 1 and a setup
priority is 0, then a route may be selected at bumping priority 0. In
this case paths with holding priority 4, 3, 2, and 1 may be bumped if
there is not enough free bandwidth on selected trunks to establish
the new path with setup priority 0."
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

### Terms of Use
[Terms of use](https://oid-base.com/disclaimer.htm.md)
