Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 4.1

Configuring Control Plane Policing

This chapter describes how to configure control plane policing (CoPP) on the NX-OS device.

This chapter includes the following sections:

•Information About CoPP

•Guidelines and Limitations

•Configuring CoPP

•Displaying the CoPP Statistics

•Verifying CoPP Configuration

•CoPP Example Configurations

•Default Settings

•Additional References

•Feature History for CoPP

Information About CoPP

The NX-OS device provides control plane policing to prevent denial-of-service (DoS) attacks from impacting performance.

The supervisor module divides the traffic that it manages into three functional components or planes:

•Data plane—Handles all the data traffic. The basic functionality of a NX-OS device is to forward packets from one interface to another. The packets that are not meant for the switch itself are called the transit packets. These packets are handled by the data plane.

•Control plane—Handles all routing protocol control traffic. These protocols, such as the Border Gateway Protocol (BGP), Open Shortest Path First (OSPF) Protocol, and Protocol Independent Multicast (PIM) Protocol, send control packets between devices. These packets are destined to router addresses and are called control plane packets.

•Management plane—Runs the components meant for NX-OS device management purposes such as the command-line interface (CLI) and Simple Network Management Protocol (SNMP).

The supervisor module has both the management plane and control plane and is critical to the operation of the network. Any disruption or attacks to the supervisor module will result in serious network outages. For example, excessive traffic to the supervisor module could overload and slow down the performance of the entire NX-OS device. Attacks on the supervisor module can be of various types such as DoS that generates IP traffic streams to the control plane at a very high rate. These attacks force the control plane to spend a large amount of time in handling these packets and prevents the control plane from processing genuine traffic.

Examples of DoS attacks are as follows:

•Internet Control Message Protocol (ICMP) echo requests

•IP fragments

•TCP SYN flooding

These attacks can impact the device performance and have the following negative effects:

•High supervisor CPU utilization.

•Loss of line protocol keep-alive messages and routing protocol updates, which lead to route flaps and major network outages.

•Interactive sessions using the CLI become slow or completely unresponsive due to high CPU utilization.

•ïResources, such as the memory and buffers, might be unavailable for legitimate IP data packets.

•Packet queues fill up, which can cause indiscriminate packet drops.

Caution It is important to ensure that you protect the supervisor module from accidental or malicious attacks by setting appropriate control plane protection.

This section includes the following topics:

•Control Plane Protection

•Modular QoS Command-Line Interface

•CoPP and the Management Interface

•Virtualization Support

Control Plane Protection

To protect the control plane, the NX-OS device segregates different packets destined to the control plane into different classes. Once these classes are identified, the NX-OS device polices or marks down packets, which ensure that the supervisor module is not overwhelmed.

This section includes the following topics:

•Control Plane Packet Types

•Classification

•Rate Controlling Mechanisms

•Default Policing Policies

Control Plane Packet Types

Different types of packets can reach the control plane:

•Receive packets—Packets that have the destination address of a router. The destination address can be a Layer 2 address (such as a router MAC address) or a Layer 3 address (such as the IP address of a router interface). These packets include router updates and keepalive messages. Multicast packets can also be in this category where packets are sent to multicast addresses that are used by a router.

•Exception packets—Packets that need special handling by the supervisor module. For example, if a destination address is not present in the Forwarding Information Base (FIB) and results in a miss, then the supervisor module sends an ICMP unreachable packet back to the sender. Another example is a packet with IP options set.

•Redirected packets—Packets that are redirected to the supervisor module. Features like Dynamic Host Configuration Protocol (DHCP) snooping or dynamic Address Resolution Protocol (ARP) inspection redirect some packets to the supervisor module.

•Glean packets—If a Layer 2 MAC address for a destination IP address is not present in the FIB, the supervisor module receives the packet and sends an ARP request to the host.

All of these different packets could be maliciously used to attack the control plane and overwhelm the NX-OS device. CoPP classifies these packets to different classes and provides a mechanism to individually control the rate at which the supervisor module receives these packets.

Classification

For effective protection, the NX-OS device classifies the packets that reach the supervisor modules to allow you to apply different rate controlling policies based on the type of the packet. For example, you might want to be less strict with a protocol packet such as Hello messages but more strict with a packet that is sent to the supervisor module because the IP option is set. The following parameters that can be used for classifying a packet:

•Source IP address

•Destination IP address

•Source MAC address

•Destination MAC address

•VLAN

•Source port

•Destination port

•Exception cause

Rate Controlling Mechanisms

Once the packets are classified, the NX-OS device has different mechanisms to control the rate at which packets arrive at the supervisor module. Two mechanisms control the rate of traffic to the supervisor module. One is called policing and the other is called rate limiting.

Using hardware policers, you can define separate actions for traffics that conforms to, exceeds, or violates certain conditions. The actions can transmit the packet, mark down the packet, or drop the packet.

You can configure the following parameters for policing:

•Committed information rate (CIR)—Desired bandwidth, specified as a bit rate or a percentage of the link rate.

•Peak information rate (PIR)—Rate above which data traffic is negatively affected.

•Committed burst (BC)—Size of a traffic burst that can exceed the CIR within a given unit of time and not impact scheduling.

•Extended burst (BE)—Size that a traffic burst can reach before all traffic exceeds the PIR.

In addition you can set separate actions such as transmit or drop for conform, exceed, and violate traffic.

For more information on policing parameters, see the Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide, Release 4.1.

Default Policing Policies

When you bring up your NX-OS device for the first time, the NX-OS software installs the default copp-system-policy policy to protect the supervisor module from DoS attacks. You can set the level of protection by choosing one of the following CoPP policy options from the initial setup utility:

•Strict—This policy is 1 rate and 2 color and has BC value of 250 ms, except for the important class, which has a value of 1000 ms.

•Moderate—This policy is 1 rate and 2 color and has a BC value of 310 ms, except for the important class, which has a value of 1250 ms. These values are 25 percent greater than the strict policy.

•Lenient—This policy is 1 rate and 2 color and has a BC value of 375 ms, except for the important class, which has a value of 1500 ms. These values are 50 percent greater than the strict policy.

•None—No control plane policy is applied.

If you do not select an option or choose not to execute the setup utility, the NX-OS software applies strict policing. You can change the CoPP policies as needed from the CLI. You can also remove the default copp-system-policy from the CLI.

The copp-system-policy policy has optimized values suitable for basic device operations. You must add specific class and access-control list (ACL) rules that meet your DoS protection requirements. The default CoPP policy does not change when you upgrade the NX-OS software on your device.

Caution Selecting the none option and not subsequently configuring CoPP protection can leave your NX-OS device vulnerable to DoS attacks.

In Cisco NX-OS Release 4.0(2) and later releases, you can reassign the CoPP default policy by entering the setup utility again using the setup command from the CLI prompt. Any changes you have made to the CoPP configuration are lost. For an example of using the setup utility, see the "Changing or Reapplying the Default CoPP Policy" section.

Note If you are using a CoPP default policy, we recommend that you reapply the CoPP default policy using the setup command after you upgrade to Cisco NX-OS Release 4.1(2) or later releases (see the "Changing or Reapplying the Default CoPP Policy" section). The CoPP default policies have the following changes for Release 4.1(2) and later releases:

•Changed the default policing policies as follows:

–All default policies are one rate and two colors.

–The strict policy has BC value of 250 ms, except for the important class, which has a value of 1000 ms.

–The moderate policy has a BC value of 310 ms, except for the important class, which has a value of 1250 ms. These values are 25 percent greater than the strict policy.

–Lenient policy has a BC value of 375 ms, except for the important class, which has a value of 1500 ms. These values are 50 percent greater than the strict policy.

•Added IPv6 ACLs for BGP, OSPF, PIM, TACACS+, RADIUS, NTP, TFTP, SSH, Telnet, and ICMP.

•Added IPv6 exception in the copp-system-class-exception class.

•Added pim-reg in the copp-system-class-important class.

•Enhanced CoPP policies for HSRP and GLBP to improve scalability.

This section includes the following topics:

•Default Classes

•Strict Default CoPP Policy

•Moderate Default CoPP Policy

•Lenient Default CoPP Policy

Default Classes

The copp-system-class-critical class has the following configuration:

ip access-list copp-system-acl-igmp

    permit igmp any 224.0.0.0/24

ip access-list copp-system-acl-msdp

    permit tcp any gt 1024 any eq 639

    permit tcp any eq 639 any gt 1024

ip access-list copp-system-acl-bgp

    permit tcp any gt 1024 any eq bgp

    permit tcp any eq bgp any gt 1024

ip access-list copp-system-acl-eigrp

    permit eigrp any any

ip access-list copp-system-acl-rip

    permit udp any 224.0.0.0/24 eq rip

ip access-list copp-system-acl-ospf

    permit ospf any any

ip access-list copp-system-acl-pim

    permit pim any 224.0.0.0/24

    permit udp any any eq pim-auto-rp

ipv6 access-list copp-system-acl-bgp6

    permit tcp any gt 1024 any eq bgp

    permit tcp any eq bgp any gt 1024

ipv6 access-list copp-system-acl-ospf6

    permit 89 any any

ipv6 access-list copp-system-acl-pim6

    permit 103 any FF02::D/128

    permit udp any any eq pim-auto-rp

class-map type control-plane match-any copp-system-class-critical

    match access-group name copp-system-acl-igmp

    match access-group name copp-system-acl-msdp

    match access-group name copp-system-acl-bgp

    match access-group name copp-system-acl-eigrp

    match access-group name copp-system-acl-rip

    match access-group name copp-system-acl-ospf

    match access-group name copp-system-acl-pim

    match access-group name copp-system-acl-bgp6

    match access-group name copp-system-acl-ospf6

    match access-group name copp-system-acl-pim6

The copp-system-class-important class has the following configuration:

ip access-list copp-system-acl-hsrp

    permit udp any 224.0.0.0/24 eq 1985

ip access-list copp-system-acl-vrrp

    permit 112 any 224.0.0.0/24

ip access-list copp-system-acl-glbp

    permit udp any eq 3222 224.0.0.0/24 eq 3222

ip access-list copp-system-acl-pim-reg

    permit pim any any

class-map type control-plane match-any copp-system-class-important        

    match access-group name copp-system-acl-hsrp

    match access-group name copp-system-acl-vrrp

    match access-group name copp-system-acl-glbp

    match access-group name copp-system-acl-pim-reg

The copp-system-class-management class has the following configuration:

ip access-list copp-system-acl-tacacs

    permit tcp any any eq tacacs

    permit tcp any eq tacacs any

ip access-list copp-system-acl-radius

    permit udp any any eq 1812

    permit udp any any eq 1813

    permit udp any any eq 1645

    permit udp any any eq 1646

    permit udp any eq 1812 any

    permit udp any eq 1813 any

    permit udp any eq 1645 any

    permit udp any eq 1646 any

ip access-list copp-system-acl-ntp

    permit udp any any eq ntp

    permit udp any eq ntp any

ip access-list copp-system-acl-ftp

    permit tcp any any eq ftp-data

    permit tcp any any eq ftp

    permit tcp any eq ftp-data any

    permit tcp any eq ftp any

ip access-list copp-system-acl-tftp

    permit udp any any eq tftp

    permit udp any any eq 1758

    permit udp any eq tftp any

    permit udp any eq 1758 any

ip access-list copp-system-acl-sftp

    permit tcp any any eq 115

    permit tcp any eq 115 any

ip access-list copp-system-acl-ssh

    permit tcp any any eq 22

    permit tcp any eq 22 any

ip access-list copp-system-acl-snmp

    permit udp any any eq snmp

    permit udp any any eq snmptrap

ip access-list copp-system-acl-telnet

    permit tcp any any eq telnet

    permit tcp any any eq 107

    permit tcp any eq telnet any

    permit tcp any eq 107 any

ipv6 access-list copp-system-acl-tacacs6

    permit tcp any any eq tacacs

    permit tcp any eq tacacs any

ipv6 access-list copp-system-acl-radius6

    permit udp any any eq 1812

    permit udp any any eq 1813

    permit udp any any eq 1645

    permit udp any any eq 1646

    permit udp any eq 1812 any

    permit udp any eq 1813 any

    permit udp any eq 1645 any

    permit udp any eq 1646 any

ipv6 access-list copp-system-acl-ntp6

    permit udp any any eq ntp

    permit udp any eq ntp any

ipv6 access-list copp-system-acl-tftp6

    permit udp any any eq tftp

    permit udp any any eq 1758

    permit udp any eq tftp any

    permit udp any eq 1758 any

ipv6 access-list copp-system-acl-ssh6

    permit tcp any any eq 22

    permit tcp any eq 22 any

ipv6 access-list copp-system-acl-telnet6

    permit tcp any any eq telnet

    permit tcp any any eq 107

    permit tcp any eq telnet any

    permit tcp any eq 107 any

class-map type control-plane match-any copp-system-class-management

    match access-group name copp-system-acl-tacacs

    match access-group name copp-system-acl-radius

    match access-group name copp-system-acl-ntp

    match access-group name copp-system-acl-ftp

    match access-group name copp-system-acl-tftp

    match access-group name copp-system-acl-sftp

    match access-group name copp-system-acl-ssh

    match access-group name copp-system-acl-snmp

    match access-group name copp-system-acl-telnet

    match access-group name copp-system-acl-tacacs6

    match access-group name copp-system-acl-radius6

    match access-group name copp-system-acl-ntp6

    match access-group name copp-system-acl-tftp6

    match access-group name copp-system-acl-ssh6

    match access-group name copp-system-acl-telnet6

The copp-system-class-normal class has the following configuration:

class-map type control-plane match-any copp-system-class-normal

    match protocol arp

The copp-system-class-redirect class has the following configuration:

class-map type control-plane match-any copp-system-class-redirect

    match redirect arp-inspect

    match redirect dhcp-snoop

The copp-system-class-monitoring class has the following configuration:

ip access-list copp-system-acl-icmp

    permit icmp any any echo

    permit icmp any any echo-reply

ip access-list copp-system-acl-traceroute

    permit icmp any any ttl-exceeded

    permit icmp any any port-unreachable

ipv6 access-list copp-system-acl-icmp6

    permit icmp any any echo-request

    permit icmp any any echo-reply

class-map type control-plane match-any copp-system-class-monitoring

    match access-group name copp-system-acl-icmp

    match access-group name copp-system-acl-traceroute

    match access-group name copp-system-acl-icmp6

The copp-system-class-exception class has the following configuration:

class-map type control-plane match-any copp-system-class-exception

    match exception ip option

    match exception ip icmp unreachable

    match exception ipv6 option

    match exception ipv6 icmp unreachable

The copp-system-class-undesirable class has the following configuration:

ip access-list copp-system-acl-undesirable

    permit udp any any eq 1434

class-map type control-plane match-any copp-system-class-undesirable

    match access-group name copp-system-acl-undesirable

Strict Default CoPP Policy

The strict default CoPP policy has the following configuration:

policy-map type control-plane copp-system-policy

    class copp-system-class-critical

        police cir 40900 kbps bc 250 ms conform transmit violate drop

    class copp-system-class-important

        police cir 1060 kbps bc 1000 ms conform transmit violate drop

    class copp-system-class-management

        police cir 10000 kbps bc 250 ms conform transmit violate drop

    class copp-system-class-normal

        police cir 680 kbps bc 250 ms conform transmit violate drop

    class copp-system-class-redirect

        police cir 280 kbps bc 250 ms conform transmit violate drop

    class copp-system-class-monitoring

        police cir 100 kbps bc 250 ms conform transmit violate drop

    class copp-system-class-exception

        police cir 360 kbps bc 250 ms conform transmit violate drop

    class copp-system-class-undesirable

        police cir 32 kbps bc 250 ms conform drop violate drop

    class class-default

        police cir 100 kbps bc 250 ms conform transmit violate drop

Moderate Default CoPP Policy

The moderate default CoPP policy has the following configuration:

policy-map type control-plane copp-system-policy

    class copp-system-class-critical

        police cir 40900 kbps bc 310 ms conform transmit violate drop

    class copp-system-class-important

        police cir 1060 kbps bc 1250 ms conform transmit violate drop

    class copp-system-class-management

        police cir 10000 kbps bc 310 ms conform transmit violate drop

    class copp-system-class-normal

        police cir 680 kbps bc 310 ms conform transmit violate drop

    class copp-system-class-redirect

        police cir 280 kbps bc 310 ms conform transmit violate drop

    class copp-system-class-monitoring

        police cir 100 kbps bc 310 ms conform transmit violate drop

    class copp-system-class-exception

        police cir 360 kbps bc 310 ms conform transmit violate drop

    class copp-system-class-undesirable

        police cir 32 kbps bc 310 ms conform drop violate drop

    class class-default

        police cir 100 kbps bc 310 ms conform transmit violate drop

Lenient Default CoPP Policy

The lenient default CoPP policy has the following configuration:

policy-map type control-plane copp-system-policy

    class copp-system-class-critical

        police cir 40900 kbps bc 375 ms conform transmit violate drop

    class copp-system-class-important

        police cir 1060 kbps bc 1500 ms conform transmit violate drop

    class copp-system-class-management

        police cir 10000 kbps bc 375 ms conform transmit violate drop

    class copp-system-class-normal

        police cir 680 kbps bc 375 ms conform transmit violate drop

    class copp-system-class-redirect

        police cir 280 kbps bc 375 ms conform transmit violate drop

    class copp-system-class-monitoring

        police cir 100 kbps bc 375 ms conform transmit violate drop

    class copp-system-class-exception

        police cir 360 kbps bc 375 ms conform transmit violate drop

    class copp-system-class-undesirable

        police cir 32 kbps bc 375 ms conform drop violate drop

    class class-default

        police cir 100 kbps bc 375 ms conform transmit violate drop

Modular QoS Command-Line Interface

CoPP uses the Modular Quality of Service Command-Line Interface (MQC). MQC is a CLI structure that allows you to define a traffic class, create a traffic policy (policy map), and attach the traffic policy to an interface. The traffic policy contains the CoPP feature that will be applied to the traffic class.

The MQC structure consists of the following high-level steps:

Step 1 Define a traffic class using the class-map command. A traffic class is used to classify traffic.

Step 2 Create a traffic policy using the policy-map command. A traffic policy (policy map) contains a traffic class and one or more CoPP features that will be applied to the traffic class. The CoPP features in the traffic policy determine how to treat the classified traffic.

Step 3 Attach the traffic policy (policy map) to the control plane using the control-plane and service-policy commands.

CoPP and the Management Interface

The NX-OS device supports only hardware-based CoPP which does not support the management interface (mgmt0). The out-of-band mgmt0 interface connects directly to the CPU and not pass through the in-band traffic hardware where CoPP is implemented. To limit traffic on the mgmt0 interface, use ACLs (see Chapter 11, "Configuring IP ACLs" and Chapter 12, "Configuring MAC ACLs").

Virtualization Support

Licensing Requirements for CoPP

The following table shows the licensing requirements for this feature:

Guidelines and Limitations

CoPP has the following configuration guidelines and limitations:

•You must use the setup utility to change or reapply the default copp-system-policy policy. You can access the setup utility using the setup command at the CLI.

•CoPP does not support non-IP classes except for the default non-IP class. You can use ACLs instead of non-IP classes to drop non-IP traffic, and use the default non-IP CoPP class to limit to non-IP traffic that reaches the supervisor module.

•You cannot enable logging in CoPP policy ACLs.

•You must ensure that the CoPP policy does not filter critical traffic such as routing protocols or interactive access to the switches. Filtering this traffic could prevent remote access to the NX-OS device and require a console connection.

•The NX-OS software does not support egress CoPP or silent mode. CoPP is supported only on ingress (service-policy output CoPP cannot be applied to the control plane interface).

•You can use the access control entry (ACE) hit counters in the hardware only for ACL logic. Use the software ACE hit counters and the show access-lists and show policy-map type control-plane commands to evaluate CPU traffic.

•The NX-OS device hardware performs CoPP on a per-forwarding-engine basis. CoPP does not support distributed policing. Therefore, you should choose rates so that the aggregate traffic does not overwhelm the supervisor module.

Note If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might differ from the Cisco IOS commands that you would use.

Configuring CoPP

This section includes the following topics:

•Configuring a Control Plane Class Map

•Configuring a Control Plane Policy Map

•Configuring the Control Plane Service Policy

•Changing or Reapplying the Default CoPP Policy

Configuring a Control Plane Class Map

You must configure control plane class maps for control plane policies.

You can classify traffic by matching packets based on existing IPv4 and IPv6 ACLs. The permit and deny ACL keywords are ignored in the matching.

BEFORE YOU BEGIN

Ensure that you are in the default VDC (or use the switchto vdc command).

Ensure that you have configured the IP ACLs (see Chapter 11, "Configuring IP ACLs") or MAC ACLs (see Chapter 12, "Configuring MAC ACLs") if you want to use ACE hit counters in the class maps.

SUMMARY STEPS

1. configure terminal

2. class-map type control-plane [match-all | match-any] class-map-name

3. match access-group name access-list-name

match exception {ip | ipv6} icmp redirect

match exception {ip | ipv6} icmp unreachable

match exception {ip | ipv6} option

match protocol arp

match redirect arp-inspect

match redirect dhcp-snoop

4. exit

5. show class-map type control-plane [class-map-name]

6. copy running-config startup-config

DETAILED STEPS

Configuring a Control Plane Policy Map

You must configure a policy map for CoPP, which include policing parameters. If you do not configure a policer for a class, then the default policer conform action is drop. Glean packets are policed using the default-class. The NX-OS software supports 1-rate 2-color and 2-rate 3-color policing.

BEFORE YOU BEGIN

Ensure that you are in the default VDC (or use the switchto vdc command).

Ensure that you have configured a control plane class map (see the "Configuring a Control Plane Class Map" section).

SUMMARY STEPS

1. configure terminal

2. policy-map type control-plane policy-map-name

3. class {class-map-name [insert-before class-map-name] | class-default}

4. police [cir] cir-rate [bps | gbps | kbps | mbps | pps]

police [cir] cir-rate [bps | gbps | kbps | mbps | pps] [bc] burst-size [bytes | kbytes | mbytes | ms | packets | us]

police [cir] cir-rate [bps | gbps | kbps | mbps | pps]
conform {drop | set-cos-transmit cos-value | set-dscp-transmit dscp-value | set-prec-transmit prec-value | transmit} [exceed {drop | set dscp dscp table cir-markdown-map | transmit}] [violate {drop | set dscp dscp table pir-markdown-map | transmit}]

police [cir] cir-rate [bps | gbps | kbps | mbps | pps]
pir pir-rate [bps | gbps | kbps | mbps | pps] [[be] extended-burst-size [bytes | kbytes | mbytes | ms | packets | us]]

5. (Optional) set cos [inner] cos-value

6. (Optional) set dscp [tunnel] {dscp-value | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | cs1 | cs2 | cs3 | cs4 | cs5 | cs6 | cs7 | sf | default}

7. (Optional) set precedence [tunnel] prec-value

8. exit

9. exit

10. show policy-map type control-plane [expand] [name policy-map-name]

11. copy running-config startup-config

DETAILED STEPS

Configuring the Control Plane Service Policy

You can configure one or more policy maps for the CoPP service policy.

BEFORE YOU BEGIN

Ensure that you are in the default VDC (or use the switchto vdc command).

Ensure that you have configured a control plan policy map (see the "Configuring a Control Plane Policy Map" section).

SUMMARY STEPS

1. configure terminal

2. control-plane

3. service-policy input policy-map-name

4. exit

5. show running-config copp [all]

6. copy running-config startup-config

DETAILED STEPS

Changing or Reapplying the Default CoPP Policy

In Cisco NX-OS Release 4.0(2) and later releases, you can change to a different default CoPP policy using the setup utility. You can also reapply the same CoPP default policy. For an example of changing the default CoPP policy, see the "Changing or Reapplying the Default CoPP Policy" section.

BEFORE YOU BEGIN

Ensure that you are in the default VDC (or use the switchto vdc command).

SUMMARY STEPS

1. setup

DETAILED STEPS

Displaying the CoPP Configuration Status

In Cisco NX-OS Release 4.0(2) and later releases, you can display the CoPP feature configuration status information.

BEFORE YOU BEGIN

Ensure that you are in the default VDC (or use the switchto vdc command).

SUMMARY STEPS

1. show copp status

DETAILED STEPS

For detailed information about the fields in the output from this command, see to the Cisco Nexus 7000 Series NX-OS Security Command Reference, Release 4.1.

Displaying the CoPP Statistics

You can display the CoPP statistics.

BEFORE YOU BEGIN

Ensure that you are in the default VDC (or use the switchto vdc command).

SUMMARY STEPS

1. show policy-map interface control-plane

DETAILED STEPS

For detailed information about the fields in the output from this command, see to the Cisco Nexus 7000 Series NX-OS Security Command Reference, Release 4.1.

Clearing the CoPP Statistics

You can clear the CoPP statistics.

BEFORE YOU BEGIN

Ensure that you are in the default VDC (or use the switchto vdc command).

SUMMARY STEPS

1. show policy-map interface control-plane

2. clear copp statistics

DETAILED STEPS

Verifying CoPP Configuration

To display CoPP configuration information, perform one of the following tasks:

For detailed information about the fields in the output from these commands, see to the Cisco Nexus 7000 Series NX-OS Security Command Reference, Release 4.1.

CoPP Example Configurations

This section includes the following topics:

•CoPP Configuration Example

•Changing or Reapplying the Default CoPP Policy

CoPP Configuration Example

The following example shows how to configure CoPP using IP ACLs and MAC ACLs:

configure terminal

ip access-list copp-system-acl-igmp 

permit igmp any 10.0.0.0/24

ip access-list copp-system-acl-msdp 

permit tcp any any eq 639

mac access-list copp-system-acl-arp 

permit any any 0x0806

ip access-list copp-system-acl-tacas 

permit udp any any eq 49

ip access-list copp-system-acl-gre 

permit 47 any any

ip access-list copp-system-acl-ntp 

permit udp any 10.0.1.1/23 eq 123

ip access-list copp-system-acl-icmp 

permit icmp any any

class-map type control-plane match-any copp-system-class-critical

match access-group name copp-system-acl-igmp

match access-group name copp-system-acl-msdp

match access-group name copp-system-acl-arp

class-map type control-plane match-any copp-system-class-important

match access-group name copp-system-acl-tacas

match access-group name copp-system-acl-gre

class-map type control-plane match-any copp-system-class-normal

match access-group name copp-system-acl-icmp

match exception ip icmp redirect

match exception ip icmp unreachable

match exception ip option

match redirect arp-inspect

match redirect dhcp-snoop

policy-map type control-plane copp-system-policy

class copp-system-class-critical

police cir 2000 kbps bc 1500 bytes pir 3000 kbps be 1500 bytes conform transmit exceed 
transmit violate drop

class copp-system-class-important

police cir 1000 kbps bc 1500 bytes pir 1500 kbps be 1500 bytes conform transmit exceed 
transmit violate drop

class copp-system-class-normal

police cir 400 kbps bc 1500 bytes pir 600 kbps be 1500 bytes conform transmit exceed 
transmit violate drop

class class-default

police cir 200 kbps bc 1500 bytes pir 300 kbps be 1500 bytes conform transmit exceed 
transmit violate drop

control-plane

service-policy input copp-system-policy

Changing or Reapplying the Default CoPP Policy

This following example shows how to change or reapply the default CoPP policy using the setup utility:

switch# setup

         ---- Basic System Configuration Dialog VDC: 1 ----

This setup utility will guide you through the basic configuration of

the system. Setup configures only enough connectivity for management

of the system.

*Note: setup is mainly used for configuring the system initially,

when no configuration is present. So setup always assumes system

defaults and not the current system configuration values.

Press Enter at anytime to skip a dialog. Use ctrl-c at anytime

to skip the remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no): yes

Do you want to enforce secure password standard (yes/no)[y]: <CR>

  Create another login account (yes/no) [n]: n

  Configure read-only SNMP community string (yes/no) [n]: n

  Configure read-write SNMP community string (yes/no) [n]: n

  Enter the switch name : <CR>

  Enable license grace period? (yes/no) [n]: n

  Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: n

  Configure the default gateway? (yes/no) [y]: n

  Configure advanced IP options? (yes/no) [n]: <CR>

  Enable the telnet service? (yes/no) [n]: y

  Enable the ssh service? (yes/no) [y]: <CR>

    Type of ssh key you would like to generate (dsa/rsa) : <CR>

  Configure the ntp server? (yes/no) [n]: n

  Configure default interface layer (L3/L2) [L3]: <CR>

  Configure default switchport interface state (shut/noshut) [shut]: <CR>

  Configure best practices CoPP profile (strict/moderate/lenient/none) [strict]: strict

  Configure CMP processor on current sup (slot 6)? (yes/no) [y]: n

  Configure CMP processor on redundant sup (slot 5)? (yes/no) [y]: n

The following configuration will be applied:

  password strength-check

  no license grace-period

  no telnet server enable

  no system default switchport

  system default switchport shutdown

  policy-map type control-plane copp-system-policy

Would you like to edit the configuration? (yes/no) [n]: <CR>

Use this configuration and save it? (yes/no) [y]: y

switch#

Default Settings

Table 21-1 lists the default settings for CoPP parameters.

Additional References

For additional information related to implementing CoPP, see the following sections:

•Related Documents

•Standards

Related Documents

Standards

Feature History for CoPP

Table 21-2 lists the release history for this feature.