Configuring a Static or Dynamic IP Demux Subscriber Interface
over Aggregated Ethernet
You can configure a subscriber interface using a static
or dynamic IP demultiplexing (demux) logical interface stacked on
an aggregated Ethernet logical interface. Optionally, you can configure
the aggregated Ethernet logical interface to support one-to-one active/backup
link redundancy or traffic load balancing.
Configuring the Number of Aggregated Ethernet Logical Interfaces
on the Router
To configure the underlying aggregated
Ethernet logical interface for a static or dynamic IP demultiplexing
(demux) subscriber interface:
Define the number of aggregated Ethernet interfaces on
the router:
[edit]
chassis {
aggregated-devices {
ethernet {
device-count number;
}
}
}
Configuring Ethernet Links as Members of an Aggregated Ethernet
Logical Interface for a Static or Dynamic IP Demux Subscriber Interface
To enable Ethernet links as members
of an aggregated Ethernet logical interface that is to serve as the
underlying interface for a static or dynamic IP demux subscriber interface:
For each Ethernet link, specify the aggregated Ethernet
logical interface name, aex. To configure,
include the 802.3ad configuration statement with the aex option at the [edit interfaces ethernet-interface-name fastether-options] or [edit interfaces ethernet-interface-name gigether-options] hierarchy level:
[edit]
interfaces {
ethernet-interface-name { # Configure
the first link
(fastether-options | gigether-options) {
802.3ad aex;
}
}
ethernet-interface-name { # Configure
the second link
(fastether-options | gigether-options) {
802.3ad aex;
}
}
}
Note:
Optionally, you can configure the aggregated Ethernet
logical interface to support one-to-one active/backup link redundancy
or traffic load balancing. For more information about configuring
link protection (for active/backup link redundancy) or configuring
multiple active links (for load balancing), see the JUNOS Network Interfaces Configuration Guide.
Configuring an Aggregated Ethernet Logical Interface to Support
a Static or Dynamic IP Demux Subscriber Interface
To configure an aggregated Ethernet
logical interface so that it can be used as the underlying logical
interface for a static or dynamic IP demux interface:
Enable demultiplexing of incoming traffic to the Ethernet
links based on IPv4 destination or source addresses in the incoming
packets. To configure, include either the demux-destination (Underlying
Interface) configuration statement with the inet option
or the demux-source (Underlying Interface) configuration
statement with the inet option.
Configure the IP address of each link in the aggregated
Ethernet logical interface:
To configure the IP address, include the configuration
statement with the option.
To enable the local address to be derived from the specified
interface, include the unnumbered-address (IP Demux) configuration
statement with the interface-name
<
preferred-source-address address>
option.
You can include these statements at the [edit interfaces
aex unit logical-unit-number] hierarchy level for each Ethernet link.
Note:
IP demux interfaces currently support only the Internet
Protocol version 4 (IPv4) suite (family inet).
[edit]
interfaces {
aex { # Example: ’ae5’
unit logical-unit-number { # Specify
the first link
(demux-destination inet | demux-source inet);
family inet {
(address number | unnumbered-address interface-name
<
preferred-source-address address>
);
}
}
unit logical-unit-number { # Specify
the second link
(demux-destination inet | demux-source inet);
family inet {
(address number | unnumbered-address interface-name
<
preferred-source-address address>
);
}
}
}
}
For general information about configuring an IP demux
underlying interface, or for specific information about configuring
a preferred source address for unnumbered Ethernet or demux interfaces,
see the JUNOS Network Interfaces Configuration Guide.
Configuring a Static IP Demux Subscriber Interface over an
Aggregated Ethernet Logical Interface
To configure a static IP demux subscriber
interface using an appropriately configured aggregated Ethernet logical
interface as the underlying logical interface:
Configure the IP demux interface on a physical device
(of the underlying logical interface) represented by a logical unit
number. To configure, include the unit configuration statement with the interface
unit number at the static [edit interface demux0] hierarchy level.
Specify the underlying interface on which the IP demux
interface is running. To configure, include the underlying-interface configuration
statement with the name of the aggregated Ethernet logical interface
at the static [edit interface demux0unitlogical-unit-numberdemux-options] hierarchy
level.
Specify how ingress IPv4 traffic is to be demultiplexed
based on packet destination or source addresses. To configure, include
either the demux-destination (Demux Interface) or the demux-source statement
(but not both) with one or more logical demultiplexing destination
or source prefixes at the static [edit interface demux0unitlogical-unit-numberfamily inet] hierarchy level. The prefixes are matched
against the destination or source address of packets that the underlying
interface receives. When a match occurs, the packet is processed as
if it was received on the IP demux interface.
(Optional) Specify a filter to apply when a packet is
received or transmitted on the interface. To configure, include the input statement with one input firewall filter name or the output statement with one egress firewall filter name (or both
statements) at the static [edit interface demux0unitlogical-unit-numberfamily inet filter] hierarchy
level.
Note:
IP demux interfaces currently support only the Internet
Protocol version 4 (IPv4) suite (family inet).
For general information about configuring an IP demux
underlying interface, see the JUNOS Network Interfaces Configuration Guide. For
general information about configuring firewall filters, see the JUNOS Policy Framework Configuration Guide.
Configuring a Dynamic IP Demux Subscriber Interface over an
Aggregated Ethernet Logical Interface
To configure a dynamic IP demux subscriber
interface using an appropriately configured aggregated Ethernet logical
interface as the underlying logical interface:
Specify that the router is to configure the IP demux interface
on a physical device (of the underlying logical interface) represented
by a logical unit number obtained from DHCP when the subscriber logs
in. To configure, include the unit configuration statement with the JUNOS internal variable $junos-interface-unit at the [edit dynamic-profiles profile-name interface demux0] hierarchy level.
Specify that the underlying interface on which the IP
demux interface is to run. To configure, include the underlying-interface configuration
statement with the JUNOS internal variable $junos-underlying-interface at the [edit dynamic-profiles profile-name interface demux0unit $junos-interface-unit demux-options] hierarchy level.
Specify that router is to configure the subscriber interface
with an IP address obtained from the DHCP server when the subscriber
logs in. To configure, include the demux-source statement with the JUNOS internal variable $junos-subscriber-ip-address at the [edit dynamic-profiles profile-name interface demux0unitlogical-unit-numberfamily inet] hierarchy
level.
(Optional) Specify a filter to apply when a packet is
received or transmitted on the interface. To configure, include the input statement with one input firewall filter name or the output statement with one egress firewall filter name (or both
statements) at the [edit dynamic-profiles profile-name interface demux0unitlogical-unit-numberfamily inet filter] hierarchy level.
Note:
IP demux interfaces currently support only the Internet
Protocol version 4 (IPv4) suite (family inet).
For general information about configuring firewall filters,
see the JUNOS Policy Framework Configuration Guide.
Displaying Configuration Information About IP Demux Interfaces
over Aggregated Ethernet
To display configuration
information that pertains to IP demux interfaces over aggregated Ethernet,
issue any of the following operational commands:
The output of the show interfaces demux0 (Demux Interfaces) operational
command can display an aggregated Ethernet logical interface as an
underlying interface for an IP demux interface
The output of the show interfaces (Aggregated Ethernet) operational command
can indicate that an aggregated Ethernet logical unit is being used
as an underlying interface for an IP demux interface and displays
the logical demultiplexing destination or source family type. However,
the command output does not display the supported IP demux logical
interface.
