JunosE 11.0.2 Release Notes
24
Known Behavior
When you upgrade from certain releases to JunosE Release 9.2.0p1-0 or
higher-numbered releases, descriptions configured for IP interfaces or IP
subinterfaces are not retained across the upgrade when the descriptions are
shorter than 9 characters in length. Additionally, VRF descriptions are not
retained across the upgrade when the combined length of the VRF description
and the VRF name is shorter than 9 characters. This behavior is seen during
upgrades using a reload, stateful SRP switchover, or unified ISSU. Upgrades
from the following releases are affected by this behavior:
7.x.x
8.0.x
8.1.x, 8.2.x, and 9.x.x builds created before July 23, 2008
Examples of descriptions that are not retained across the upgrade:
host1(config-if)#
ip description 12345678
host1(config)#
ip vrf 123
host1(config-vrf)#
description 45678
Examples of descriptions that are retained across the upgrade:
host1(config-if)#
ip description longdescription
host1(config)#
ip vrf longername
host1(config-vrf)#
description 45678
host1(config)#
ip vrf 123
host1(config-vrf)#
description longdescription
Work-around:
Before you upgrade from an affected release to JunosE Release
9.2.0p1-0 or higher-numbered releases, ensure that you do the following:
Change IP interface and subinterface descriptions to 9 or more characters.
Change VRF descriptions, VRF names, or both so that the combination of
associated VRF names and descriptions consists of 9 or more characters.
When you issue the
show ip forwarding-table
command for a particular slot, it
is normal and appropriate behavior when the Status field indicates Valid while
the Load Errors field is increasing daily for that VR. The Load Errors field
records any failed routing table distribution attempt as an error. Attempts can
fail for many reasons during normal operation; a failed attempt does not
necessarily indicate a problem. It is normal to see many load errors per day. If
the Status field indicates Invalid, then the routing table distribution has failed
constantly for that VR and a real problem exists. You might occasionally see a
status of Updating. However, if the Status field always indicates Updating, then
again the routing table distribution has failed constantly for that VR, and a real
problem exists.
