Avoiding Conflicts Between Multiple Packet Mirroring Configurations

The JunosE Software gives you a great deal of flexibility in creating your packet mirroring environment by supporting both the CLI-based and the RADIUS-based configuration methods. However, a conflict might occur when you use both methods. For example, a given subscriber might be targeted by both a CLI-based configuration and a RADIUS-based configuration. The rival configurations might use the same trigger to identify the subscriber, or they might use different triggers.

The configuration method that is applied to the subscriber depends on several variables: the trigger, when the packet mirroring configuration is created, and when the subscriber logs in. The following considerations apply to multiple packet mirroring configurations.

Consider the following scenarios.

Scenario 1: When Configurations Use the Same Identification Criteria

  1. Currently logged-in subscribers are not being mirrored. These subscribers include 20 subscribers with the username joe@example.com. Their subscriber access is through virtual router boston1.
  2. You create a RADIUS COA (RADIUS-initiated) configuration that targets subscribers that match joe@example.com logging in through virtual router boston1.
  3. Mirroring begins for all 20 of these subscribers.
  4. Ten more subscribers with the username joe@example.com log in through VR boston1. None of these new subscribers is mirrored because the RADIUS COA configuration makes no persistent rules.
  5. You create a CLI configuration to mirror subscribers with username joe@example.com logging in through VR boston1.
  6. All 30 of these subscribers are now mirrored. The CLI configuration expands the RADIUS COA configuration because both configurations use the same identification criteria. The original mirrored users continue to be mirrored based on the COA configuration; the new users are mirrored based on the CLI configuration.
  7. You delete the CLI configuration while the subscribers are still logged in and being mirrored. The deletion has no effect on these subscribers; mirroring continues as before the deletion.

Scenario 2: When Configurations Use Different Identification Criteria

  1. Currently logged-in subscribers are not being mirrored. These subscribers include 20 subscribers with the username joe@example.com. Their subscriber access is through virtual router boston1.

    The subscribers have been assigned IP addresses 10.1.1.1 through 10.1.1.20.

  2. You create a RADIUS COA (RADIUS-initiated) configuration that targets the subscriber that matches IP address 10.1.1.5 and VR boston1.
  3. This subscriber is mirrored.
  4. You create a CLI configuration to mirror subscribers with username joe@example.com logging in through VR boston1.
  5. No additional subscribers are mirrored because one subscriber that matches that group (username and VR) is already being mirrored by another identification criterion (IP address and VR).

Related Documentation