Description: Administrative control and status of a protocol on a router.

The following values can be read from this object: active(1) - Indicates that the protocol on the designated router is created, configured, and running. notReady(3) - Indicates that the protocol requires additional configuration in a protocol specific MIB module. Examples include the BGP and OSPF protocols, which require additional configuration of protocol specific parameters such as: Autonomous System (AS) for BGP, and Process Id for OSPF. destroy(6) - The destroy(3) operation can fail if there are executing applications dependent on the protocol. If an attempt is made to destroy(6) an active(1) protocol that other applications are dependent on, the rowStatus will read destroy(6). Normally, when a row is destroyed, the agent will cleaup and remove the entry.

The following values can be written to this object: active(1) - Activate protocol on the designated router. createAndGo(4) - Create protocol on designated router. The router indicated by usdRouterProtocolRouterIndex must already exist in the usdRouterTable. The value of the usdRouterProtocolProtocolIndex must be from the set of protocol values defined by the UsdRouterProtocolIndex type. destroy(6) - Destroy protocol on designated router. If the operation is successful, the agent will remove the entry. If the operation failed, the row will remain in the table with a rowStatus value of destroy(6).

Conditions on destroy(6): 1) The default router can not be deleted. 2) The local router can not be deleted. A local router is defined as the router that sourced the SNMP request.

Upon creation of a router in the usdRouterTable, some protocol entries will appear in this table by default, which indicates that these protocols are created by the action of creating a router. It is important to note, that this behavior may change over time by protocol type.