{"id":34970,"date":"2019-10-31T22:01:34","date_gmt":"2019-10-31T19:01:34","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-8-nastrojka-svitcha\/"},"modified":"2019-10-31T22:01:34","modified_gmt":"2019-10-31T19:01:34","slug":"trening-cisco-200-125-ccna-v3-0-den-8-nastrojka-svitcha","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-8-nastrojka-svitcha","title":{"rendered":"Cisco 200-125 CCNA v3.0 Training. Day 8. Switch Configuration","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Welcome to the world of switches! Today we'll talk about switches. Imagine you are a network administrator at a new company. A manager approaches you with a 'boxed' switch and asks for it to be configured. You might have thought that this refers to a regular electrical switch (in English, the word 'switch' denotes both a network switch and an electrical switch \u2013 translator's note), but that's not the case \u2013 it refers to a network switch, or Cisco switch.<\/p>\n

\"Cisco
\n
\nSo, the manager hands you a new Cisco switch that is equipped with multiple interfaces. This could be an 8, 16, or 24-port switch. In this case, the slide shows a switch that features 48 ports on the front, divided into 4 sections of 12 ports each. As we learned in previous lessons, there are several interfaces at the back of the switch, one of which is the console port. The console port is used for external access to the device and allows you to see how the switch's operating system is being loaded. <\/p>\n

We have already discussed the scenario where you want to help your colleague and use remote desktop. You connect to their computer, make changes, but if you want your friend to restart the computer, you will lose access and cannot observe what happens on the screen during boot-up. This problem arises if you don\u2019t have external access to that device and are only connected through the network.<\/a><\/noindex> <\/p>\n

But if you have out-of-band access, you can see the boot screen, the IOS unpacking, and other processes. Another way to access this device is to connect to any of the front ports. If you have configured IP address management on this device, as will be shown in this video, you can access it via Telnet. The problem is that you will lose this access as soon as the device powers off. <\/p>\n

Let's take a look at how to perform the initial setup of a new switch. Before we dive into configuration settings, we need to enter a few basic rules. <\/p>\n

\"Cisco
\n
\nFor most of the video lessons, I used GNS3 \u2014 an emulator that allows you to emulate the Cisco IOS operating system. In many cases, I need more than one device, for example, if I'm demonstrating routing. In this case, I might need, say, four devices. Instead of purchasing physical devices, I can use the operating system of one of my devices, connect it to GNS3, and emulate this IOS on several instances of virtual devices. <\/p>\n

So, I don't need to physically have five routers; I can have just one router. I can use the operating system on my computer, install the emulator, and get five instances of devices. In the subsequent video lessons, we will look at how to do this, but for today, the problem with using the GNS3 emulator is that it cannot emulate a switch because a Cisco switch has hardware ASIC chips. This special integrated circuit is what actually makes a switch a switch, so you can't just emulate this hardware function.<\/p>\n

Overall, the GNS3 emulator helps to work with a switch, but there are some features that cannot be accomplished with it. Therefore, for this lesson and some other videos, I used another Cisco software called Cisco Packet Tracer. Don't ask me how to access Cisco Packet Tracer; you can find out about it through Google. I can only say that to gain access, you must be a member of the Network Academy.
\nYou can have access to Cisco Packet Tracer, you can have access to physical devices, or you can use GNS3; you can utilize any of these tools while studying the Cisco ICND course. You can use GNS3 if you have a router, the operating system, and a switch, and it will work without issues. You can use a physical device, or you can use Packet Tracer \u2013 just decide which one suits you best. <\/p>\n

In my video tutorials, I will be using Packet Tracer, so I'll have a couple of videos, one specifically for Packet Tracer and another for GNS3, which I will upload soon. For now, we will use Packet Tracer. Here is what it looks like. If you have access to the Network Academy, you can access this program; if not, you can use other tools.<\/p>\n

\"Cisco
\n
\nSo, since we are discussing switches today, I will note the Switches item, select a model from the 2960 series, and drag its icon into the program window. If I double-click this icon, I will go to the command line interface.<\/p>\n

\"Cisco
\n
\nNext, I see the switch's operating system loading. <\/p>\n

\"Cisco
\n
\nIf you connect a physical device to your computer, you will see the exact same Cisco IOS boot sequence. You can see that the operating system has unpacked, and you can read some usage restrictions and the licensing agreement, as well as copyright information... all of this is displayed in this window. <\/p>\n

Next, the platform on which the OS is running will be shown; in this case, it's the WS-C2690-24TT switch, and all hardware features are displayed. The version of the program is also shown here. Then we proceed directly to the command line; if you remember, we have prompts for the user here. For example, the symbol (>) invites you to enter a command. From the \"Day 5\" tutorial, you know that this is the initial, lower access mode for the device settings, known as user EXEC mode. This access can be obtained on any Cisco device.<\/p>\n

If you are using Packet Tracer, you will have out-of-band OOB access to the device and can observe the device boot process. This program simulates access to the switch via the console port. How do you transition from user EXEC mode to privileged EXEC mode? You type the command \"enable\" and press \"Enter\"; you could also use the prompt by simply entering \"en\" and getting suggestions for commands starting with those letters. If you just type the letter \"e\", the device will not understand what you mean because there are three commands starting with \"e\". But if I type \"en\", the system will recognize that the only word starting with those two letters is enable. Thus, by entering this command, you gain access to privileged EXEC mode.<\/p>\n

In this mode, we can do everything that was shown on the second slide \u2013 change the hostname, set a login banner, Telnet password, enable password entry, configure the IP address, set the default gateway, issue a shutdown command, cancel previously entered commands, and save the changes made to the configuration. <\/p>\n

\"Cisco
\n
\nThese are the 10 basic commands you use when initializing a device. To enter these parameters, you need to use global configuration mode, which we will now access.<\/p>\n

So, the first parameter is the hostname, which applies to the entire device, so it is changed in global configuration mode. For that, we enter the command line parameter Switch (config)#. If I want to change the hostname, I enter in this line hostname NetworKing, press \"Enter\", and see that the device's name Switch has changed to NetworKing. If you connect this switch to a network with many other devices already in place, this name will serve as its identifier among the other network devices, so try to come up with a unique and meaningful name for your switch. For example, if this switch will be installed in the administrator's office, you might name it AdminFloor1Room2. Thus, if you assign the device a logical name, it will be very easy to determine which switch you are connecting to. This is important as it helps avoid confusion with devices as the network expands.<\/p>\n

The following parameter is the Logon Banner. This is the first thing anyone will see when logging into this device using a login. This parameter is set using the command #banner. You can then enter an abbreviation like motd, which stands for Message of The Day. If I enter a question mark on the line, I will receive a message like: LINE with banner-text.<\/p>\n

It may seem confusing, but it simply means that you can enter text starting from any character except for 's', which acts as the delimiter in this case. So, let\u2019s start with an ampersand (&). I press 'Enter', and the system states that any text for the banner can now be entered and should end with the same character (&) with which the line began. So, I started with an ampersand and must finish my message with an ampersand. <\/p>\n

I will start my banner with a line of asterisks (*), and on the next line, I will write 'Most dangerous switch! Do not enter!' I think that's cool; anyone would be scared to see such a welcoming banner.<\/p>\n

\"Cisco
\n
\nThis is my 'Message of The Day'. To check how it looks on the screen, I press CTRL+Z to switch from global mode to privileged EXEC mode, from where I can exit the configuration mode. This is how my message appears on the screen, and this is what anyone logging into this switch will see. This is what is called a logon banner. You can get creative and write anything you want, but I advise you to take it seriously. I mean, some people, instead of sensible text, have placed character images as a welcoming banner that carry no meaningful content. Nothing can prevent you from engaging in such 'creativity', but remember that extra characters overload the device's memory (RAM) and the configuration file used during system startup. The more characters in this file, the slower the switch boots, so try to minimize the configuration file, keeping the banner content clear and concise.<\/p>\n

Next, we will discuss the Console Password. It prevents unauthorized access to the device. Suppose you left the device open. If I were a hacker, I could connect my laptop to the switch using a console cable, log into the switch via the console, and change the password or do something malicious. But if you use a password on the console port, I would only be able to access the system with that password. You wouldn't want someone to simply enter the console and modify any settings on your switch. So, let\u2019s first look at the current configuration. <\/p>\n

Since I am in config mode, I can enter the commands do sh run. The show run command is a privileged EXEC command. If I want to switch from this mode to global mode, I need to use the command 'do'. If we look at the console line, we see that by default there is no password, and it shows line con 0. This line is in one section, and below is another section of the configuration file. <\/p>\n

Since there is nothing in the 'line console' section, this means that when connected to the switch via the console port, I will have direct access to the console. Now, if I type 'end', I can return to privileged mode and then switch to user mode. If I press 'Enter' now, I will go directly into command-line prompt mode because there is no password here; otherwise, the system would have prompted me for it to enter configuration settings.
\nSo, let's press 'Enter' and type in the line con 0, because in Cisco devices everything starts at zero. Since we only have one console, it is abbreviated as 'con'. Now, to set a password, for instance, the word 'Cisco', we need to type in NetworKing (config-line)# command password cisco and hit 'Enter'. <\/p>\n

Now we have set a password, but we still seem to be missing something. Let\u2019s try everything again and exit the settings. Despite setting the password, the system doesn't prompt for it. Why?<\/p>\n

It does not prompt for a password because we are not querying it. We set a password but did not specify the line where it would be checked when traffic starts coming to the device. So what should we do? We need to go back to the line where it says line con 0 and enter the word 'login'.<\/p>\n

\"Cisco
\n
\nThis means you need to check the password, so a login is required to access the system. Let's check what we have accomplished. To do this, exit the settings and return to the banner window. You can see that right below it, there is a line asking for the password. <\/p>\n

\"Cisco
\n
\nIf I enter the password here, I will be able to access the device settings. Thus, we effectively prevented access to the device without your permission, and now only those who know the password can log in. <\/p>\n

Right now, you can see that we have a small problem. If you type something the system does not understand, it thinks it is a domain name and tries to resolve the server's domain name, connecting to the IP address 255.255.255.255.<\/p>\n

\"Cisco
\n
\nThis can happen, and I will show you how to disable this message. You can simply wait for the request timeout, or use the Control+Shift+6 key combination; sometimes it works even on physical devices. <\/p>\n

Next, we need to ensure that the system does not look for a domain name, for this we enter the command 'no IP-domain lookup' and check how it worked. <\/p>\n

\"Cisco
\n
\nAs you can see, now you can work with the switch settings without any problems. If we exit the settings back to the welcome screen and make the same mistake, that is, enter an empty line, the device will not waste time looking for a domain name, but will simply return the message 'unknown command'. So, setting a login password is one of the main things you will need to do on a new Cisco device.<\/p>\n

Next, we will look at the password for the Telnet protocol. If for the console password we had \"con 0\" in the line, for the default Telnet password the parameter is \"line vty\", which means the password is set in virtual terminal mode, as Telnet is not a physical but a virtual line. The first parameter of line vty is 0, and the last one is 15. If we set the parameter to 15, it means that you can create 16 lines for accessing this device. That is, if we have multiple devices in the network, when connecting to the switch via Telnet, the first device will use line 0, the second will use line 1, and so on up to line 15. Thus, up to 16 people can connect to the switch at the same time, and the seventeenth person attempting to connect will be informed by the switch that the connection limit has been reached. <\/p>\n

We can set a common password for all 16 virtual lines from 0 to 15, following the same concept as when setting the console password, which means we input the command password in the line and set the password, for example, the word \"telnet\", and then enter the command \"login\". This means we do not want people to access the device via Telnet without a password. Therefore, we instruct to verify the login, and only after that provide access to the system.
\nCurrently, we cannot use Telnet because access to the device via this protocol can only be obtained after configuring some IP address on the switch. Therefore, to check Telnet settings, let's first move to managing IP addresses. <\/p>\n

\"Cisco
\n
\nAs you know, the switch operates at Layer 2 of the OSI model, has 24 ports, and therefore cannot have a specific IP address. But we must assign this switch an IP address if we want to connect to it from another device for managing IP addresses.
\nSo, we need to assign the switch one IP address that will be used for IP management. To do this, we will enter one of my favorite commands, \"show ip interface brief\", and we will be able to see all the interfaces present on this device.<\/p>\n

\"Cisco
\n
\nThus, I see that I have twenty-four FastEthernet ports, two GigabitEthernet ports, and one VLAN interface. VLAN is a virtual network; we will discuss its concept in detail later, but for now, I'll just say that each switch comes with one virtual interface called the VLAN interface. This is the interface we use to manage the switch. <\/p>\n

Therefore, we will try to access this interface and enter the command vlan 1 in the command line. Now you see that the command line has taken the form NetworKing (config-if) #, which means we are in the management interface of the VLAN switch. Now we will enter the command to set the IP address like this: Ip add 10.1.1.1 255.255.255.0 and hit \u2018Enter.\u2019 <\/p>\n

We see that this interface has appeared in the list of interfaces marked as \u2018administratively down.\u2019 If you see such a message, it means that there is a \u2018shutdown\u2019 command for this interface that allows you to disable the port, and in this case, that port is disabled. You can issue this command for any interface that is marked \u2018down\u2019 in the specifications list. For example, you can go to interface FastEthernet0\/23 or FastEthernet0\/24, issue the \u2018shutdown\u2019 command, after which this port will be marked as \u2018administratively down\u2019 in the list of interfaces, meaning it is disabled. <\/p>\n

So, we have looked at how the \u2018shutdown\u2019 command works to disable a port. To enable a port or turn something on in the switch, the Negating Command, or \u2018negation of the command,\u2019 is used. For example, in our case, using such a command would mean \u2018no shutdown.\u2019 This is a very simple command consisting of just one word: \u2018no\u2019 \u2014 if the command \u2018shutdown\u2019 means \u2018disable the device,\u2019 then the command \u2018no shutdown\u2019 means \u2018enable the device.\u2019 Thus, by negating any command with the particle \u2018no,\u2019 we instruct the Cisco device to perform the exact opposite action. <\/p>\n

\"Cisco
\n
\nNow I will re-enter the command \u2018show ip interface brief,\u2019 and you will see that the state of our VLAN port, which now has the IP address 10.1.1.1, has changed from \u2018down\u2019 to \u2018up\u2019; however, the protocol line still shows \u2018down.\u2019<\/p>\n

Why isn\u2019t the VLAN protocol working? Because it currently sees no traffic passing through this port, since, if you remember, there is only one device in our virtual network \u2013 a switch, and in this case, there can be no traffic. Therefore, we will add another device to the network, a personal computer PC-PT(PC0).
\nYou don\u2019t need to worry about Cisco Packet Tracer; in one of the next videos, I will explain in detail how this program works. For now, we will just have a general overview of its capabilities. <\/p>\n

\"Cisco
\n
\nSo, I will now activate the PC simulation, click on the computer icon, and run a cable from it to our switch. The console displays a message stating that the VLAN1 interface protocol has changed its state to UP, since we now have traffic from the PC. As soon as the protocol detected traffic, it immediately transitioned to the ready state. <\/p>\n

If you run the 'show ip interface brief' command again, you will see that the FastEthernet0\/1 interface has changed its state and its protocol state to UP, because it is the one connected to the computer via the cable through which traffic is coming. The VLAN interface also transitioned to the active state because it 'saw' traffic on this port. <\/p>\n

Now we will click on the computer icon to see what it represents. It is just a PC simulation running Windows OS, so we will go to the network configuration settings to assign the computer an IP address of 10.1.1.2 and set the subnet mask to 255.255.255.0.<\/p>\n

\"Cisco
\n
\nWe don't need a default gateway because we are on the same network as the switch. I will now attempt to ping the switch with the command 'ping 10.1.1.1', and as you can see, the ping was successful. This means that the computer can now access the switch, and we have an IP address of 10.1.1.1 through which the switch is managed. <\/p>\n

You may wonder why the first request from the computer received a 'timeout' response. This happened because the computer did not know the MAC address of the switch and had to send an ARP request first; hence the first attempt to reach the IP address 10.1.1.1 failed.<\/p>\n

Let's try using the Telnet protocol by typing \"telnet 10.1.1.1\" in the console. We are connecting to this computer via Telnet with the address 10.1.1.1, which is nothing more than a virtual interface of the switch. After that, in the command line terminal window, I immediately see the welcome banner of the switch that we previously set up.<\/p>\n

\"Cisco
\n
\nPhysically, this switch can be located anywhere \u2013 on the fourth floor or the first floor of the office, but we can locate it using Telnet regardless. You see that the switch prompts for a password. What is this password? We set two passwords \u2013 one for the console and another for VTY. Let's first try entering the console password \"cisco\", and you see that it is not accepted by the system. Then I try the password \"telnet\" for VTY, and it worked. The switch accepted the VTY password because line vty password is what works with the Telnet protocol used here.<\/p>\n

I am now trying to enter the command 'enable', to which the system responds 'no password set' \u2014 meaning that the switch has granted me access to user mode settings but has not given me privileged access. To enter EXEC privileged mode, I need to set what is called an 'enable password', that is, to enable a password. For this, we return to the switch configuration window to allow the system to use a password. <\/p>\n

\"Cisco
\n
\nTo do this, with the command \"enable\", we switch from user EXEC mode to privileged EXEC mode. Since we enter \"enable\", the system also requires a password, because this function will not work without using a password. Therefore, we return to simulating console access. I already have access to this switch, so in the IOS command line interface window on the NetworKing (config) # enable line, I need to add \"password enable\", which means activating the password usage feature.
\nNow let me try typing 'enable' again in the computer's command line and press 'Enter', after which the system prompts for a password. What is this password? After I entered the command 'enable', I gained access to EXEC privileged mode. Now I have access to this device through the computer, and I can do anything I want with it. I can go to 'conf t', I can change the password or the hostname. Right now, I will change the hostname to SwitchF1R10, which means 'first floor, room 10'. Thus, I changed the switch's name, and now it shows me the location of this device in the office. <\/p>\n

If I return to the switch command line interface window, I can see that its name has changed, and I did this remotely during a Telnet session. <\/p>\n

This is how we gain access to the switch via Telnet: we assigned a hostname, created a login banner, set a console password, and a Telnet password. Then we enabled password input, created IP management capability, activated the 'shutdown' feature, and allowed denial of the command.<\/p>\n

Next, we need to assign a default gateway. For this, we go back to the switch's global configuration mode, type the command 'ip default-gateway 10.1.1.10' and press 'Enter'. You may ask why a default gateway is needed if our switch is a Layer 2 device of the OSI model. <\/p>\n

In this case, we connected a PC directly to the switch, but let's assume we have multiple devices. Suppose the device from which I initiated Telnet, that is, the computer, is on one network, while the switch with an IP address of 10.1.1.1 is on another network. In this case, the Telnet traffic came from a different network, and the switch needs to send it back but doesn't know how to reach that network. The switch determines that the IP address of the computer belongs to another network, so a default gateway is needed to communicate with it. <\/p>\n

\"Cisco
\n
\nThus, we set the default gateway for this device so that when traffic comes from another network, the switch can send a response packet to the default gateway, which will forward it to the intended destination. <\/p>\n

Now we will finally discuss how to save this configuration. We have made so many changes to this device's settings that it is time to save them. There are two ways to save. <\/p>\n

One way is to enter the 'write' command in privileged EXEC mode. I type this command, press 'Enter', and the system responds with the message 'Building configuration \u2014 OK', meaning the current configuration of the device has been successfully saved. What we did before saving is called the 'running configuration of the device'. It is stored in the switch's RAM and will be lost after power off. Therefore, we need to write everything from the running configuration to the startup configuration. <\/p>\n

Regardless of what is in the running configuration, the 'write' command copies this information and saves it to the startup configuration file, which is independent of the RAM and resides in the switch's non-volatile memory, NVRAM. Upon booting the device, the system checks if there is a startup configuration in NVRAM and turns it into the running configuration by loading the parameters into RAM. Each time we use the 'write' command, the parameters of the running configuration are copied and saved in NVRAM. <\/p>\n

The second way to save configuration parameters is to use the older command 'do write'. If we use this command, we first need to enter the word 'copy'. After that, the Cisco operating system will ask where to copy the configuration settings from: from the file system via FTP or flash, from the running configuration, or from the startup configuration. We want to make a copy of the running configuration, so we enter that phrase. The system will then display a prompt asking where to copy the parameters to, and we indicate 'startup-configuration'. Thus, we have copied the running configuration to the startup configuration file.<\/p>\n

Be very careful with these commands, as copying the startup configuration into the running configuration\u2014something that sometimes happens when setting up a new switch\u2014will erase any changes made and result in a boot with zero parameters. Therefore, you need to be mindful of what and where you plan to save after adjusting the switch configuration settings. This way, you save the configuration, and now, if you reboot the switch, it will return to the same state it was in before the reboot. <\/p>\n

So, we've discussed how to configure the basic settings of a new switch. I know many of you are seeing the device's command line interface for the first time, so it may take some time to grasp everything shown in this tutorial. I recommend watching this video a few times until you understand how to use the different configuration modes: user EXEC mode, privileged EXEC mode, global configuration mode, and how to use the command line to enter subcommands, change the hostname, create a banner, and so on. <\/p>\n

We have covered the essential commands that you must know and which are used during the initial configuration of any Cisco device. If you know the commands for a switch, you also know the commands for a router. <\/p>\n

Just remember which mode each of these basic commands is executed from. For example, the hostname and login banner are part of global configuration; to assign a password to the console, you need to use the console, and the Telnet password is assigned in the VTY line from 0 to 15. To manage the IP address, you need to use the VLAN interface. Keep in mind that the 'enable' feature is disabled by default, so you might need to enable it by entering the 'no shutdown' command. <\/p>\n

If you need to assign a default gateway, you enter global configuration mode, use the 'ip default-gateway' command, and assign the gateway an IP address. Finally, you save the changes using the 'write' command or by copying the running configuration to the startup configuration file. I hope this video has been very informative and helped you in mastering our networking course. <\/p>\n

\r\n \"Play\r\n
<\/div>\r\n <\/div><\/center>
\nThank you for staying with us. Do you enjoy our articles? Would you like to see more interesting materials? Support us by placing an order or recommending us to your friends. 30% discount for Habr users on a unique entry-level server designed by us for you:<\/b> The whole truth about VPS (KVM) E5-2650 v4 (6 Cores) 10GB DDR4 240GB SSD 1Gbps starting at $20, or how to properly divide a server?<\/a><\/noindex> (options available with RAID1 and RAID10, up to 24 cores and up to 40GB DDR4).<\/p>\n

VPS (KVM) E5-2650 v4 (6 Cores) 10GB DDR4 240GB SSD 1Gbps free until summer<\/b> when paid for a term of six months or more, you can order here<\/a><\/noindex>.<\/p>\n

Dell R730xd for half the price?<\/b> Only with us 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100TB starting at $199<\/a><\/noindex> in the Netherlands! Dell R420 \u2014 2x E5-2430 2.2GHz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 from $99!<\/b><\/b> Read about how To build a corporate-class infrastructure using Dell R730xd E5-2650 v4 servers costing 9000 euros for peanuts?<\/a><\/noindex>
\n
Source: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0414\u043e\u0431\u0440\u043e \u043f\u043e\u0436\u0430\u043b\u043e\u0432\u0430\u0442\u044c \u0432 \u043c\u0438\u0440 \u0441\u0432\u0438\u0442\u0447\u0435\u0439! \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440\u0430\u0445. \u041f\u0440\u0435\u0434\u043f\u043e\u043b\u043e\u0436\u0438\u043c, \u0447\u0442\u043e \u0432\u044b \u2013 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440 \u0438 \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u0435\u0441\u044c \u0432 \u043e\u0444\u0438\u0441\u0435 \u043d\u043e\u0432\u043e\u0439 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438. \u041a \u0432\u0430\u043c \u043f\u043e\u0434\u0445\u043e\u0434\u0438\u0442 \u043c\u0435\u043d\u0435\u0434\u0436\u0435\u0440 \u0441\u043e \u0441\u0432\u0438\u0442\u0447\u0435\u043c \u00ab\u0438\u0437 \u043a\u043e\u0440\u043e\u0431\u043a\u0438\u00bb \u0438 \u043f\u0440\u043e\u0441\u0438\u0442 \u0435\u0433\u043e \u043d\u0430\u0441\u0442\u0440\u043e\u0438\u0442\u044c. \u0412\u043e\u0437\u043c\u043e\u0436\u043d\u043e, \u0432\u044b \u043f\u043e\u0434\u0443\u043c\u0430\u043b\u0438, \u0447\u0442\u043e \u0440\u0435\u0447\u044c \u0438\u0434\u0435\u0442 \u043e\u0431 \u043e\u0431\u044b\u0447\u043d\u043e\u043c \u044d\u043b\u0435\u043a\u0442\u0440\u0438\u0447\u0435\u0441\u043a\u043e\u043c \u0432\u044b\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u0435 (\u0432 \u0430\u043d\u0433\u043b\u0438\u0439\u0441\u043a\u043e\u043c \u044f\u0437\u044b\u043a\u0435 \u0441\u043b\u043e\u0432\u043e switch \u043e\u0431\u043e\u0437\u043d\u0430\u0447\u0430\u0435\u0442 \u0438 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440, \u0438 \u044d\u043b\u0435\u043a\u0442\u0440\u0438\u0447\u0435\u0441\u043a\u0438\u0439 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26316,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-34970","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Cisco Training 200-125 CCNA v3.0. Day 8. Switch configuration | ProHoster","description":"Welcome to the world of switches! Today we will talk about switches. Let's assume you are a network administrator and are in the office of a new company.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-8-nastrojka-svitcha","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0422\u0440\u0435\u043d\u0438\u043d\u0433 Cisco 200-125 CCNA v3.0. \u0414\u0435\u043d\u044c 8. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0441\u0432\u0438\u0442\u0447\u0430 | ProHoster","og:description":"\u0414\u043e\u0431\u0440\u043e \u043f\u043e\u0436\u0430\u043b\u043e\u0432\u0430\u0442\u044c \u0432 \u043c\u0438\u0440 \u0441\u0432\u0438\u0442\u0447\u0435\u0439! \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440\u0430\u0445. \u041f\u0440\u0435\u0434\u043f\u043e\u043b\u043e\u0436\u0438\u043c, \u0447\u0442\u043e \u0432\u044b \u2013 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440 \u0438 \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u0435\u0441\u044c \u0432 \u043e\u0444\u0438\u0441\u0435 \u043d\u043e\u0432\u043e\u0439 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438.","og:url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-8-nastrojka-svitcha","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:01:34+00:00","article:modified_time":"2019-10-31T19:01:34+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"34970","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 21:20:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:12:27","updated":"2026-01-21 21:20:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/34970","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=34970"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/34970\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media\/26316"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=34970"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=34970"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=34970"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}