JunosE 10.3.2 Release Notes
34
Known Behavior
In a router with a redundancy group that does not span quadrants (for example,
a three-slot redundancy group that spans slots 0, 1, and 2 in an ERX1410
chassis), the potential bandwidth of the redundant module is erroneously
included in the quadrant bandwidth calculation. The
show utilization
command might indicate that the bandwidth is exceeded for modules in that
group. [Defect ID 31034]
When you copy the running configuration to NVS, the E Series router verifies
whether it has available space equal to at least twice the size of the .cnf file. If
the space is insufficient, you cannot complete the copy. [Defect ID 40655]
Work-around:
Make sufficient space on the NVS by deleting .rel or .cnf files.
You cannot delete the ipInterface log after you delete the corresponding IP
interface. This does not prevent you from adding filters to other interfaces, nor
does it prevent you from adding a filter to the same interface if you re-create it
after deletion. [Defect ID 34842/45063]
Work-around:
Remove the filter before you remove the interface. Alternatively,
if you remove the interface first, then you must remove all filters associated
with all IP interfaces.
System Logging
If you enable engineering logs and set the control network logs to a level of
notice or lower (down from the default of error), you might see erroneous
controlNetwork log messages like the following that are generated because
SNMP polling on line modules (correctly) detects no fabric: [Defect ID 43168]
NOTICE 09/01/2002 18:47:52 CEST controlNetwork (slot 11): Control Bus
Master slave error 0x5 while accessing slot
Tunneling
When you configure the GE-2 line module, the GE-HDE line module, or the
ES2-S1 GE-4 IOA to operate as a shared tunnel-server module, the available
bandwidth for tunnel services is limited to 0.5 Gbps per module.
In releases numbered lower than Release 7.3.0, a dynamic tunnel-server port
was located on port 8 of the GE-HDE line module and GE-8 I/O module.
In Release 7.3.0 and higher-numbered releases, the dynamic tunnel-server port
is located on port 9. When you upgrade to Release 7.3.0, any existing
tunnel-server port configurations move from port 8 to port 9.
