SCU Configuration

Configuring SCU

Figure 1: SCU Topology Diagram

Figure 1 shows a basic SCU configuration with three routers. Source routers A and B use loopback addresses as the prefixes to be monitored. Most of the configuration tasks and actual monitoring occurs on transit Router SCU.

Begin your configuration on Router A. The loopback address on Router A contains the origin of the prefix that is to be assigned to source class A on Router SCU. However, no SCU processing happens on this router. Therefore, configure Router A for basic OSPF routing and include your loopback interface and interface so-0/0/2 in the OSPF process.

Router A:

Router SCU handles the bulk of the activity in this example. On Router SCU, enable source class usage on the inbound and outbound interfaces at the [edit interfaces interface-name unit unit-number family inet accounting] hierarchy level. Make sure you specify the expected traffic: input, output, or, in this case, both.

Next, configure a route filter policy statement that matches the prefixes of the loopback addresses from routers A and B. Include statements in the policy that classify packets from Router A in one group named scu-class-a and packets from Router B in a second class named scu-class-b. Notice the efficient use of a single policy containing multiple terms.

Last, apply the policy to the forwarding table.

Router SCU

Complete the configuration tasks on Router B. Just as Router A provides a source prefix, Router B’s loopback address matches the prefix assigned to scu-class-b on Router SCU. Again, no SCU processing happens on this router, so configure Router B for basic OSPF routing and include your loopback interface and interface so-0/0/4 in the OSPF process.

Router B:

Verifying Your Work

To verify that SCU is functioning properly, use the following commands:

• show interfaces interface-name statistics

• show interfaces interface-name (extensive | detail)

• show route (extensive | detail)

• show interfaces source-class source-class-name interface-name

• clear interface interface-name statistics

You should always verify SCU statistics at the outbound SCU interface on which you configured the output statement. You can perform the following three steps to check the functionality of SCU:

1. Clear all counters on your SCU-enabled router and verify that they are empty.

2. Send a ping from one edge router to another edge router to generate SCU traffic across the SCU-enabled router.

3. Verify that the counters are incrementing correctly on the outbound interface.

The following section shows the output of these commands as used with the configuration example.