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

Interface and Next-Hop Service Sets

There are two types of service sets: interface and next-hop. Interface service sets must be attached to media interfaces to direct traffic to the PIC, and they apply to all packets entering and leaving the PIC. After the service set is applied, packets can be reinjected back to the Packet Forwarding Engine for regular forwarding.

When a service set cannot be attached to an interface, use a next-hop service set.

Example: Interface Service Set

The following service set can be attached to any media interface of family type inet:



[edit]
services {


service-set sset1 {


extension-service jnx-flow {

provider-specific rules;
}


# Existing hierarchy


interface-service {
service-interface { # Indicates service set is an interface
service set
ms-x/y/0.0; # Specifies which PIC to install this policy
on
}


}


}

To associate a defined service set with an interface, include the service-set statement at the [edit interfaces interface-name unit logical-unit-number family inet service (input | output)] hierarchy level. The following configuration attaches the service set sset1 to the media interface ge-0/0/0.0:



[edit]
# Existing hierarchy
interfaces {


ge-0/0/0 {


unit 0 {


family inet {


service {


input {
service-set sset1;   # Attach service set to input
}




output {
service-set sset1;   # Attach service set to output
}


}


}


}


}


}

Example: Next-Hop Service Set

In the following example, the service set sset1 cannot be attached to an interface; instead, two routes are added to direct traffic to the PIC:



[edit]
services {


service-set sset1 {


extension-service jnx-flow {

provider-specific rules;
}


# Existing hierarchy


next-hop-service { # Indicates service set is a next-hop
service set
inside-service-interface ms-1/2/0.0;
outside-service-interface ms-1/2/0.1;
}


}


}

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