CloudLabBox
Try the free demo

CCNP ENARSI lab 27 of 35

Control plane policing

Classify everything that reaches a router's own CPU into routing, management, ICMP, unwanted and default traffic, police each class, and prove that a ping flood and telnet attempts from a guest network no longer threaten OSPF, BGP or SSH.

Run this lab

It needs Lite: its 3 nodes are set to 3 vCPU and 1,536 MB in total. That fits the free demo too.

In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 27 - Control plane policing

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Advanced
Time
About 70 minutes
Nodes need
3 vCPU, 1,536 MB
Smallest plan
Lite

The scenario

Kestrel Hotels' core router R1 runs OSPF and eBGP with R2 and is managed from the core network (10.27.12.0/24). It also routes the guest network, where a misbehaving device (R3) floods R1 with large pings and hammers it with telnet and web connection attempts. Last week a flood pushed R1's CPU so high that OSPF and BGP dropped. Your task: protect R1's control plane so routing and management survive anything the guest network sends.

DeviceInterfaceAddressNotes
R1Gi0/010.27.12.1/24core: OSPF and eBGP (AS 65001 ↔ 65002) with R2
R1Gi0/110.27.13.1/24guest network
R2Gi0/0 / Lo110.27.12.2/24 / 172.16.2.1/24core router and management station
R3Gi0/010.27.13.3/24guest device

R1 has a local user admin / Admin-Pass1, telnet and SSH on VTY, SNMP community Kestrel-RO, and HTTP/HTTPS servers.

What you’ll practise

  • Explain what the control plane is and why it needs its own policy
  • Classify routing (OSPF, BGP, EIGRP), management (SSH, Telnet, HTTPS, SNMP), ICMP and unwanted traffic with ACLs and class maps
  • Police and drop per class in a policy map applied to the control plane
  • Read show policy-map control-plane counters and tune the policy

The tasks

  1. Prepare SSH and look at the threat
  2. Classify control-plane traffic
  3. Police each class and apply the policy
  4. Attack again and read the counters

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Control plane policing3 nodes, 2 links. Every link is listed as text below the diagram.R1R2R3Gi0/0Gi0/0Gi0/1Gi0/0
3 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R2 Gi0/0 to R1 Gi0/0
  • R1 Gi0/1 to R3 Gi0/0
Nodes in Control plane policing, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R3Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder CCNP ENARSI 300-410 guided labs.

  3. Open 27 - Control plane policing and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More CCNP ENARSI labs

All CCNP ENARSI labs

Related labs in other courses

CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.