Cisco switch connection

Cisco switch connection DEFAULT

8 Steps to Configure Your Network Switch

  • show version
  • show running-config
  • show VLAN brief
  • show VTP status
    • (config)# IP domain-name routerfreak.com
    • (config)# hostname Switch01
    • (config)# interface VLAN1
    • (config)# description Management VLAN
    • (config)# IP address 192.168.101.1 255.255.255.0
    • vtp [client | server | transparent]
    • vtp domain name
    • description *** DESCRIPTION ***
    • switchport access vlan ###
    • sswitchport mode access
    • power inline consumption ###
    • queue-set 2
    • mls qos trust dscp
    • storm-control multicast level 50.00
    • no cdp enable
    • spanning-tree portfast
    • spanning-tree bpduguard enable
    • Interface GigabitEthernet1/0/1
    • description *** UPLINK ***
    • switchport trunk encapsulation dot1q
    • switchport mode trunk
    • speed 1000
    • duplex full
    • Switch01(config)# crypto key generate rsa
    • The name for the keys will be:
    • Switch01.routerfreak.com
    • How many bits in the modulus [512]: 1024
    • % Generating 1024 bit RSA keys, keys will be non-exportable...[OK]
    • # line vty 0 4
    • (config-line)# transport input ssh
    • (config-line)# login local
    • (config-line)# password routerfreak
    • (config-line)# exit
    • # line console 0
    • (config-line)# logging synchronous
    • (config-line)# login local
    • Switch01# service password-encryption
    • remote-computer# ssh 192.168..101.1
    • Log in as: username
    • Password:
    • Switch01>en
    • Password:
    • Switch01#
  • For spare switches, make sure to delete the flash:vlan.dat file to erase the previous configuration.

    Step 2: Set up management IP

    Unlike with that punny name you gave your home Wi-Fi network, when setting up the hostname for your switch you should probably stick to a more professional and standard naming convention. Follow any preset naming assignment your company is using and then assign an IP address on the management VLAN. Next, make sure your switch has a set hostname and domain name:

    Step 3: Check VTP revision number

    Hit the show vtp status command to reveal your Virtual Trunking Protocol (VTP) revision numbers. The VTP revision numbers determine which updates are to be used in a VTP domain. When you set a VTP domain name, the revision number is set to zero—after which each change to the VLAN database increases the revision number by one. Your switch will only process data from a neighboring switch coming from the same domain and if the revision number of the neighboring switch is higher than its own. This means that the switches will update their VLAN configuration based on the VTP information being sent by the switch with the highest revision number.

    So, before you add your switch to the network, you’re going to want to set its revision number to zero. To easily reset the domain back to zero, change the config mode to transparent:

    Step 4: Configure access ports

    You might already have a template ready for access port configuration, but in case you don’t, here are some commands you should use:

    Step 5: Configure trunk ports

    Enter the command sh int g0/1 capabilities and check the trunking protocol supported. If ISL is supported, you have to issue the switchport trunk encapsulation dot1q on the trunk port configuration. If not, simply type switchport mode trunk. It means there is no other encapsulation supported so there is no need for an encapsulation command. It only supports 802.1Q.

    Step 6: Configure access ports

    After already performing basic network switch configurations, it’s time to generate RSA keys to be used during the SSH process, using the crypto commands shown here:

    Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes.

    Step 7: Set up VTY line config

    If you have not set the console line yet, you can easily input these values:

    Set the enable password using the enable secret password command. Then, set the privilege exec password with username name privilege 15 secret password. Make sure that the password-encryption service is activated.

    Verify SSH access by typing ‘sh ip ssh’ to confirm that the SSH is enabled. You can now try to log in from a remote machine to verify that you can ssh to your Cisco switch.

    Finishing touches

    You’ve made it through the learning process with (hopefully) minimum bumps and bruises, and you’re just about ready to ride off. All that’s left is to test your access, reload the switch, and ready the cables. Once that’s done, label your switch, rack it up, and go enjoy doing anything that doesn’t involve switch configuration!

    Sours: https://www.cisco.com/c/en/us/solutions/small-business/resource-center/networking/how-to-setup-network-switch.html

    How to Configure Cisco Switch: A Step-by-Step Guide with Commands

    How to configure Cisco switches - A step-by-step guide

    When we think of connectivity in a network, the router is probably the first device that comes to mind, but switches play a vital role in enabling network devices to communicate.

    Switches can take incoming/outgoing traffic and pass it onward toward its final destination. Cisco is one of the most well-known switch vendors on the market and in this article, we’re going to look at how to configure Cisco switches with PuTTY and from the command-line.

    Getting Started with Cisco Switch Commands

    Before we begin, get to know what hardware you’re using, fire up your CLI and download PuTTY.

    The first step is to check what hardware you’re using before you begin. If you’re using a Cisco switch you need to know what model you have. You also want to check the physical state of the device and verify that none of the cables are damaged. You can turn the router on to make sure there is no damage to the lighting/indicators.

    Now that you’ve made sure the device is in working order you’re ready to start configuring. In this guide, we’re going to perform a Cisco switch configuration through the command-line interface (CLI) with the open-source SSH/Telnet client PuTTY (although you can use another tool if you prefer). If for any reason putty is not an option for your setup, you can get similar results with a PuTTY alternative.

    1. Connect the Switch to PuTTY

    To start configuration, you want to connect the switch console to PuTTY. You can do this by doing the following:

    1. Connect the switch to PuTTY with a 9-pin serial cable.
    2. Now open PuTTY and the PuTTY Configuration window will display. Go to the Connection type settings and check the Serial option (shown below).
      PuTTY Configuration sample screenshot
    3. Go to the Category list section on the left-hand side and select the Serial option.
    4. When the options controlling local serial lines page displays enter the COM port your network is connected to in the Serial line to connect to box e.g. COM1.
    5. Next, enter the digital transmission speed of your switch model. For 300 and 500 Series Managed Switches, this is 115200.
    6. Go to the Data bits field and enter 8.
    7. Now go to the Stops bits field and enter 1.
    8. Click on the Parity drop-down menu and select the None option.
    9. Go to the Flow Control drop-down menu and select the None option.

    Save Your Settings and Start the PuTTY CLI

    To save your PuTTY settings for your next session do the following:

    1. Click on the Session option from the Category list on the left-hand side of the page.
      PuTTY Configuration - specify destination screenshot
    2. Go to the Saved Session field and enter a name for your settings e.g. Comparitech.
    3. Click the Save button to store the settings.
    4. Press the Open button at the bottom of the page to launch the CLI.

    The following message will display in the command prompt:

    Switch>

    2. Enter Privileged EXEC Mode and Set a Hostname for the Switch

    Type in the enable command to enter privileged EXEC mode (you don’t need a password at this stage because you’re under the default configurations which don’t have one!):

    Enable 

    Next, enter Global Configuration Mode and enter the following command:

    Switch# configure terminal Switch(config)#

    You can make the switch easier to locate in the network by assigning a hostname. Enter the following command to assign a hostname:

    Switch(config)# hostname access-switch1 access-switch1(config)#1

    3. Assign a Password to the Switch

    Once you’ve assigned a hostname you will want to create a password to control who has access to the privileged EXEC mode (to prevent everyone from being able to log in). To assign an administrator password to enter the following command:

    access-switch1(config)# enable secret COMPARI7ECH

    Remember to pick a strong password so that it’s harder to figure out.

    4. Configure Telnet and Console Access Passwords

    The next step is to configure passwords for Telnet and console access. Configuring passwords for these is important because it makes your switch more secure. If someone without authorization gains telnet access then it puts your network at serious risk. You can configure passwords by entering the following lines (See the top paragraph for Telnet and the bottom paragraph for Console access).

    Telnet

    access-switch1(config)# line vty 0 15access-switch1(config-line)# password COMPARI7ECHaccess-switch1(config-line)# loginaccess-switch1(config-line)# exitaccess-switch1(config)#

    Console

    access-switch1(config)# line console 0access-switch1(config-line)# password COMPARI7ECH access-switch1(config-line)# loginaccess-switch1(config-line)# exitaccess-switch1(config)#

    5. Configure IP Addresses With Telnet Access

    The next step is to decide which IP addresses will have access to Telnet, and add them with the PuTTY CLI. To select permitted IP’s enter the following command (replace the listed IPs with the IPs of the components you want to grant permission to):

    access-switch1(config)# ip access-list standard TELNET-ACCESSaccess-switch1(config-std-nacl)# permit 216.174.200.21access-switch1(config-std-nacl)# permit 216.174.200.21access-switch1(config-std-nacl)# exit

    You can also configure your network’s access control lists (ACLs) to virtual terminal (VTY) lines. ACLs ensure that only the administrator can connect to the router through Telnet.

    access-switch1(config)# line vty 0 15access-switch1(config-line)# access-class TELNET-ACCESS inaccess-switch1(config-line)# exitaccess-switch1(config)#

    6. Configure a Network Management IP address (or Management Interface)

    Next, you need to configure a network management IP address. Switches don’t come with an IP address by default, meaning that you can’t connect to it with Telnet or SSH. To solve this problem you can select a virtual LAN(VLAN) on the switch and create a virtual interface with an IP address. You can do this by entering the following command:

    access-switch1(config)# interface vlan 1access-switch1(config-if)# ip address 10.1.1.200 255.255.255.0access-switch1(config-if)# exitaccess-switch1(config)#

    The new IP management address is located in VLAN1, which other computers will now use to connect.

    7. Assign a Default Gateway to the Switch

    At this stage, you want to assign a default gateway to the switch. The default gateway is essentially the address of the router that the switch will be communicating with. If you don’t configure a default gateway then VLAN1 will be unable to send traffic to another network. To assign the default gateway, enter the command below (change the IP address to that of your router).

    access-switch1(config)# ip default-gateway 10.1.1.254

    8. Disable Unused Open Ports

    As a best practice, it is a good idea to disable any unused open ports on the switch. Cyber-criminals often use unsecured ports as a way to breach a network. Closing these ports down reduces the number of entry points into your network and makes your switch more secure. Enter the range of ports you want to close by entering the following command (you would change 0/25-48 to the ports that you want to close):

    access-switch1(config)# interface range fe 0/25-48access-switch1(config-if-range)# shutdownaccess-switch1(config-if-range)# exitaccess-switch1(config)#

    9. Save Your System Configuration Settings

    Once you’ve finished configuring the router it’s time to save your system configuration. Saving the configuration will make sure that your settings are the same when you open up your next session. To save enter the following command:

    access-switch1(config)# exit access-switch1# wr

    Always remember to save any changes to your settings before closing the CLI.

    10. Configure NetFlow to Manage Your Cisco Switch (Optional)

    It is also a good idea to use a network traffic analyzer to monitor network traffic. As a Cisco device, your switch will have the communication protocol NetFlow. However, it must be configured first. You can configure NetFlow by completing the four steps below. Before we begin, enter Global Configuration Mode by executing the following command:

    Switch# configure terminal 

    Create a flow record

    1. The first step is to create a flow record (you can change the name). You can do this by entering the following command: #flow record Comparitechrecord
    2. After you’ve entered the previous command you need to set the IPv4 source address, IPv4 destination address, iPv4 protocol, transport source-port, transport destination-port, IPv4 dos, interface input, and interface output. You can do this by entering the following command: Switch# match ipv4 source address Switch# match ipv4 destination address Switch# match ipv4 protocol Switch# match transport source-port Switch# match transport destination-port Switch# match ipv4 tos Switch# match interface input Switch# collect interface output 
    3. To finish configuring the flow record and define the type of data you’re going to collect, enter the following switch configuration commands: Switch# collect interface output Switch# collect counter bytes Switch# collect counter packets Switch# collect timestamp sys-uptime first Switch# collect timestamp sys-uptime last 

    Create the Flow Exporter

    1. You must now create the flow exporter to store the information that you want to export to an external network analyzer. The first step is to name the flow exporter: Switch# flow exporter Comparitechexport
    2. Enter the IP address of the server your network analyzer is on (Change the IP address): Switch# destination 117.156.45.241
    3. Configure the interface that you want to export packets with: Switch# destination source gigabitEthernet 0/1 
    4. Configure the port that the software agent will use to listen for network packets: Switch# transport UDP 2055 
    5. Set the type of protocol data that you’re going to export by entering this command: Switch# export-protocol netflow-v9 
    6. To make sure there are no gaps in when flow data is sent enter the following command: Switch# template data timeout 60 

    Create a Flow Monitor

    1. Once you’ve configured the flow exporter it is time to create the flow monitor. Create the flow monitor with the following command:< Switch# flow monitor Comparitechmonitor
    2. Associate the flow monitor with the flow record and exporter we configured earlier: Switch# record Comparitechrecord Switch# exporter Comparitechexport
    3. To make sure that flow information is collected and normalized without a delay, enter the following command: Switch# cache timeout active 60 Switch# cache timeout inactive 15 
    4. Enter the exit command: Switch# exit 
    5. You need to input the interfaces that will collect the NetFlow data. If this is an ethernet interface you would enter the following: Switch# interface gigabitEthernet 0/1
    6. Use the following command to configure NetFlow on multiple interfaces (the input command will still collect data in both directions): Switch# ip flow monitor Comparitechmonitor input 
    7. If you want to collect NetFlow data on only one interface then you must use the input and output command. So you would enter the following: Switch# ip flow monitor Comparitechmonitor input Switch# ip flow monitor Comparitechmonitor output 
    8. Exit configuration mode by entering the following command: Switch# exit 
    9. Save your settings to finish.

    Configure a Cisco Switch for Peace of Mind! 

    Completing simple tasks like configuring passwords and creating network access lists controls who can access the switch can enable you to stay secure online. Incomplete or incorrect configurations are a vulnerability that attackers can exploit.

    Configuring a Cisco switch is only half the battle, you also have to regularly monitor its status. Any performance issues with your switch can have a substantial impact on your users.

    Using a network monitoring tool and network analyzer can help you to monitor switches remotely and review performance concerns. Taking the time out of your day to configure a switch and assign strong passwords gives you peace of mind so that you can communicate safely online.

    Cisco Switch Configuration & Commands FAQs

    How to configure a trunk port on a Cisco 2960 switch?

    To configure a trunk port on a Cisco 2960 switch:

    1. Enter configuration mode:
    configure terminal
    1. Specify the port to use:
    interface <interface-id>
    1. Configure the port as a Layer 2 trunk:
    switchport mode {dynamic {auto | desirable} | trunk}

    These options mean:

    • dynamic auto – The Default. Creates a trunk link if the neighboring interface is set to trunk or desirable mode.
    • dynamic desirable – Creates a trunk link if the neighboring interface is set to trunk, desirable, or auto mode.
    • trunk – Sets the interface in permanent trunking mode.
    1. Specify a default VLAN to use for back up. This is optional:
    switchport access vlan <vlan-id>
    1. Specify the native VLAN:
    switchport trunk native vlan <vlan-id>
    1. Exit the config mode:
    end

    How do I set a static IP on a Cisco switch?

    A problem with the GUI interface of Cisco switches makes it impossible to assign a static IP address to an interface. Follow these steps for a workaround:

    1. Create a text file on your PC. It doesn’t matter where you save it or what you call it, but make sure you remember where it is. Substitute real values for the tokens shown in angle brackets (<>) below. The text in the file should be:
    Config t Interface <VLAN ID> No ip address DHCP Y No ip address <old IP address> IP address <new IP address> <subnet mask> Exit IP default-gateway <gateway IP address>
    1. Access the admin menu of the switch for Switch Management.
    2. In the menu, click on Administration, then File Management, and then select File Operations.
    3. In the File Operations screen, set the following:
    • Operation Type: Update File
    • Destination File Type: Running Configuration
    • Copy Method: HTTP/HTTPS
    • File Name: (Browse to select the file you created on your PC).
    1. Click on Apply.

    These steps will create a static IP address, which you can check by going from the main menu to IP Configuration > IPv4 Interface.

    Do I have to configure a Cisco switch before it gets to work?

    No. The typical Cisco switch is ready to go out-of-the-box. However, you might want to change some parameters to customize its operations. 

    Sours: https://www.comparitech.com/net-admin/configure-cisco-switches/
    1. Seat belts custom
    2. Vbs theme 2016
    3. Back pod for sale
    4. Akrapovic removable baffle

    Chapter 10. Connecting switches using trunk links

    The switch I’ve been working with in this book has only 24 ports. Yours may have 24 or 48, but regardless of the exact number, in an organization of any size, you can imagine that one switch isn’t going to cut it. As you add more devices to a network, eventually you’re going to run out of switch ports. When that happens, you’ll have to add another switch.

    In this chapter, you’re going to connect your second switch, Switch2, to Switch1. You’ll then move Executive-PC1 from Switch1 to Switch2. Before starting this chapter, be sure you’ve configured Switch2 using the lab setup instructions found under the Source Code link at https://www.manning.com/books/learn-cisco-network-administration-in-a-month-of-lunches. If you haven’t, you won’t be able to complete the labs in this chapter.

    Adding another switch isn’t as simple as connecting the new switch to an existing switch and powering it on. It’s almost that simple, but you have to perform a few key steps to get everything working. Here’s a quick overview of those steps:

    1. Physically connect the new switch.
    2. Configure the switch ports to form a VLAN trunk.
    3. Configure VLANs on the new switch.

    10.1. Connecting the new switch

    10.2. Understanding VLAN trunk links

    10.3. Configuring Switch2

    10.4. Moving devices to the new switch

    10.5. Changing the trunk encapsulation

    10.6. Commands in this chapter

    10.7. Hands-on lab

    Sours: https://livebook.manning.com/book/learn-cisco-network-administration-in-a-month-of-lunches/chapter-10/
    Connect Cisco Router and Switch to ISP Home Router and Access Internet

    Access the CLI via PuTTY using a Console Connection on 300 and 500 Series Managed Switches

    Objective

    Switches can be accessed and configured through the Command Line Interface (CLI). Accessing the CLI allows commands to be entered in a terminal based window. For a user who has had more experience with terminal commands, this may be an easier alternative to navigating the web configuration utility. Certain tasks such as recovering an administrator password can only be performed through the CLI. In order to access the CLI you must use an SSH client. PuTTY is a standard SSH client and can be found here. This document assumes you are connecting to the switch using PuTTY.

    The objective of this document is to show you how to access the Command Line Interface (CLI) of a switch and a Secure Shell (SSH) client.

    Note: Cisco 200 Series Small Business Managed Switches do not support the CLI.

    Applicable Devices | Software Version

    Accessing the CLI via PuTTY with a Console Connection

    Step 1. Connect the switch to the computer using a standard 9-pin serial cable.

    The Cisco DB9 to RJ45 Console Cable also supports console connections, but only if the switch has an RJ45 Console port. An RJ45 Console port resembles an Ethernet port and is labeled CONSOLE on the back of the switch.

    Newer laptops don’t have Serial ports on them, so in this case you have to use a USB to Serial adapter. When plugging that into a computer it assigns a COM port number to it that is not COM1. If this is the case for you, you need to know where to look to find the correct COM port number when setting up the connection with PuTTY. Right-click on the Windows logo/Start menu and click on Device Manager to open it.

    In the Device Manager, you would look to see what COM port is given to the USB adapter. In this case you would need to use COM4 for the Serial line to make the connection.

    Step 2. Open the PuTTY application. The PuTTY Configuration window opens:

    Step 3. Under the Connection Type field, click the Serial radio button.

    Step 4. In the Category navigation field, choose Serial.

    The Options controlling local serial lines page opens:

    Step 5. In the Serial line to connect to field, enter the COM port that your device is connected to. The default COM port is COM1.

    Step 6. In the Speed (baud) field, enter the digital transmission speed that is compatible with the switch. For 300 and 500 Series Managed Switches, the speed must be set to 115200.

    Step 7. In the Data bits field, enter the number of data bits used for each character. The recommended value is 8.

    Step 8. In the Stop bits field, enter the number of bits to be sent at the end of every character. The stop bit informs the machine that it has reached the end of a byte. The recommended value is 1.

    Step 9. In the Parity drop-down menu, select the method of detecting errors in transmission. The recommended method for detecting errors in transmission is None.

    Step 10. In the Flow Control drop-down menu, select the method of preventing data overflow. The recommended method for preventing data overflow is None.

    Step 11. (Optional) In order to save the connection settings for future use, go to the Category navigation pane and choose Session. If you do not wish to save the connection settings, skip to Step 14.

    Step 12. Under the Saves Sessions field, enter a name for the settings to be saved as.

    Step 13. Click Save.

    Step 14. Click Open.

    The COM1 – PuTTY console window opens.

    Step 15. Hit Enter on the keyboard to activate the Command Line Interface (CLI). The log in prompt is displayed:

    Step 16. Enter the User Name. The default username is cisco.

    Step 14. Enter the Password. The default password is cisco.

    Sours: https://www.cisco.com/c/en/us/support/docs/smb/switches/cisco-small-business-300-series-managed-switches/smb4984-access-the-cli-via-putty-using-a-console-connection-on-300-a.html

    Switch connection cisco

     


    In preparation of your CCNA exam, we want to make sure we cover the various concepts that we could see on your Cisco CCNA exam. So to assist you, below we will discuss something you will definately need to be able to do in your CCNA lab; Connecting your PC to your Cisco Switch or Router. So since this is probably one of the first tasks on your way to your CCNA certification, let me congratulate you on taking the first step to advance your networking career with a Cisco certification!

    Connect a PC to a Cisco Router or Switch

    Use the supplied rollover cable and the DB-9 adapter to connect a PC to the Cisco console port. The PC or terminal must support VT100 terminal emulation. The terminal emulation software—frequently a PC application such as Microsoft Windows HyperTerminal or Symantec Procomm Plus—makes possible the communication between the switch and your PC or terminal during the setup program.

    Follow these steps to connect the PC to the Cisco unit:

     

    1. Connect the 9 pin to RJ-45 adapter to the console cable.(Depending on my source for the console kit, you may already have this step done for you as sometimes I get one piece console kits.)
    2. Connect the 9 pin adapter to COM1 on your PC(If your PC only has USB ports and does not have a 9 pin serial port, you will need to purchase a USB to 9 pin serial converter).  We now actually recommend our FTDI console cable and no longer stock the converter cables.  Here is a link to check those out, they are awesome!  FTDI Console Cable
    3. With the supplied rollover cable, insert the RJ-45 connector into the console port.
    4. Launch HyperTerminal and name the console session.
    5. Select COM1 as your “Connect Using” port(make sure you connected the console cable to COM1 on your PC.
    6. Configure the baud rate and character format of HyperTerminal to match these console port default characteristics:
      o 9600 baud
      o 8 data bits
      o 1 stop bit
      o No parity
      o NO FLOWCONTROL
    7. Turn the Cisco unit on and now you should see the boot process in HyperTerminal of your unit.
    8. Press ENTER to connect to your Cisco unit. This will bring you in User mode.
    9. At the router> prompt, type in a question mark (?) This will list all the User mode commands. Feel free to play with all the available commands. You are in a safe zone.
      Nothing will be damaged.
    10. Press the Enter key to the view the commands line by line.
    11. Press the SPACEBAR to view the commands a full screen at a time.
    12. Type enable or en, the press ENTER. This will put you in Privileged mode, where you can change and view the router configuration.
    13. At the router# prompt, type a question mark (?) This will list all available commands in the Router Global configuration mode. Use these commands with cautions.
    14. Type config and ENTER.
    15. Press ENTER to configure your router using your terminal.
    16. At the router(config)# prompt, type another question mark (?) This will list all commands available in router configuration mode. Use these commands with cautions.
    17. Press the CONTROL key and the letter Z at the same time. Notice how the take you out of Configuration mode and brings you back in Privileged mode.
    18. Type disable. This will put you into where you begin – the User mode.
    19. Type exit, which will log you out of the unit.

    We hope you found this Cisco certification article helpful. We pride ourselves on not only providing top notch Cisco CCNA exam information, but also providing you with the real world Cisco CCNA skills to advance in your networking career.

    Sours: https://www.certificationkits.com/connect-pc-cisco-router/
    Cisco SF300-48PP PoE+ Managed Switch Unboxing - Quick Mini Configuration!

    Mom, kindly asked, Smiling, like, sweetly, Daughters, stand side by side - Fearsomes, hit parade. - There is a ball in the palace today, - The messenger babbled to them, - There will be dances and a buffet. Will you come.

    You will also like:

    The woman shuddered, she, with difficulty picked up the book from the floor and clamped it in her teeth. Having untied the leash, and taking the box, the man led the slave to her room. - Go, wash yourself, you creature, you smell like a dog.



    4199 4200 4201 4202 4203