The products, specifications, and other technical information regarding the products contained in this document are subject to
change without notice. All information in this document is believed to be accurate and reliable, but is presented without warranty
of any kind, express or implied, and users must take full responsibility for their application of any products specified in this
document. Lucent disclaims responsibility for errors which may appear in this document, and it reserves the right, in its sole
discretion and without notice, to make substitutions and modifications in the products and practices described in this document.
Lucent, Cajun, CajunDocs, OpenTrunk, P550, P220 and CajunView are trademarks of Lucent Technologies.
Microsoft, Windows, Windows NT, Windows 95, Windows 98, and Internet Explorer are trademarks or registered trademarks of
Microsoft Corporation in the U.S. and/or other countries.
OpenView is a trademark of Hewlett Packard Company.
Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation in the United States and
other countries.
3Com is a registered trademark and PACE is a trademark of 3Com or its subsidiaries.
Adobe is a registered trademark of Adobe Systems Incorporated.
Bay Networks and System 5000 are registered trademarks of Nortel Networks.
Cisco Catalyst 5000 is a registered trademark of Cisco Systems Incorporated.
ALL OTHER TRADEMARKS MENTIONED IN THIS DOCUMENT ARE PROPERTY OF THEIR RESPECTIVE OWNERS.
Chapter 1 Read Me First
This section of the Release Notes Supporting the Cajun P220 and Cajun P550 family of switches
contains information that is crucial to know before proceeding to install or use the Cajun switch.
Please review the following release notes before continuing to the Overview section.
CAUTION: Release 4.0.1 embedded software requires a MINIMUM of 16 MB DRAM
(Dynamic Random Access Memory) to run on a Cajun P550 Layer 2
supervisor module. BEFORE upgrading, ensure that the switch meets this
16 MB DRAM requirement. A memory upgrade is not required for a Cajun
P550 Layer 3 supervisor module, or the Cajun P220.
CAUTION: Release 4.0.1 introduces a new ASCII configuration file format that replaces
the traditional binary (*.cfg) files used to store and restore saved
configurations. You must save your binary configuration before upgrading the
switch to Release 4.0.1 or rebooting the switch for the first time using Release
4.0.1. For information about saving your binary configuration, refer to the
“Installation” section of these release notes.
CAUTION: When making configuration changes to the switch, explicitly save changes by
copying the running configuration to the startup configuration to ensure that
the changes persist after the switch is restarted.
This set of release notes supports the Cajun P220, Cajun P550, and Cajun P550R switches. For
detailed information about your product, refer the basic set of user documentation. These release
notes are intended to get you up and running as quickly as possible. The following topics are
covered:
This section covers features specified for Release 4.0.1 of the Cajun P220, Cajun P550, and Cajun
P550R switches. All supporting documentation is available from the Lucent Technologies Web
site at HTTP://pubs.lucentctc.com.
The Cajun P550R switch, which supports Layer 3 technology, contains features that are not
available in the Layer 2 Releases of the switch.
The following new features are available in Release 4.0.1 through the Enhanced Command Line
Interface or the Web Agent:
• VTP eavesdropping (Cisco compatibility)
• LDAP Release 3 client necessary for RealNet Rules support
• Support for the following MIBs:
- Policy capabilities MIB (proprietary)
- RIP v1/v2 (RFC1724)
- OSPFv2 (RFC1850)
- IGMP – Internet Group Management Protocol MIB (draft-ietf-edmr-igmp-mib-
• ASCII text configuration files with upload/download
• Redundant backplane support for Cajun P550R switches
• SNTP (Simple Network Time Protocol)
• AppleTalk Routing
• Hexadecimal addressing – subnet masks may be represented by a hexadecimal value
• Access lists
- Source and destination IP address wildcarding and TCP/UDP ranges
- TCP established connection filtering
• Configuration scripting via command line execution
Additional Undocumented Features
Features in this section are not documented in the released product documentation.
BOOTP/DHCP Relay Gateway
You can Enable or Disable the BOOTP/DHCP Relay Gateway from the Enhanced CLI in Interface
mode using the command '[no] ip bootp-dhcp gateway'. From the Cajun Switch Web
Agent, this setting is located in the IP Interfaces dialog box. To open the IP Interfaces dialog box,
in the IP Configuration section of the Web Agent, click Interfaces. The default for this parameter
is Disable.
This parameter affects how the router chooses a source interface for the reception of BOOTP/
DHCP requests received on a VLAN, as this source interface determines the value that is inserted
by the router into the giaddr field and designates the IP subnet pool that the DHCP server uses
to assign an address.
CAUTION: Release 4.0.1 embedded software requires a MINIMUM of 16 MB DRAM
(Dynamic Random Access Memory) to run on a Cajun P550 Layer 2
supervisor module. BEFORE upgrading, ensure that the switch meets this
16 MB DRAM requirement. A memory upgrade is not required for a Cajun
P550 Layer 3 supervisor module, or the Cajun P220.
NOTE: Release 4.0.1 introduces a new ASCII configuration file format that replaces the
traditional binary (*.cfg) files used to store and restore saved configurations. Before
upgrading the switch to Release 4.0.1, review the Installation section of these release
notes.
The following memory upgrade kits are available through your local sales representative:
Table 1-3: Module Descriptions
DescriptionModel Number
16 MB Memory
Upgrade Kit
M5500-MEM16
32 MB Memory
Upgrade Kit
Use the following procedure to upgrade from Release 3.1 to Release 4.0.1 of the Cajun P220,
Cajun P550, or Cajun P550R switch. For more detailed installation procedures, refer to the Cajun P550/P220 Switch Installation Guide.
M5500-MEM32
Downgrading to a Previous Release
1. In the CLI Configuration section of the Web Agent, click Config File Management.
In the Configuration File Management dialog box, save your Release 4.0.1 Running
Configuration (running.txt) to a TFTP server for potential later use.
2. From the Release 4.0.1 Enhanced CLI, clean the current configuration by issuing the
nvram init command.
3. Configure the switch to select the APP that contains the previous code release.
5. Use the CLI setup command to configure the switch.
6. Restore the binary configuration files of the release (3.1 or previous) you want to
restore. These configuration files do not reflect any changes you made to the
running configuration while using Release 4.0.1.
Problem: Release 4.0.1 of the Cajun switch contains new range-checking procedures
that may be reasonably more restrictive than those of previous releases.
Workaround: If you have a parameter in 3.1 that is outside the 4.0 range, it will be
noted in the Script Log File. After the second reboot the switch, check the Script Log File
to find out if any errors occurred as the script executed. To check the Script Log File, click
Script Log File in the CLI Configuration section of the Web Agent. If errors were
found, scroll up to find the particular error message. If you prefer to use the Enhanced
CLI, at the system prompt, type: show file logfile.txt.
NOTES:
• Some of the associated CLI command incorrectly list “Multilayer” and “3Com”.
These are not supported by the Cajun P550 48-Port 10/100 Media Module (M5548E100TC).
• In Release 4.0.1 of the Cajun switch, the Web Agent provides a new set of dialog
boxes in which you can:
- View startup and running configuration files
- View script execution log files
- Copy and manage configuration files
Ensure that you copy configuration files to a TFTP server or other storage location using
the Configuration File Management dialog box.
Upgrading from Release 3.1 or Previous Releases
Use the following procedure to upgrade the switch from Release 3.1 to Release 4.0.1.
NOTE: The Cajun switch does not support a direct upgrade to Release 4.0.1 from
releases prior to Release 3.0. If your switch runs a release prior to 3.0, upgrade the
switch to Release 3.0 or 3.1. Then, use the following procedure to upgrade the switch
from Release 3.0 or 3.1 to Release 4.0.1.
7. Save your Release 3.1 binary configuration file:
a. In the Memory Subsystems section of the Web Agent, click TFTP Update.
b. In the TFTP Server IP Address field, enter the IP address of the TFTP server to
which you will upload the 3.1 binary configuration file.
c. In the Filename field, specify the destination path and filename of the
configuration file. This is the TFTP server path.
d. In the TFTP Target Section pull-down menu, select Save Configuration
(binary).
e. Click the Update button.
f. Click the Status button. View the Transfer Completed message in the System
Status frame of the TFTP Update dialog box.
8. In the Memory Subsystems section of the Web Agent, click TFTP Update. In the
TFTP Update dialog box, download V4.0 onto your switch (into either APP1 or APP2).
9. Configure the switch to choose the appropriate APP (that contains V4.0 code) at the
next reboot.
10. Reset the switch to load the V4.0 image.
11. Refresh your Web browser window.
12. Verify the existence of the startup.txt file in NVRAM: in the CLI Configuration
section of the Web Agent, click Startup Config.
NOTE: The script log file (a new feature of Release 4.0.1) records the output of scripts
executed on the system, including the startup.txt file. Upon initial upgrade to Release
4.0.1, the script is generated but not run, and output is not initially recorded in the file.
13. In the CLI Configuration section of the Web Agent, click Script Log File. Scroll to
the bottom of the Script Log File to find out if any errors occurred as the script
executed. If errors were found, scroll up to find the particular error message.
The following problems and workarounds generally apply to all Cajun switches unless expressly
specified.
Cajun 48-Port 10/100 Media Module
Problem: Due to the positioning of the Cajun P550 48-Port Media Module (M5548E100TC) as a high-density desktop connectivity module, the following functionality is not
supported:
• Multi-layer and 3Com trunk mode
• Link aggregation (hunt groups)
• Port mirroring
• 3Com mapping table selection
• Flow control setting of "Enable with Aggressive Backoff"
• PACE priority mode
• Spanning tree mode (disabled by factory default; enabled in other cases)
• Port statistics: intra-BCM5308 unicast frames not reflected
Additionally, flow control and rate limiting available only on a per-module basis
Workarounds:
• If link aggregation is required over a 10/100TX Link, use a Cajun P550 20-port
Module (M5520-100TX) or a Cajun P550 Layer 3 12-port Copper Module (M5512R100TX).
• If a port is inadvertently configured to use Multilayer tagging, reconfigure the port to
use either Clear or IEEE 802.1Q tagging. To reconfigure the port from the Enhanced
CLI, enter the following command at the system prompt:
set port trunking-format {<mod-num>|<mod-port-range>}[...[,]{<modnum>|<mod-port-range>}] { clear | ieee-802.1Q}
If a port is inadvertently configured to use 3Com tagging, use the following procedure:
1. Reconfigure the port to use either Clear or IEEE 802.1Q tagging.
2. Copy (Save) the Running-Config to the Startup-Config.
3. Reboot the switch.
NOTES:
• 3Com VLT Tagging is not supported but can be enabled on the Cajun P550 48-port
Media Module’s (M5548E-100TC) internal switch ports by using the Web or CLI
management interface.
• The Cajun P550 48-port Media Module (M5548E-100TC) has been optimized for
desktop connections. Spanning Tree topology change convergence time can be
lengthy. This could lead to loss of connectivity and/or wrongful flow of data.
Command Line Interface
The command "set vlan <vlan-id> <port>" is used to bind additional ports to a VLAN if
trunking is enabled on that port. To set the port default VLAN for a port, use "set port vlan
NOTE: Release notes for the Cajun DocServer incorrectly excludes mention of the P550
platform. Both the Cajun P550 and P220 platforms are supported.
DVRMP
NOTE: The Cajun P550R Switch may lose a small number of DVMRP neighbor-toneighbor probe messages which may cause multicast routing instability under heavy
loads.