Modifying the Physical Interfaces Configuration for Security Devices
You can use the Physical Interfaces section on the Modify Configuration page to view and modify physical interfaces on the device. You can also view, add, modify, or delete logical interfaces associated with the physical interfaces.
Refer to the Junos OS documentation (available at http://www.juniper.net/documentation/en_US/release-independent/junos/information-products/pathway-pages/junos/product/) for a particular release and device. There you can find detailed information on the configuration parameters for that device.
To modify physical interfaces:
Action |
Guideline |
---|---|
Modify a physical interface |
Select a physical interface and click the pencil icon. The Edit Physical Interface page appears. You can modify some of the fields on this page. See Table 2 for an explanation of the fields. After you have modified the physical interface, click OK. The changes are saved and you are returned to the Physical Interfaces section on the Modify Configuration page. |
View or configure the logical interfaces associated with a physical interface |
View or configure the logical interfaces associated with a physical interface by clicking the View/Configure link in the Logical Interfaces column. The Logical Interfaces page appears, displaying the list of logical interfaces associated with the physical interface. You can perform the following actions on this page:
|
Setting |
Guideline |
---|---|
Basic Information |
|
Description |
Enter the description of the physical interface. We recommend that you enter a maximum of 255 characters. |
MTU |
Specify the maximum transmission unit (MTU) on the physical interface. Range: 256 through 9216 |
Speed |
Select the speed (in MBps) at which the data transfer occurs in the interface. |
Advanced Options |
|
Enable VLAN Tagging |
Select this check box to enable VLAN tagging for the physical interface or clear the check box to disable VLAN tagging for the physical interface. |
Setting |
Guideline |
---|---|
Basic Information |
|
Name |
Enter the name of the logical interface, which must be a number from 0 through 2,147,483,647. |
Description |
Enter the description of the logical interface. We recommend that you enter a maximum of 255 characters. |
VLAN ID |
Enter the VLAN ID for the 802.1q VLAN tags. Range: 0 through 4096. |
IPv4 Address |
|
You can do the following:
|
|
IPv6 Addresses |
|
You can do the following:
|
Setting |
Guideline |
---|---|
IP Address |
Enter an IPv4 address for the logical interface. |
Subnet |
Enter the subnet for the IPv4 address. |
Primary |
Select this check box to specify that the IPv4 address is the primary address of the protocol on the logical interface. If the logical unit has more than one IP address, the primary IP address is used by default as the source address when packet transfer originates from the interface and the destination address does not indicate the subnet. |
Preferred |
Select this check box to specify that the IPv4 address is the preferred address for the logical interface. If you configure more than one IP address on the same subnet, the preferred source address is chosen by default as the source address when you initiate frame transfers to destinations on the subnet |
Setting |
Guideline |
---|---|
IP Address |
Enter an IPv6 address for the logical interface. |
Subnet |
Enter the subnet for the IPv6 address. Range: 0 through 128 |
Primary |
Select this check box to specify that the IPv6 address is the primary address of the protocol on the logical interface. If the logical unit has more than one IP address, the primary IP address is used by default as the source address when packet transfer originates from the interface and the destination address does not indicate the subnet. |
Preferred |
Select this check box to specify that the IPv6 address is the preferred address for the logical interface. If you configure more than one IP address on the same subnet, the preferred source address is chosen by default as the source address when you initiate frame transfers to destinations on the subnet |