Upgrading Multilayer Switching Modules From 3.0 Or 3.0.1 To; Transition Issues From Release 2.1 To - 3Com 4007 Release Note

3com 4007: release note
Hide thumbs Also See for 4007:
Table of Contents

Advertisement

114
C
8: S
HAPTER
OFTWARE
Upgrading
Multilayer
Switching Modules
From 3.0 or 3.0.1 to
3.0.5
Transition Issues from
Release 2.1 to 3.0
Table 6 NVRAM Conversion Issues That Result When Upgrading From Release 2.1 to Release 3.0.0 or 3.0.1
Release 3.0 or 3.0.1 Command
ip multicast igmp snooping
ip multicast igmp query
ip multicast igmp interface ttl
ip multicast dvmrp mode
ip multicast dvmrp interface metric 1
ip multicast dvmrp tunnels define
qos control define
qos control define
qos classifier define
bridge trunk define
I
NSTALLATION
This section explains the process for upgrading a Multilayer Switching
Module to Release 3.0.5 if the module is starting from Release 3.0.0 or
Release 3.0.1. This upgrade procedure is simple and straightforward —
no feature settings should change as the module transitions from Release
3.0.0 or 3.0.1 to Release 3.0.5.
However, before you begin the upgrade to 3.0.5, if you have previously
upgraded the module from Release 2.1 to 3.0.0 or 3.0.1, 3Com
recommends that you first check the settings of some features, as that
particular upgrade transition caused many settings to change. It is highly
probable that you would have already noticed such conditions. However,
we thought it prudent to list the issues again, so that you can fix any
settings before you upgrade a module to Release 3.0.5.
Table 6 outlines the issues that occur when a Multilayer Switching
Module transitions from Release 2.1 to Release 3.0.0 or 3.0.1.
Value Set in
Release 2.x
Enabled
Enabled
Enabled
Enabled
Tunnel IP address
Trunk controls
defined
Ports assigned to
control
TCP/UDP source
port range
Backplane trunk
port defined
Issue or Value After
Upgrade to Release
3.0.0 or Release 3.0.1
Disabled
Disabled
Disabled
Disabled
0
Tunnels do not convert
Control index is incorrect
Port numbers may be
incorrect
Source port range is
incorrect
Some backplane trunk
ports may not be enabled.
Action to Take
Reset to the Release 2.x value
(see Note 5)
Reset to the Release 2.x value
Reset to the Release 2.x value
Reset to the Release 2.x value
(See Note 6)
Reset to the Release 2.x value
Redefine up to 8 DVMRP
tunnels per module
If trunked ports are defined,
and QoS controls are defined
for each port, redefine the
controls.
Modify each QoS control to
reselect the desired ports
Change the source range
(0-65535) or a desired
start-end range
See Note 7.

Advertisement

Table of Contents
loading

Table of Contents