[Contents] [Prev] [Next] [Index] [Report an Error]

Option: Sending Traffic to Multiple Export Interfaces by Using Next-Hop Groups

To send port-mirrored traffic to multiple flow servers or packet analyzers, you can use the next-hop-group statement. The routing platform can make up to 16 copies of traffic per group and send the traffic to the next-hop group members you configure. A maximum of 30 groups can be configured on a routing platform at any given time. The port-mirrored traffic can be sent to any interface, except aggregated SONET/SDH, aggregated Ethernet, loopback (lo0), or administrative (fxp0) interfaces. To configure multiple port mirroring with next-hop groups, include the next-hop-group statement at the [edit forwarding-options] hierarchy level.

You must port-mirror the initial traffic to a tunnel interface so that it can be filtered and duplicated. Also, you need configure only the interface names for point-to-point interfaces, but you must configure the interface names and a next hop for multipoint interfaces (such as Ethernet).



[edit]
forwarding-options {


port-mirroring {


family inet {


input {
rate 1;
}




output {
interface vt-3/3/0.1;
no-filter-check;
}


}


}




next-hop-group ftp-traffic {
interface so-4/3/0.0;
interface so-0/3/0.0;
}




next-hop-group http-traffic {


interface ge-1/1/0.0 {
next-hop 10.12.1.2;
}




interface ge-1/2/0.0 {
next-hop 10.13.1.2;
}


}




next-hop-group default-collect {
interface so-7/0/0.0;
interface so-7/0/1.0;
}


}

Note: Next-hop groups are supported on M-series routers only, except the M120 router and the M320 router.

[Contents] [Prev] [Next] [Index] [Report an Error]