Configuring the Address and Domain for Services Interfaces
On the AS or Multiservices PIC, you configure a source address
for system log messages by including the address statement
at the [edit interfaces interface-name unit logical-unit-number family inet] hierarchy level:
address address { ... }
Assign an IP address to the interface by configuring the address value. The AS or Multiservices
PIC generally supports only IP version 4 (IPv4) addresses configured
using the family inet statement, but IPsec services support
IP version 6 (IPv6) addresses as well, configured using the family inet6 statement.
If you configure the same address on multiple interfaces in the same routing instance, Junos OS uses only the first configuration, the remaining address configurations are ignored and can leave interfaces without an address. Interfaces that do not have an assigned address cannot be used as a donor interface for an unnumbered Ethernet interface.
For example, in the following configuration the address configuration of interface xe-0/0/1.0 is ignored:
interfaces {
xe-0/0/0 {
unit 0 {
family inet {
address 192.168.1.1/24;
}
}
}
xe-0/0/1 {
unit 0 {
family inet {
address 192.168.1.1/24;
}
}
}
For more information on configuring the same address on multiple interfaces, see Configuring the Interface Address.
For information on other addressing properties you can configure that are not specific to service interfaces, see the Junos OS Network Interfaces Library for Routing Devices.
The service-domain statement specifies whether the
interface is used within the network or to communicate with remote
devices. The software uses this setting to determine which default
stateful firewall rules to apply, and to determine the default direction
for service rules. To configure the domain, include the service-domain statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level:
service-domain (inside | outside);
If you are configuring the interface in a next-hop service-set
definition, the service-domain setting must match the configuration
for the inside-service-interface and outside-service-interface statements; for more information, see Configuring Service Sets to be Applied to Services
Interfaces.