Table of Contents
Advertisement
JUNOSe 10.0.3 Release Notes
System Logging
TCP
Unified ISSU
50
Known Problems and Limitations
If your router is in Manual Commit mode, then you must issue the write
memory command before you perform an SRP module switch or a manual
reload. You must do this even when you have made no changes to the system
configuration and the file systems are synchronized. [Defect ID 44469]
The show configuration category management syslog virtual-router default
command incorrectly displays logs for multiple syslog destinations when you
add a log to only one syslog destination. The show log configuration
command shows the correct configuration. [Defect ID 84082]
The SRP module resets in any of the following circumstances on an E320
router that has a line module configured with 5000 ANCP adjacencies: [Defect
ID 176916]
When you issue the issu initialization command from the console and
then reload the line module from a Telnet session.
When the client that has the 5000 ANCP clients resets or an intermediate
switch resets.
When you reload the line module.
ATM line modules might reset after a unified ISSU when you attempt to add
memory to a VLAN subinterface in a large bridged Ethernet configuration.
[Defect ID 178798]
Unified ISSU is not supported with 8000 bridged Ethernet interfaces on an
OC3/STM1 GE/FE ATM line module. [Defect ID 179547]
When any of the subsystems is excluded for a JUNOSe release, a unified ISSU
to that release fails to apply conversion code to all of the line modules. As a
result, the line modules reset when they come up with that release. [Defect ID
179595]
Work-around: To prevent the exclusion of a subsystem file from the release,
do the following before you upgrade to a new JUNOSe release that supports
unified ISSU:
1. Issue the show subsystems file fileName.rel command, where fileName is
the name of the software release file, to determine whether any of the
subsystem files are excluded from the release.
2. For each subsystem file that is excluded, issue the no exclude-subsystem
subsystemName command to remove the exclusion for the specified
subsystem file.
If you copied the software release to the router before removing the subsystem
file from the exclusion list, you must copy the release to the router again to
ensure that all subsystem files are included in the release.
Advertisement
Table of Contents
