New and Changed Information

New and Changed Information

Table 1. New and Changed Features for Cisco NX-OS Release 10.4(x)

Feature

Description

Changed in Release

Where Documented

Support tunnel interfaces

ePBR supports IPv4 and IPv6 policies on tunnel interfaces.

10.4(1)F

Guidelines and Limitations for ePBR L3

Support for load-balancing/redirection to nodes over tunnels

ePBR supports redirection or load-balancing to layer-3 endpoints reachable over tunnel interfaces.

10.4(1)F

Guidelines and Limitations for ePBR L3

ePBR out-of-service

ePBR supports the ability to temporarily shutdown an endpoint, either administratively or by gracefully disabling the endpoint when a user defined failure threshold is met.

10.4(1)F

ePBR Service Endpoint Out-of-Service

Guidelines and Limitations for ePBR L3

Configuring ePBR Service Endpoint Out-of-Service

Support for port operators in ACLs

ePBR L3 and ePBR L2 policies supports Layer-4 port operators in match access-lists.

10.4(1)F

Guidelines and Limitations for ePBR L3

Guidelines and Limitations for ePBR L2

User mask position load-balance configuration options​

ePBR supports the mask-position configuration to choose the bits used for load-balancing in user-defined ACL for IPv4 or IPv6 matches.

10.4(1)F

Guidelines and Limitations for ePBR L2

Configuring ePBR Service, Policy, and Associating to an Interface

Configuration Examples for ePBR

Minimal disruptive fail-action for ePBR Layer 2

ePBR L2 fail-action feature is optimized to modify only the ACEs that are currently affected by the failure of the node.

10.4(1)F

ePBR Object Tracking, Health Monitoring, and Fail-Action

Support to redirect/deny 'all' packets using ePBR policy

Added the default redirect-all configuration for the ePBR policy to allow the catch-all rules to redirect all traffic, including control packets to redirect to the egress interface.

10.4(1)F

Guidelines and Limitations for ePBR L2

Enforcing Redirection and Drop for Control Traffic