Retrieving a Cisco Contents Service Switch Configuration

Tested on a Cisco CSS

Using SSH, Telnet or the Console

For this procedure you will be using the Command Line Interface (CLI) of your Cisco Contents Service Switch device using an SSH client (such as OpenSSH or Putty), Telnet or through the console port. We would recommend using either SSH (for remote connections) or using a direct connection to the console port. Telnet provides no encryption of the communications and therefore your authentication credentials and configuration would be vulnerable if a malicious user were to monitor your connection.

 1.       Connect to the Cisco CSS using your favorite SSH client, Telnet or a direct console connection. (NB: You may need to set the baud rate to the appropriate speed for your device.  A list of standard rates can be found at the end of this document.  On our Cisco CSS test device, the baud rate was 9600)

2.       Logon using your administration authentication credentials.

3. Execute the following CLI command and capture the output (possibly using the cut and paste facility):

show startup-config

4. Save the captured output to a file and remove any visible page lines (i.e. --More--).

If you are unsure about the baud rate that your device is set to we would suggest trying the most common default baud rates which are 9600, 19200 & 115200

For your convenience, we have listed the other baud rates commonly supported by serial ports below:

110

300

600

1200

2400

4800

14400

28800

38400

56000

57600

Standard baud rates supported by some serial ports:

128000

153600 

230400

256000

460800

921600

How to Extract a 3Com Switch Configuration

3Com Switch configuration retrieval instructions

(Tested on a 3Com Switch 5500-SI)

Using SSH, Telnet or the Console.

For this procedure you will be using the Command Line Interface (CLI) of your 3Com Switch device using an SSH client (such as OpenSSH or Putty), Telnet or through the console port. We would recommend using either SSH (for remote connections) or using a direct connection to the console port. Telnet provides no encryption of the communications and therefore your authentication credentials and configuration would be vulnerable if a malicious user were to monitor your connection. 

1.       Connect to the 3Com Switch using your favourite SSH client, Telnet or a direct console connection.  (NB: You may need to set the baud rate to the appropriate speed for your device.  A list of standard rates can be found at the end of this document.  On our 3Com test device, the baud rate was 19200)

2.       Press ENTER twice to get started.

3.       If required, log in using your administration authentication credentials.

4.       Execute the following CLI command and capture the output (possibly using the cut and paste facility):

display current-config

1.       Save the captured output to a file and, if necessary, remove any visible page lines (i.e. --More--).

2.       The resulting file should now be auto-detected as a 3Com device when entered into Nipper Studio. 

If you are unsure about the baud rate that your device is set to we would suggest trying the most common default baud rates which are 9600, 19200 & 115200

For your convenience, we have listed the other baud rates commonly supported by serial ports below:

110

300

600

1200

2400

4800

14400

28800

38400

56000

57600

 Standard baud rates supported by some serial ports:

128000

153600 

230400

256000

460800

921600

Retrieving Configuration Files from 3Com Switches

(Tested on a 3Com Switch 5500-SI)

Using SSH, Telnet or the Console.

For this procedure you will be using the Command Line Interface (CLI) of your 3Com Switch device using an SSH client (such as OpenSSH or Putty), Telnet or through the console port. We would recommend using either SSH (for remote connections) or using a direct connection to the console port. Telnet provides no encryption of the communications and therefore your authentication credentials and configuration would be vulnerable if a malicious user were to monitor your connection.

1.       Connect to the 3Com Switch using your favourite SSH client, Telnet or a direct console connection.  (NB: You may need to set the baud rate to the appropriate speed for your device.  A list of standard rates can be found at the end of this document.  On our 3Com test device, the baud rate was 19200)

2.       Press ENTER twice to get started.

3.       If required, log in using your administration authentication credentials.

4.       Execute the following CLI command and capture the output (possibly using the cut and paste facility):

display current-config

1.       Save the captured output to a file and, if necessary, remove any visible page lines (i.e. --More--).

2.       The resulting file should now be auto-detected as a 3Com device when entered into Nipper Studio.

If you are unsure about the baud rate that your device is set to we would suggest trying the most common default baud rates which are 9600, 19200 & 115200

For your convenience, we have listed the other baud rates commonly supported by serial ports below:

110

300

600

1200

2400

4800

14400

28800

38400

56000

57600

Standard baud rates supported by some serial ports:

128000

153600 

230400

256000

460800

921600

Brought to you by Titania www.titania.com

Network Security Auditing Tool- Free Trial Available

Nipper Studio Network Security Auditing Tool

Free trial at www.titania-security.com

Nipper Studio is a security auditing software that allows its users to produce detailed security reports on the vulnerabilities in their network devices (switches, routers, firewalls etc.) Nipper Studio works from the inside out by analysing the actual devices configurations, giving you a much more detailed report than a vulnerability scanner could produce. Furthermore the software never touches the network so Nipper Studio can be used in high security environments. A report at the level of a manual penetration tester is generated within seconds and displays:

• Severity of the threat
• Ease of resolution
• Potential solutions to resolve the issue

(you can use either the CVSSv2 rating system or the established Nipper Studio Rating System and export results into various formats)

Nipper Studio also produces a mitigation report that provides the information to help organisations fix their network vulnerabilities with the smallest impact on their operations. When the fixes are made Nipper Studio can generate a comparison report that displays what changes have been made and how successful this has been in securing their networks.

Customizable settings include:

1. The ability to theme your report throughout with your own company branding;

2. Choose policy settings that are relevant to your organization and construct profiles that remember these settings;

3. Wholly or partly exclude sections and findings in the report. You can also hide sensitive information from the report;

4. Add your own notes to the report;

Nipper Studio is multi-platform and supports an extensive amount of devices, for a full supported device list go to www.titania-security.com/nipperstudio/devices 

For a free evaluation of the software go to www.titania-security.com

Retrieving Config Files from Cisco CatOS-Based Catalyst Switches

For this procedure you will need to use the Command Line Interface (CLI) of your Cisco device using an SSH client (such as OpenSSH or Putty), Telnet or through the console port. We would recommend using either SSH (for remote connections) or using a direct connection to the console port. Telnet provides no encryption of the communications and therefore your authentication credentials and configuration would be vulnerable if a malicious user were to monitor your connection.

1. Connect to the Cisco using your favorite SSH client, Telnet or a direct console connection.
2. Logon using your administration authentication credentials.
3. Enter \data{enable} and type in your enable password.
4. Execute the following CLI command and capture the output (possibly using the cut and paste facility):
   

   show config all

5. Save the captured output to a file and remove any visible page lines (i.e. --More--).

Retrieving Config Files From Cisco IOS-Based Routers, Switches And APs

There are multiple different methods of extracting the configuration from your Cisco IOS-based router, switch or wireless access point. This guide outlines just two of those methods.

Using HTTP(S)

We would recommend using HTTPS rather than HTTP for transferring your devices configuration as the latter provides no encryption. The procedure for getting the configuration from the device using HTTP(S) is as follows:

1. Using your favorite web browser, connect to the HTTP(S) service provided by your Cisco device for remote management. You can do this by entering "https://" (recommended) or "http://" followed by your devices IP address.
2. Logon using your administration username and password.
3. Click on the link to level 15 of the web console.
4. Click on the "show" link.
5. Click on the "running-config" link.
6. Finally click on the "CR" link.
7. Copy and paste the configuration into a file to use with Nipper Studio.

Using SSH, Telnet Or The Console

For this procedure you will be using the Command Line Interface (CLI) of your Cisco device using an SSH client (such as OpenSSH or Putty), Telnet or through the console port. We would recommend using either SSH (for remote connections) or using a direct connection to the console port. Telnet provides no encryption of the communications and therefore your authentication credentials and configuration would be vulnerable if a malicious user were to monitor your connection.

1. Connect to the Cisco using your favorite SSH client, Telnet or a direct console connection.
2. Logon using your administration authentication credentials.
3. Enter \data{enable} and type in your enable password.
4. Execute the following CLI command and capture the output (possibly using the cut and paste facility):

   show run

5. Save the captured output to a file and remove any visible page lines (i.e. --More--).

Retrieving Config Files from HP ProCurve Switches And Routing Switches

There are multiple different methods of extracting the configuration from from your HP ProCurve devices, this guide outlines two of those methods.

Using HTTP(S)

We would recommend using HTTPS rather than HTTP for transferring your devices configuration as the latter provides no encryption. The procedure for getting the configuration from the device using HTTP(S) is as follows:

1. Using your favorite web browser, connect to the HTTP(S) service provided by your HP ProCurve device for remote management. You can do this by entering "https://" (recommended) or "http://" followed by your devices IP address.
2. Logon using your administration username and password.
3. Select the "Diagnostics" tab, then the "Configuration Report" button.
4. Copy and paste the configuration into a file to use with Nipper Studio.

Using SSH, Telnet Or The Console

For this procedure you will be using the Command Line Interface (CLI) of your HP ProCurve device using an SSH client (such as OpenSSH or Putty), Telnet or through the console port. We would recommend using either SSH (for remote connections) or using a direct connection to the console port. Telnet provides no encryption of the communications and therefore your authentication credentials and configuration would be vulnerable if a malicious user were to monitor your connection.

1. Connect to the HP ProCurve using your favorite SSH client, Telnet or a direct console connection.
2. Logon using your administration authentication credentials.
3. Execute the following CLI command and capture the output (possibly using the cut and paste facility):

   show config

4. Save the captured output to a file and remove any visible page lines (i.e. --More--).

Retrieving Config Files from Netgear FSM Switches

You can obtain a copy of your configuration from Netgear FSM devices by using SSH, Telnet or the Console.

For this procedure you will be using the Command Line Interface (CLI) of your Netgear FSM device using an SSH client (such as OpenSSH or Putty), Telnet or through the console port. We would recommend using either SSH (for remote connections) or using a direct connection to the console port. Telnet provides no encryption of the communications and therefore your authentication credentials and configuration would be vulnerable if a malicious user were to monitor your connection.

1. Connect to the Netgear FSM using your favorite SSH client, Telnet or a direct console connection.
2. Logon using your administration authentication credentials.
3. Execute the following CLI command and capture the output (possibly using the cut and paste facility):

   show run

4. Save the captured output to a file and remove any visible page lines (i.e. --More--).

1. Extracting Configurations from Dell PowerConnect Switches

There are multiple different methods of extracting the configuration from your Dell PowerConnect devices, this guide outlines two of those methods.

Using HTTP

The procedure for getting the configuration from the device using HTTP is as follows:

1. Using your favorite web browser, connect to the HTTP service provided by your Dell PowerConnect Device for remote management. You can do this by entering "http://" followed by your devices IP address.
2. Logon using your administration username and password.
3. Select the "Systems" tab, then the "File Management" tab, then the "File Upload" option.
4. Select the "Configuration upload" button, and the "Upload via HTTP" button.
5. Select the "Running Configuration" option in the "Transfer File Name" drop down menu.
6. Press the "Apply Changes" button, and the configuration will be saved in a format ready for use with Nipper Studio.

Using SSH, Telnet Or The Console

For this procedure you will be using the Command Line Interface (CLI) of your Dell PowerConnect device using an SSH client (such as OpenSSH or Putty), Telnet or through the console port. We would recommend using either SSH (for remote connections) or using a direct connection to the console port. Telnet provides no encryption of the communications and therefore your authentication credentials and configuration would be vulnerable if a malicious user were to monitor your connection.

1. Connect to the Dell PowerConnect device using your favorite SSH client, Telnet or a direct console connection.
2. Logon using your administration authentication credentials.
3. Execute the following CLI command and capture the output (possibly using the cut and paste facility):

   show config

4. Save the captured output to a file and remove any visible page lines (i.e. --More--).