Dynamic Interfaces; Ethernet - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - RELEASE NOTES 2010-11-09 Release Note

JunosE 11.3.0 Release Notes

Dynamic Interfaces

Ethernet

22 Known Behavior
Work-around: You can eliminate this issue by modifying any one of these conditions.
For example, this issue does not exist with any of the following configuration
modifications:
 Configure DHCP external server and either DHCP relay or relay proxy in the same
virtual router.
 Configure the client-facing and server-facing interfaces for DHCP external server
and either DHCP relay or relay proxy on the same ES2 10G LM instead of the
same ES2 4G LM.
 Configure the client-facing and server-facing interfaces for DHCP external server
and either DHCP relay or relay proxy on separate ES2 4G LMs.
Dynamic IPv6 interfaces over static PPP interfaces are not supported.

The hashing algorithm that selects the LAG member link is associated with the IP

address of the subscriber client to support QoS. Consequently, a particular flow is
always hashed to the same link. When a member link is removed from a LAG bundle,
traffic rate is disrupted and traffic flow is reduced. When the link goes down and then
comes back up, the traffic flow is automatically redistributed.
When counting bits per second on a Fast Ethernet or Gigabit Ethernet interface, an E

Series router includes 12 bytes for interpacket gap, 7 bytes for preamble, and 1 byte
for start frame delimiter, for a total of 20 bytes (160 bits) per packet more than some
non–E Series routers. This value therefore shows the total bandwidth utilization on
the interface, including both data and overhead.
Support for the 0x9200 S-VLAN Ethertype has been removed. You can no longer

specify the 9200 option with the svlan ethertype command.
When you upgrade to Release 7.1.0 or higher-numbered release, the software
automatically transfers existing configurations that use the 0x9200 Ethertype to the
0x88a8 Ethertype.
The show interface gigabitEthernet command output does not display the following

line of output for Gigabit Ethernet modules that do not support SFPs, such as the GE
Single Mode I/O module and GE I/O Multi Mode I/O modules:
Primary/Secondary link signal detected
Primary/Secondary link signal not detected
To bridge unicast known-DA packets at line rate on both 2-Gbps ports of the GE-2

line module or the GE-HDE module when paired with the GE-2 SFP I/O module, the
minimum packet size must be at least 144 bytes.
When installed in the ERX1440 router, the GE-2 module delivers full bandwidth of
4 GB per line module (2 GB at the ingress and 2 GB at the egress) only when installed
in slot 2 or slot 4, and when the SRP-40G+ module is used in the router. When
installed in any other ERX1440 slot, the GE-2 module delivers a maximum bandwidth
of 2 GB per line module (1 GB maximum at the ingress and 1 GB maximum at the
egress). Therefore, of the maximum 24 possible ports for the module in an ERX1440
chassis (that is, two ports in each of 12 slots), full bandwidth is delivered only on a
maximum of four ports (those in slots 2 and 4).
Copyright © 2010, Juniper Networks, Inc.