■
If the MSTP configuration contains a VLAN (under
protocols mstp msti
msti-id
)
that does not exist on the switch and you try to commit the configuration, the
commit will fail. Remove the VLAN from the MSTP configuration before you
perform an upgrade.
■
In the
interfaces
configuration stanza, if
no-auto-negotiation
is configured but
speed and link duplex settings are not configured under
ether-options
and you
try to commit the configuration, the commit will fail. If
no-auto-negotiation
is
configured under
ether-options
, you must configure speed and link duplex settings.
■
In the
ethernet-switching-options
configuration, if
action
is not configured for the
number of MAC addresses allowed on the interface (under
secure-access-port
interface
interface-name
mac-limit
in the CLI or in the Port Security Configuration
page in the J-Web interface), and you try to commit the configuration, the commit
will fail. You must configure an action for the MAC address limit before upgrading
from Release 9.2 to Release 10.1.
■
If you have configured a tagged interface on logical interface 0 (unit 0), configure
a tagged interface on a logical interface other than unit
0
before upgrading from
Release 9.2 to Release 10.1. If you have not done this and you try to commit
the configuration, the commit will fail. Beginning with JUNOS Release 9.3 for EX
Series switches, untagged packets, BPDUs (such as in LACP and STP), and
priority-tagged packets are processed on logical interface 0 and not on logical
interface 32767. In addition, if you have not configured any untagged interfaces,
the switch creates a default logical interface 0.
■
On EX4200 switches, if you have installed advanced licenses for features such
as BGP, rename the
/config/license
directory to
/config/.license_priv
before
upgrading from Release 9.2 to Release 9.3 or later. If the switch does not have
a
/config/license
directory, create the
/config/.license_priv
directory manually
before you upgrade. If you do not rename the
/config/license
directory or create
the
/config/.license_priv
directory manually, the licenses installed will be deleted
after you upgrade from Release 9.2 to Release 9.3 or later.
Downgrading from JUNOS Release 10.1 to Release 9.2 for EX4200
Switches
When you downgrade a Virtual Chassis configuration from JUNOS Release 10.1 to
Release 9.2 for EX Series switches, member switches might not retain the mastership
priorities that had been configured previously. To restore the previously configured
mastership priorities, commit the configuration by issuing the
commit
command.
Related Topics
■
New Features in JUNOS Release 10.1 for EX Series Switches on page 184
■
Changes in Default Behavior and Syntax in JUNOS Release 10.1 for EX Series
Switches on page 187
■
Limitations in JUNOS Release 10.1 for EX Series Switches on page 188
■
Outstanding Issues in JUNOS Release 10.1 for EX Series Switches on page 191
200
■
Upgrade and Downgrade Issues for JUNOS Release 10.1 for EX Series Switches
JUNOS 10.1 Software Release Notes