Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Kiwi CatTools > Kiwi CatTools Documentation > Kiwi CatTools 3.11 Administrator Guide > Devices > Device specific information > 3Com superstack switches

3Com superstack switches

Table of contents
No headers
Created by Caroline Juszczak, last modified by Caroline Juszczak on Jun 28, 2016

Views: 199 Votes: 0 Revisions: 1

CatTools 3Com switch issues


What switches are supported?


3Com SuperStack Switches:

610 / 630 / 1100 / 3300 / 3300 FX / 3300XM / 3300TM / 3300SM / 3300MM



Although telnet is not the most elegant, nor efficient way to obtain the configuration of a 3Com switch, there aren't many other practical options. By capturing the output of various 'display' commands, CatTools provides a human readable list of settings in case of switch failure. Since 3Com doesn't provide a nice "show config" type command, this backup method is the next best thing. Because of all the commands required to obtain a complete list of settings, the backup can take up to 5 minutes per switch. A future version of CatTools may use SNMP or HTTP to obtain the config.



While accessing the 3Com switch CLI, at odd times and for no obvious reason, the switch will perform a warm reset. This will cause the telnet session to disconnect. All network traffic will stop flowing until the switch has finished its start-up sequence. This can take around 15 seconds.


The switch appears to reset more often when the telnet session originates from a high speed port (100MBps). Once the switch has warm started, it is more prone to crashing again. A power reset (remove power cord) does help to return the switch to a stable state and reduce the chance of a crash occurring.


The crash does not appear to be associated with any particular command.


I have seen these crashes occur with all versions of switch agent software, up to and including version 2.62.


Using the Admin username to login instead of Security reduces the occurrence of crashes.


Hopefully this issue can be resolved in a future release of 3Com switch software. Any additional feedback would be appreciated.


Recommended backup plan.

Because of the chance of a switch crash, please only backup the devices during times of low traffic use. Also, reduce the frequency of your backups. Only make a backup when you believe the config might have changed. Use the Admin username instead of the Security username to login.


At this stage the config will always appear to have changed. This is because various packet counters and stats are included in the captured config. These values will change with each backup. A future version of CatTools may parse the captured data better and produce a cleaner list.


What commands are issued?


CatTools issues the following commands and captures the output to a file.


1    "bridge display"

2    "bridge multicastFiltering routerPort list"

3    "bridge port address list all" 

4    "bridge port summary all" 

5    "ethernet summary all"

6    "feature resilience detail"

7    "feature trunk summary" 

8    "ip interface display"

9    "snmp trap display"

10   "system display"

11    "system inventory"

12    "system module display"

13    "system security access display"

14    "system security user display"

15    "bridge vlan summary all"

16    "bridge vlan detail" (Defined VLAN numbers) 

17    "bridge port detail" (1 to number of switch ports)

18    "feature trunk detail" (1 to number of trunks)


Device setup.


Use the Username / Password fields to enter the username and passwords for the device. Leave the VTY and enable passwords blank as they are not used.


The standard 3Com usernames are: Monitor, Admin, Manager and Security.

You will need to use the Security login if you want to make changes to passwords etc.


Accessing switch stacks.

A switch stack consists of up to 4 switches connected via matrix cables. Each switch has a unit number (1 to 4) which identifies it. The IP address will be the same for each device in the stack.


Once logged in, you switch between the stack units by issuing the 'system unit N' command where N is the number of the stack unit you want to session to.


Refer to the 'Connecting via a session' section as to how to set up the devices in CatTools.


Sending commands to the CLI via CatTools.


By using the Device.CLI.Send commands at enable prompt menu, you can send commands to the 3Com switch CLI. Some examples are given below.

The registered version of CatTools allows you to capture the output to a file.


To change the password for the user "admin" use the commands:


system security user modify admin






To add port 3 to VLAN 2 with tagging use the command:


bridge vlan addport 2 3 802.1Q 



To drop back a menu item, use the "q" (quit) command.



Last modified