Configuring Next-Hop Groups to Use Multiple Interfaces to Forward Packets Used in Port Mirroring
Next-hop groups allow you to include multiple interfaces used to forward duplicate packets used in port mirroring.
To configure a next-hop group, include the next-hop-group statement at the [edit forwarding-options] hierarchy
level:
[edit forwarding-options] next-hop-group [ group-names ] { interface interface-name { next-hop [ addresses ]; } }
or
[edit forwarding-options port-mirroring family inet6 output] next-hop-group group-name{ group-type inet6; interface interface-name { next-hop ipv6-address; } next-hop-subgroup group-name{ interface interface-name { next-hop ipv6-address; } } }
You can specify one or more group names. To configure the interface
that sends out sampled information, include the interface statement and specify an interface. To specify a next-hop address
to send sampled information, include the next-hop statement
and specify an IP address.
Next-hop groups have the following restrictions:
Starting with release 14.2, next-hop groups are supported for M Series and MX Series routers only.
Next-hop groups support up to 16 next-hop addresses.
You can configure up to 30 next-hop groups.
Each next-hop group must have at least two next-hop addresses.
When a firewall filter with next-hop-group action is applied on an interface in egress, the redirected copy does not retain any packet headers added while forwarding the packet to that interface. For example, if a filter with action next-hop-group is applied in egress of a GRE interface, the redirected copies received on the next-hop-group member interfaces do not contain a GRE header.
Next-hop groups can be used for port mirroring.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.