Introduction to the Junos Operating System
Interface Configuration Examples
The slide highlights the topic we discuss next.
www.juniper.net |
Interface Configuration Examples • A–7 |
Introduction to the Junos Operating System
Configuration Examples: Part 1
The slide shows two configuration examples. The first configuration example displays a tagged Ethernet interface with multiple logical interfaces; each logical unit is assigned its respective VLAN ID. The second configuration example shows a serial interface configured with the frame-relay encapsulation. Each logical interface assigned to the serial interface has a corresponding data-link connection identifier (DLCI). Both configuration examples are configured for IPv4 routing, which uses the inet protocol family.
A–8 • Interface Configuration Examples |
www.juniper.net |
Introduction to the Junos Operating System
Configuration Examples: Part 2
The slide shows two configuration examples. The first configuration example displays an Asynchronous Transfer Mode (ATM) interface with a single logical unit and corresponding VCI. Note that this ATM interface configuration example is based on the ATM2 IQ interface. A second ATM interface configuration example is shared in the Using Configuration Groups section, which is based on the ATM1 interface.
The second configuration example on the slide shows a SONET interface configured with Point-to-Point Protocol (PPP) encapsulation and multiple protocol families. We used the iso protocol family for the IS-IS routing protocol, and we used the mpls protocol family for traffic engineering. Both configuration examples are for IPv4 routing, which uses the inet protocol family.
www.juniper.net |
Interface Configuration Examples • A–9 |
Introduction to the Junos Operating System
Configuration Examples: Part 3
The slide highlights a basic Multilink Point-to-Point Protocol (MLPPP) configuration. In this example, two serial interfaces function as member links for the configured bundle. The sample configuration is from the host1-a device.
Continued on the next page.
A–10 • Interface Configuration Examples |
www.juniper.net |
Introduction to the Junos Operating System
Configuration Examples: Part 3 (contd.)
The following is the configuration for the host2-a device:
interfaces { ls-0/0/0 {
unit 0 {
family inet {
address 172.18.37.6/30;
}
}
}
se-1/0/0 { serial-options {
clocking-mode internal;
}
unit 0 {
family mlppp {
bundle ls-0/0/0.0;
}
}
}
se-1/0/1 { serial-options {
clocking-mode internal;
}
unit 0 {
family mlppp {
bundle ls-0/0/0.0;
}
}
}
}
www.juniper.net |
Interface Configuration Examples • A–11 |
Introduction to the Junos Operating System
Configuration Examples: Part 4
The slide illustrates the steps used to configure a link aggregation group (LAG). The first step creates a logical aggregated Ethernet interface. In this example, we created a single aggregated interface, ae0. By default, no aggregated interfaces exist. To create an aggregated interface, simply add an aggregated device under the [edit chassis] hierarchy, as shown in the example on the slide. Once this portion of the configuration is committed, the device creates the ae0 interface. The following is an example that illustrates this behavior:
[edit]
user@router# run show interfaces terse |match ae
[edit]
user@router# edit chassis [edit chassis]
user@router# set aggregated-devices ethernet device-count 1
[edit chassis] user@router# commit commit complete [edit chassis]
user@router# run show interfaces terse |match ae
ae0 up down
Continued on the next page.
A–12 • Interface Configuration Examples |
www.juniper.net |
Introduction to the Junos Operating System
Configuration Examples: Part 4 (contd.)
The next step is to define the parameters associated with the ae0 interface. As shown on the slide, the ae0 interface configuration includes at least one logical unit along with the desired logical interface properties. The example shows the ae0 interface configured as an ethernet switch with three VLANs. The example on the slide also includes the Link Aggregation Control Protocol (LACP) under the aggregated-ether-options hierarchy level. As previously indicated, if LACP is used, at least one side must be configured in active mode to successfully establish the connection.
Note that LAG support and configuration varies between the different Junos devices. For support information, always refer to the technical documentation for your specific product.
www.juniper.net |
Interface Configuration Examples • A–13 |