vPC peer link with no separate peer keepalive
At a glance
Base severity
Area
Platform
Evidence level
Benchmark reference
Reads the export, not the device
ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.
Why it matters
Without a keepalive on a path of its own, a failed peer link leaves each switch unable to tell a dead peer from a broken link, and both can keep forwarding as primary.
How to fix it
Web interface
The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.
- Configure peer-keepalive under the vPC domain, on the management VRF or a VRF of its own, between the two switches' management addresses.
Command line
Cisco IOS-XE CLI
configure terminalvpc domain <domain-id>peer-keepalive destination <peer-mgmt-ip> source <own-mgmt-ip> vrf managementendwrite memory
An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. Typed in configuration mode; copy running-config startup-config saves it, with no separate commit. Read every line first.
Read it back
show vpc peer-keepaliveValues to fill in3
- <domain-id>
- The vPC domain number
- <peer-mgmt-ip>
- The peer switch's management address
- <own-mgmt-ip>
- This switch's management address
Before you type it1
- Written from the Cisco IOS-XE 17 and NX-OS 9 and 10 command references and not run on a device: read each line before you paste it.
How to confirm the fix
- On the Nexus (read only): show vpc peer-keepalive, and confirm the keepalive is alive on the expected VRF.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Interfaces and Segmentation
- SW-SEC-006Edge ports without BPDU guard
- SW-SEC-007Ports negotiating trunking (DTP)
- SW-SEC-008Trunk native VLAN is VLAN 1
- SW-SEC-009Trunk carries every VLAN
- SW-SEC-010User ports in the default VLAN
- SW-SEC-011DHCP snooping not enabled
- SW-SEC-012Dynamic ARP inspection not enabled
- SW-SEC-016VTP in server or client mode
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.