[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Ethernet Physical Interface Properties

To configure Fast Ethernet-specific physical interface properties, include the fastether-options statement at the [edit interfaces fe-fpc/pic/port] hierarchy level:

[edit interfaces fe-fpc/pic/port]
link-mode (full-duplex | half-duplex);
speed (10m | 100m);
vlan-tagging;
fastether-options {
802.3ad aex (primary | backup);
(flow-control | no-flow-control);
ignore-l3-incompletes;
ingress-rate-limit rate;
(loopback | no-loopback);
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}

Note: The speed statement applies to the management Ethernet interface (fxp0), the Fast Ethernet 12-port and 48-port Physical Interface Card (PIC) interfaces, the J-series Gigabit Ethernet uPIM interfaces and the MX-series Tri-Rate Ethernet copper interfaces. The Fast Ethernet and fxp0 interfaces can be configured for 10 Mbps or 100 Mbps (10m | 100m). The J-series Gigabit Ethernet uPIM interfaces and the MX-series Tri-Rate Ethernet copper interfaces can be configured for 10 Mbps, 100 Mbps, or 1 Gbps (10m | 100m | 1g). The 4-port and 8-port Fast Ethernet PICs support a speed of 100 Mbps only.

To configure physical interface properties specific to Gigabit Ethernet and 10-Gigabit Ethernet, include the gigether-options statement at the [edit interfaces ge-fpc/pic/port] or [edit interfaces xe-fpc/pic/port] hierarchy level:

[edit interfaces ge-fpc/pic/port]
gigether-options {
802.3ad aex (primary | backup);
auto-negotiation | no-auto-negotiation) remote-fault <local-interface-online | local-interface-offline>
(flow-control | no-flow-control);
ignore-l3-incompletes;
(loopback | no-loopback);
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}

Additionally, for 10-Gigabit Ethernet DWDM-specific physical interface properties, include the optics-options statement at the [edit interfaces ge-fpc/pic/port] hierarchy level:

[edit interfaces ge-fpc/pic/port]
optics-options {
wavelength nm;
}

To configure Gigabit Ethernet IQ-specific physical interface properties, include the gigether-options statement at the [edit interfaces ge-fpc/pic/port] hierarchy level. These statements are supported on 10-Gigabit Ethernet IQ2 PIC. Some of these statements are also supported on Gigabit Ethernet PICs with small form-factor pluggable transceivers (SFPs) (except the 10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port on the M7i platform). For more information, see Example: Configuring Gigabit Ethernet Interfaces.

[edit interfaces ge-fpc/pic/port]
flexible-vlan-tagging;
gigether-options {
802.3ad aex (primary | backup);
auto-negotiation | no-auto-negotiation) remote-fault <local-interface-online | local-interface-offline>
(flow-control | no-flow-control);
ignore-l3-incompletes;
(loopback | no-loopback);
(source-filtering | no-source-filtering);
ethernet-switch-profile {
(mac-learn-enable | no-mac-learn-enable);
tag-protocol-id [tpids ];
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [values ];
}
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
}
}
}
native-vlan-id number;
}

To configure 10-Gigabit Ethernet IQ2-specific physical interface properties, include the lan-phy or wan-phy statement at the [edit interfaces xe-fpc/pic/port framing] hierarchy level. For more information, see Configuring 10-Gigabit Ethernet Framing.

[edit interfaces]
xe-0/0/0 {
framing {
(lan-phy | wan-phy);
}
}

To configure OAM 802.3ah support for Ethernet interfaces, include the oam statement at the [edit protocols] hierarchy level.

oam {
ethernet {
link-fault-management {
interfaces {
interface-name{
pdu-interval interval;
link-discovery (active | passive);
pdu-threshold count;
}
}
}
}
}

To configure Gigabit Ethernet IQ-specific logical interface properties, include the input-vlan-map, output-vlan-map, and layer2-policer statements:

input-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
output-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;

You can include these statements at the following hierarchy levels:

To configure aggregated Ethernet-specific physical interface properties, include the aggregated-ether-options statement at the [edit interfaces aex] hierarchy level:

[edit interfaces aex]
aggregated-ether-options {
ethernet-switch-profile {
tag-protocol-id tpid;
}
(flow-control | no-flow-control);
lacp mode {
periodic interval;
}
link-protection;
link-speed speed;
(loopback | no-loopback);
minimum-links number;
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
[Contents] [Prev] [Next] [Index] [Report an Error]

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.