Creating DTCP ENABLE Messages to Trigger a Drop Policy
Creating DTCP DISABLE Messages to Remove a Drop Policy
Creating DTCP ADD Messages to Trigger Traffic Mirroring
Creating DTCP ENABLE Messages to Trigger Traffic Mirroring
Using LIST Messages to Verify That Subscriber Traffic Is Being Mirrored
Using DELETE Messages to Remove Traffic Mirroring Triggers
Verifying That Traffic Mirroring Was Stopped on the Subscriber Interfaces

Example: Using DTCP Messages to Trigger, Verify, and Remove Traffic Mirroring for Subscribers

This example shows how to create DTCP messages to do the following:

Trigger a drop policy if one does not already exist.
Remove an existing drop policy.
Trigger traffic mirroring for two subscribers based on interface ID.
Verify that subscriber traffic on the two interfaces is being mirrored.
Remove traffic mirroring on the two subscriber interfaces.
Verify that traffic mirroring was stopped on the two subscriber interfaces.

In this example, SSH is being used to communicate with the router.

Creating DTCP ENABLE Messages to Trigger a Drop Policy

This section shows the DTCP attributes used in ENABLE messages to cause the router to trigger a drop policy if one does not already exist from a prior DTCP ADD or DTCP ENABLE command.

Creating DTCP DISABLE Messages to Remove a Drop Policy

This section shows the DTCP attributes used in DISABLE messages to cause the router to remove an existing a drop policy created with a prior DTCP ENABLE command.

Creating DTCP ADD Messages to Trigger Traffic Mirroring

This section shows examples of DTCP ADD messages on a mediation device that use the interface ID to trigger traffic mirroring on interfaces demux0.30010002 and demux0.30010001.

Creating DTCP ENABLE Messages to Trigger Traffic Mirroring

This section shows the DTCP attributes used in ENABLE messages to cause the router to trigger a drop policy if one does not already exist from a prior DTCP ADD or DTCP ENABLE command.

Using LIST Messages to Verify That Subscriber Traffic Is Being Mirrored

This section shows examples of a LIST message on the mediation device. The LIST message requests information about the subscribers being mirrored. The information is returned in a LIST response. The response shows that traffic for the two interfaces—demux0.30010002 and demux0.30010001—is being mirrored.

Using DELETE Messages to Remove Traffic Mirroring Triggers

This section shows examples of DELETE messages used to remove traffic mirroring triggers on demux0.30010001 and demux0.30010002. DTCP DELETE can use either Criteria-ID to delete only that criteria or Cdest-ID to delete everything with cdest-ID that you previously created.

Verifying That Traffic Mirroring Was Stopped on the Subscriber Interfaces

This section shows an example of a LIST message used to show that traffic mirroring on demux0.30010001 and demux0.30010002 is removed.

ON THIS PAGE