Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All
Example: HTTP Service Attached to a Dynamic Interface
A dynamic service attachment uses a dynamic profile. In the following dynamic profile example, the name of the service set can be populated dynamically for each subscriber at instantiation time. This dynamic profile encapsulates a service attachment point associated with a statically preprovisioned service set sset-1.
dynamic-profiles {profile prof-2 { # parameterized service attachmentinterfaces {$junos-interface-ifd-name {unit $junos-interface-unit {family inet {service {input {service-set $junos-service-set service-filter $junos-service-filter;post-input-filter $junos-post-input-filter ;}output {service-set $junos-service-set;}}}}}}}}
To handle scalability more efficiently, in the following example the name of the service set can be populated dynamically for each subscriber at instantiation time.
dynamic-profiles {profile prof-2 { # parameterized service attachmentinterfaces {$junos-interface-ifd-name {unit $junos-interface-unit {family inet {service {input {service-set $junos-service-set service-filter $junos-service-filter;post-input-filter $junos-post-input-filter ;}output {service-set $junos-service-set;}}}}}}}}
The following attaches a service set dynamically at family inet6:
dynamic-profiles {profile prof-1 {interfaces {$junos-interface-ifd-name {unit $junos-interface-unit {family inet6 {service {input {service-set sset-1 service-filter fltr-1;post-input-filter pfltr-1 ;}output {service-set sset-1 service-filter fltr-1;}}}}}}}}
