tBgpPGExtendNhEncoding

TIMETRA-BGP-MIB · .1.3.6.1.4.1.6527.3.1.2.14.3.5.1.62

Object

column r/w TmnxIpFamily
The value of tBgpPGExtendNhEncoding specifies the type of AFI/SAFI the
Bgp group is configured to support extended next-hop encoding.

Context

MIB
TIMETRA-BGP-MIB
OID
.1.3.6.1.4.1.6527.3.1.2.14.3.5.1.62
Type
column
Access
readwrite
Status
current
Parent
tBgpPeerGroupParamsEntry
Groups
1

Walk the column to discover its indexed instances, or supply every index to read one instance.

Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'TIMETRA-BGP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-BGP-MIB::tBgpPGExtendNhEncoding'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'TIMETRA-BGP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-BGP-MIB::tBgpPGExtendNhEncoding.<index>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-BGP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-BGP-MIB::tBgpPGExtendNhEncoding'

Syntax

Source
TmnxIpFamily
Base type
Bits
Type Description
The value of TmnxIpFamily specifies the types of Network Layer Routing
Information (NLRI) to be distributed by BGP. BGP was initially
designed for the distribution of IPv4 routing information.
Multi-protocol extensions such as IPv6, VPN-IPv4 and VPN-IPv6,
MVPN-IPv4 and MVPN-IPv6, L2-VPN addresses, and many more have been
added to extend its ability to carry overlapping routing information.
At the current time, NLRI for 21 address families can be carried in
MP-BGP.
          
The first address family is plain 'IPv4 (1)'. The NLRI for this
address family was described in RFC1771, which was the original BGPv4
RFC. (RFC1771 was later obsoleted by RFC4271). Therefor the NLRI does
not need to be encapsulated in Multi-Protocol BGP. IPv4 is the only
address family that does not need to be encapsulated in MP-BGP.
          
All following address families are transported using Multi-Protocol
BGP. MP-BGP was first described in RFC2283, which is obsoleted by
RFC4760.
          
A 'vpnIpv4 (2)' NLRI is a an IPv4 prefix advertised in the context of
a Virtual Private Network (VPN). The format of a vpnIpv4 NLRI is a
12-byte value consisting of an 8-byte Route Distinguisher (RD), and
the 4-byte ipv4 IP prefix. The RD must be unique within the scope of
the VPRN. This allows the IP address prefixes within different VRFs to
overlap. IPv4 VPNs were first described in RFC2547, which was
obsoleted by RFC4364.
          
An 'ipv6 (3)' NLRI is an IPv6 prefix, used for natively routing IPv6.
See RFC2545.
          
An 'mcastIpv4 (4)' NLRI is an ipv4 prefix that can be used for the
Reverse Path Forwarding check (RPF) in multicast-routing. This allows
a network to have a incongruent topology for unicast routing and
multicast-routing.
          
A 'vpnIpv6 (5)' NLRI is an address from family 'ipv6 (3)' carried
inside a VPN. The format is a 24-byte value consisting of the 8-byte
RD, and 16 bytes for the IPv6 prefix. When both IPv4 and IPv6 VPRN
services are enabled, the PE router uses the same RD for both address
families. See RFC4659.
          
A 'l2vpn (6)' address is a 12-byte Virtual Switch Instance identifier
(VSI-ID) value consisting of the 8-byte route distinguisher(RD)
followed by a 4-byte value.
          
A 'mvpnIpv4  (7)' address is variable size value consisting of the
1-byte route type, 1-byte length and variable size route type specific.
The content of these NLRI are PIM messages. See RFC6513.
          
A 'mdtSafi (8)' address is a 16-byte value consisting of 12-byte route
distinguisher(RD) followed by a 4-byte group address.
          
A 'mspw (9)' address is a dynamic multi-segment pseudowire address.
          
A 'flowIpv4 (10)' address is a variable size value consisting of 1 or
2-byte NLRI (Network Layer Reachability Information) length followed
by a variable length NLRI value.
          
A 'routeTarget (11)' address is a variable size value consisting of
zero length or 12 byte (ipv4) or 24 byte (ipv6) NLRI (Network Layer
Reachability Information) length followed by a variable length NLRI
value.
          
A 'mcastVpnIpv4(12)' NLRI is an address from family 'mcastIpv4 (4)'
carried inside a VPN. The format is a 12-byte value consisting of the
8-byte RD and 4 bytes for the IPv4 prefix. This allows customers to
have incongruent unicast and multicast topologies over a VPN.
          
A 'mvpnIpv6 (13)' address is variable size value consisting of the
1-byte route type, 1-byte length and variable size route type
specific. The content of these NLRI are PIM messages. See RFC6513.
          
A 'flowIpv6 (14)' address is a variable size value consisting of 1 or
2-byte NLRI(Network Layer Reachability Information) length followed by
a variable length NLRI value.
          
A 'evpn (15)' address is variable size value consisting of the 1-byte
route type, 1-byte length and variable size route type specific. Route
type defines encoding for the route type specific field. Length
indicates the length in octets of the route type specific field.
          
A 'mcastIpv6 (16)' NLRI is similar to 'mcastIpv4 (4)', but for IPv6.
The mcastIpv6 NLRI is an ipv6 prefix that can be used for the Reverse
Path Forwarding check (RPF) in multicast-routing. This allows a
network to have a incongruent topology for unicast IPv6 routing and
multicast-IPv6-routing.
          
A 'bgpLs (19)' NLRI is a piece of information that has been taken from
the Link-State Database of IS-IS or OSPF, and is transported via BGP
to a controller. This can e.g. be a SDN-controller, or a network
management station.
          
A 'mcastVpnIpv6 (20)' NLRI is a prefix from family 'mcastIpv6 (16)'
carried inside a VPN. The format is a 24-byte value consisting of the
8-byte RD and 16 bytes for the IPv6 prefix. This allows customers to
have incongruent unicast and multicast IPv6-topologies over a VPN.
          
If any address type is added to TmnxIpFamily, the same address type
should also be added in TmnxIpFamilyIdentifier.

Values & Constraints

Type Values
0unused
1ipv4
2vpnIpv4
3ipv6
4mcastIpv4
5vpnIpv6
6l2vpn
7mvpnIpv4
8mdtSafi
9mspw
10flowIpv4
11routeTarget
12mcastVpnIpv4
13mvpnIpv6
14flowIpv6
15evpn
16mcastIpv6
17labelIpv4
18labelIpv6
19bgpLs
20mcastVpnIpv6
21srplcyIpv4
22srplcyIpv6
23flowVpnIpv4
24flowVpnIpv6