Cisco Nexus 3600 NX-OS User Manual

•
For strict uRPF to work, you must enable it on both the ingress interface and the interface where the
source IP address is learned.
•
The switch hardware does not implement strict uRPF per the configured routing interface.
•
Strict uRPF is implemented per learned route on strict uRPF-enabled interfaces.
•
If a route is resolved as ECMP, strict uRPF will fall back to loose mode.
•
Because of the hardware limitation on the trap resolution, uRPF might not be applied on supervisor-bound
packets via inband.
•
For IP traffic, both IPv4 and IPv6 configurations should be enabled simultaneously.
•
Due to hardware limitations, the Cisco Nexus 3600 Series switches support only the following
combinations:
Applied Traffic Check on Source IP AddressuRPF Configuration
MPLS
Encap/VPN/ECMP
IP ECMPIP UnipathIPv6IPv4
AllowAllowAllowDisableDisable
uRPF looseuRPF looseuRPF looseLooseLoose
uRPF looseuRPF looseuRPF strictStrictStrict
Default Settings for Unicast RPF
This table lists the default settings for Unicast RPF parameters.
Table 14: Default Unicast RPF Parameter Settings
DefaultParameters
DisabledUnicast RPF
Configuring Unicast RPF
You can configure one the following Unicast RPF modes on an ingress interface: You can configure either
Strict Unicast RPF or Loose Unicast RPF mode on the ingress interface. For Strict Unicast mode, apply the
configuration to interfaces where the source IP is attached. This allows you to that you can white list specific
sources.
Cisco Nexus 3600 NX-OS Security Configuration Guide, Release 7.x
104
Configuring Unicast RPF
Default Settings for Unicast RPF

Cisco Nexus 3600 NX-OS Specifications

General

Brand	Cisco
Model	Nexus 3600 NX-OS
Category	Switch
Language	English