• Author : Nikhil Goyal

 
 

Support for ECMP routes in RIP

Description This feature adds the support for learning multiple equal cost routes for a destination in the RIP protocol. This increases the robustness as well as enables the router to load balance the traffic through different paths. This feature will only support enabling or disabling of the ECMP and users will not have an option to control the maximum number of next hops in an ECMP route. By default, ECMP is disabled. The feature is supported in both single-agent as well as multi-agent routing protocol models. Platform compatibility This feature is provided on all platforms. Configuration The following CLI command...
Continue reading →

DSCP support for CPU generated traffic

The differentiated services code point (DSCP) is a 6 bit field in the IP header, which can be used to mark traffic for providing quality of service (QoS). This feature can be used to set the DSCP value individually for various protocols that are used for network management. All protocol specific traffic leaving the switch will be marked with the configured DSCP value. The supported protocols are RADIUS, TACACS, SNMP, SSH and sFlow. IPv4 support for this feature is available since 4.18.1F. IPv6 support for this feature is available since 4.23.0F. Platform compatibility This feature is provided on all platforms....
Continue reading →

DSCP support for CPU generated traffic

Description The differentiated services code point (DSCP) is a 6-bit field in the IP header, which can be used to mark traffic for providing quality of service (QOS). This feature adds the support to set the DSCP value individually for NTP, DNS, Syslog, Traceroute, OSPF, and OSPF3 protocols. All protocol specific traffic leaving the switch will be marked with the configured DSCP value. In the case of NTP, DNS, Syslog, and Traceroute, the configured DSCP value will be applicable for both ipv4 and ipv6 traffic. This feature is an extension to DSCP support. Platform compatibility This feature is provided on...
Continue reading →

IS-IS LSDB Export

Description This feature provides streaming of the IS-IS Link State Database via TerminAttr. The IS-IS LSDB is exported to Smash at the following path Smash/routing/isis/lsdb/<level>/<VRF>/. The Smash table is keyed by LSPID (in network byte order) and the value is the entire IS-IS LSP contents. The LSDB is exported as a blob or in raw format, i.e., the LSP contents are kept in the IS-IS on-wire format. The exported LSDB allows customers who want to consume the LSDB via TerminAttr to parse the IS-IS LSPs for ingest into their collection infrastructure (SDN controller). LSPs are written to Smash when there is...
Continue reading →

IS-IS Graceful Restart

IS-IS Graceful Restart adds support for Restart Signaling for IS-IS, IETF RFC 5306. When IS-IS is used as the IGP, the following EOS features require NSF and support for the graceful restart from IS-IS: ASU2 – Software upgrades. SSO – Planned SSO initiated by an operator for maintenance or Unplanned SSO due to failures on the active supervisor. RIB agent restart due to software failures. With IS-IS Graceful Restart (GR) configured, a redundancy switchover from active to standby supervisor or ASU2 or restart of the IS-IS software (the RIB Agent) should, if the GR completes successfully, be a hitless event.  Which means that neighbor routers continue to...
Continue reading →

Follow

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

Join other followers: