Telnetting to Cisco 300 Series Managed Switches

Available Languages

Download Options

  • PDF     (3.8 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (42.8 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (61.1 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:December 13, 2018
Document ID:SMB72

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Telnetting to Cisco 300 Series Managed Switches

Objective

Telnet is disabled by default. It must be enabled by using the web-based switch configuration utility or the console interface and a serial cable connection. The objective of this document is to enable users to connect using telnet.

Applicable Devices

  • SF 300-08
  • SF 302-08
  • SF 302-08MP
  • SF 302-08P
  • SF 300-24
  • SF 300-24P
  • SF 300-48
  • SF 300-48P
  • SG 300-10
  • SG 300-10MP
  • SG 300-10P
  • SG 300-20
  • SG 300-28
  • SG 300-28P
  • SG 300-52

Connecting using telnet (Windows)

1. Select Start > Run.

2. Enter CMD in the Open field and press Enter.

3. Type telnet, a space, and the switch IP address. For example: c:>telnet 192.168.1.114

4. Press Enter. The Login displays. Press Ctrl-R to refresh the Menu CLI Login or to jump to the Menu CLI Login from any other window.

5. Enter cisco (default) as the User Name.

6. Enter the password cisco (default).

7. Press Enter.

Revision History

Revision Publish Date Comments
1.0
13-Dec-2018
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco