Check Your Work
To verify that SCU is functioning properly in the Layer 3 VPN, use the following commands:
show interfacesinterface-namestatisticsshow interfaces source-classsource-class-name interface-nameshow interfacesinterface-name(extensive | detail)show route (extensive | detail)clear interfaceinterface-namestatisticsYou should always verify SCU statistics at the outbound SCU interface on which you configured the
outputstatement. To check SCU functionality, follow these steps:
- Clear all counters on your SCU-enabled router and verify they are empty.
- Send a ping from the ingress CE router to the second CE router to generate SCU traffic across the SCU-enabled VPN route.
- Verify that the counters are incrementing correctly on the outbound interface.
The following section shows the output of these commands used with the configuration example.
Step One:
Clear the Counters
user@pe2> clear interfaces statistics alluser@pe2>show interfaces so-0/0/0.0 statisticsLogical interface so-0/0/0.0 (Index 6) (SNMP ifIndex 113)Flags: Point-To-Point SNMP-Traps Encapsulation: PPPProtocol inet, MTU: 4470Source class Packets BytesGOLD1 0 0Addresses, Flags: Is-Preferred Is-Primaryuser@pe2>show interfaces source-class GOLD1 so-0/0/0.0Protocol inetSource class Packets BytesGOLD1 0 0Step Two:
Ping from the Edge Router
user@ce1> ping 10.20.253.2 source 10.114.1.1 rapid count 10000Step Three:
Verify the Counters
user@scu>show interfaces source-class GOLD1 so-0/0/0.0Protocol inetSource class Packets BytesGOLD1 20000 1680000user@scu>show interfaces so-0/0/0.0 statisticsLogical interface so-0/0/0.0 (Index 6) (SNMP ifIndex 113)Flags: Point-To-Point SNMP-Traps Encapsulation: PPPProtocol inet, MTU: 4470Source class Packets BytesGOLD1 20000 1680000Addresses, Flags: Is-Preferred Is-PrimaryDestination: 10.20.253/24, Local: 10.20.253.1