• Author : Yuanzhi Gao

 
 

Per Address Family BGP Missing Policy Action for Multi-agent Model

Description Prior to EOS-4.23.2F, BGP missing policy action configuration is a global BGP configuration that, when set to deny, will deny/reject import (and/or export) of all routes when route-map is missing or misconfigured and it only applies to IPv4 Unicast and IPv6 Unicast address family. Now for multi-agent routing protocol model (single-agent model remains unchanged), the missing policy action can be applied to all address families by specifying “address-family all” in the existing missing policy configuration. With “address-family all” enabled, missing-policy config will apply to all AFs. Note that “address-family all” applies a “loose” behavior that misconfigured route map in...
Continue reading →

LSP Ping/Traceroute for MPLS Nexthop Group Tunnels

Description MPLS ping/traceroute utility is extended to support liveness checking of Nexthop Group tunnel endpoint (MPLS Nexthop Group). The feature is also supported on vEOS-lab and cEOS-lab. Platform Compatibility Platform independent. vEOS-lab/cEOS-lab. CLI Command ping mpls tunnel nexthop-group <endpoint> [entry <index>] Example output: rtrmpls1#ping mpls tunnel nexthop-group 100.0.116.1/32 LSP ping to nexthop-group tunnel 100.0.116.1/32 100.0.116.1/32: nexthop-group tunnel index 1 (nexthop-group name: nhg-100) Entry 0 Via 10.0.16.2 Reply from 10.0.108.1: seq=1, time=507.546ms Entry 1 Via 10.0.16.8 Reply from 10.0.113.1: seq=1, time=516.131ms --- nexthop-group tunnel index 1, nexthop-group nhg-100: lspping statistics --- Entry 0 Via 10.0.16.2 1 packets transmitted, 1 received, 0%...
Continue reading →

Support for Nexthop Group as IP Tunnels

Description Nexthop Group tunnels are a tunneling abstraction in EOS. A nexthop group tunnel is comprised of a tunnel endpoint (IP prefix) and a nexthop group name representing the underlying nexthop group that forwards the traffic. If the underlying nexthop group is not configured, the tunnel endpoint will be unreachable until the given nexthop group is configured. Platform Compatibility Platform independent Configuration The nexthop-group tunnel can be configured by the following CLI command under global config mode: ip tunnel <prefix> nexthop-group <nhg-name> To remove a nexthop-group tunnel: no ip tunnel <prefix> nexthop-group Limitations Egress tunnel counter for Nexthop Group tunnel...
Continue reading →

ipv6 nd ra experimental network-boot

Description This configuration command features an IPv6 Neighbor Discovery (ND) option (called Boot File URL (BFURL) option) that can be used to provide configuration information for nodes to be booted from the network. Platform Compatibility Platform independent Configuration This feature can be activated per-interface basis and it is supported in default and non default VRF. interface Vlan 100 ipv6 nd ra experimental network-boot <bootfile-url> The existing ND message (RA) is used to carry this network boot information.  Nodes can get the boot file url and parameters through RA messages via BFURL option. Show Commands None Syslog Messages None References https://tools.ietf.org/html/draft-qin-6man-nb-option-03

Follow

Get every new post on this blog delivered to your Inbox.

Join other followers: