tripRouteTypeEntry OBJECT-TYPE
SYNTAX TripRouteTypeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing information about the route type
that a particular TRIP entity supports. Each entry
represents information about either the local or a remote
LS peer. The object tripRouteTypePeer is used to
distinguish this. In the case of a local LS, the
address/port information will reflect the values
configured in tripCfgTable. In the case of a remote
peer, the address/port information will reflect the
values of an entry in the tripPeerTable.
Implementation need to be aware that if the size of
tripRouteTypeAddr exceeds 111 sub-IDs, then OIDs of column
instances in this table will have more than 128 sub-IDs
and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3."
INDEX { applIndex,
tripRouteTypeAddrInetType,
tripRouteTypeAddr,
tripRouteTypePort,
tripRouteTypeProtocolId,
tripRouteTypeAddrFamilyId }
View at oid-info.com
An entry containing information about the route type
that a particular TRIP entity supports. Each entry
represents information about either the local or a remote
LS peer. The object tripRouteTypePeer is used to
distinguish this. In the case of a local LS, the
address/port information will reflect the values
configured in tripCfgTable. In the case of a remote
peer, the address/port information will reflect the
values of an entry in the tripPeerTable.
Implementation need to be aware that if the size of
tripRouteTypeAddr exceeds 111 sub-IDs, then OIDs of column
instances in this table will have more than 128 sub-IDs
and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3.
Parsed from file rfc3872-Telephony-Routing-over-IP-TRIP.mib-2.txt
Company: None
Module: TRIP-MIB
An entry containing information about the route type
that a particular TRIP entity supports. Each entry
represents information about either the local or a remote
LS peer. The object tripRouteTypePeer is used to
distinguish this. In the case of a local LS, the
address/port information will reflect the values
configured in tripCfgTable. In the case of a remote
peer, the address/port information will reflect the
values of an entry in the tripPeerTable.
Implementation need to be aware that if the size of
tripRouteTypeAddr exceeds 111 sub-IDs, then OIDs of column
instances in this table will have more than 128 sub-IDs
and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3.
Parsed from file TRIP-MIB.mib
Module: TRIP-MIB
Automatically extracted from RFC3872
tripRouteTypeEntry OBJECT-TYPE SYNTAX TripRouteTypeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing information about the route type that a particular TRIP entity supports. Each entry represents information about either the local or a remote LS peer. The object tripRouteTypePeer is used to distinguish this. In the case of a local LS, the address/port information will reflect the values configured in tripCfgTable. In the case of a remote peer, the address/port information will reflect the values of an entry in the tripPeerTable. Implementation need to be aware that if the size of tripRouteTypeAddr exceeds 111 sub-IDs, then OIDs of column instances in this table will have more than 128 sub-IDs and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3." INDEX { applIndex, tripRouteTypeAddrInetType, tripRouteTypeAddr, tripRouteTypePort, tripRouteTypeProtocolId, tripRouteTypeAddrFamilyId } ::= { tripRouteTypeTable 1 }
tripRouteTypeEntry OBJECT-TYPE SYNTAX TripRouteTypeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing information about the route type that a particular TRIP entity supports. Each entry represents information about either the local or a remote LS peer. The object tripRouteTypePeer is used to distinguish this. In the case of a local LS, the address/port information will reflect the values configured in tripCfgTable. In the case of a remote peer, the address/port information will reflect the values of an entry in the tripPeerTable. Implementation need to be aware that if the size of tripRouteTypeAddr exceeds 111 sub-IDs, then OIDs of column instances in this table will have more than 128 sub-IDs and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3." INDEX { applIndex, tripRouteTypeAddrInetType, tripRouteTypeAddr, tripRouteTypePort, tripRouteTypeProtocolId, tripRouteTypeAddrFamilyId } ::= { tripRouteTypeTable 1 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.116.1.2.1.1 | tripRouteTypeAddrInetType | 0 | 0 | The type of Inet Address of the tripRouteTypeAddr. |
| 1.3.6.1.2.1.116.1.2.1.2 | tripRouteTypeAddr | 0 | 0 | The network address of this entry's TRIP peer LS. The type of this address is determined by the value of the tripRouteTypeAddrIne… |
| 1.3.6.1.2.1.116.1.2.1.3 | tripRouteTypePort | 0 | 0 | The port for the TCP connection between this and an associated TRIP peer. |
| 1.3.6.1.2.1.116.1.2.1.4 | tripRouteTypeProtocolId | 0 | 0 | The object identifier of a protocol that the associated peer is using. |
| 1.3.6.1.2.1.116.1.2.1.5 | tripRouteTypeAddrFamilyId | 0 | 0 | The object identifier of an address family that the associated peer belongs to. |
| 1.3.6.1.2.1.116.1.2.1.6 | tripRouteTypePeer | 0 | 0 | This object identifies whether this entry is associated with a 'local' or 'remote' LS peer. |