Did you make any changes to the environment (VLANs, adding modules or upgrades) before or at the time of this event?

Are there other similarly configured devices that could have this problem but do not?

Where was this problematic device connected (which switch and interface)?

When did this problem first occur?

When did this problem last occur?

How often does this problem occur?

How many devices have this problem?

Were any traces or debug output captured during the problem time? What troubleshooting steps have you tried? Which, if any, of the following tools were used?

– Ethanalyzer, local or remote SPAN

– CLI debug commands

– traceroute, ping

Is your problem related to a software upgrade attempt?

– What was the original Cisco VSG version?

– What is the new Cisco VSG version?

Obtaining a File of Core Memory Information

Cisco customer support engineers often use files from your system for analysis. One such file that contains memory information is referred to as a core dump. The file is sent to a TFTP server or to a flash card in slot0: of the local switch. You should set up your switch to generate this file under the instruction of your TAC representative, and send it to a TFTP server so that it can be e-mailed to TAC.

This example shows how to generate a file of core memory information or a core dump:

vsg(config)# system cores tftp://10.91.51.200/svr15svc_coresvsg(config)# show system coresCores are transferred to tftp://10.91.51.200/svr15svc_coresvsg(config)#

Note The filename (indicated by svr15svc_cores) must exist in the TFTP server directory.

Copying Files

You might need to move files to or from the switch. These files may include log, configuration, or firmware files.

The Cisco VSG always acts as a client. For example, an FTP/SCP/TFTP session always originates from the switch and either pushes files to an external system or pulls files from an external system.

Tip You should back up the startup-configuration file to a server daily and before you make any changes. You could use a short script to be run on the Cisco VSG to perform a save and a backup of the configuration. The script must contain two commands: copy running-configuration startup-configuration and copy startup-configuration tftp://server/name. To execute the script, use the run-script [filename] command.