Teaching how to use the COSI switches
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

185 lines
7.5 KiB

4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
  1. # Using the TL-SG3424
  2. This guide is in no way comprehensive - if you have more curiosities, you should read the manual in the `manuals/TL-SG3424` folder.
  3. ## Contents
  4. * Basic Operations
  5. * Log In
  6. * Overview
  7. * Managing VLAN Configurations
  8. * View VLAN configuration
  9. * Adding/Removing VLAN ID's
  10. * Adding VLAN ID's to a port
  11. * Set up a ACCESS port
  12. * Set up a TRUNK port
  13. * Managing LAG and LACP Configurations
  14. * Managing STP Configurations
  15. * View STP configuration
  16. * Change STP configuration
  17. * Saving Switch Config (!important!)
  18. * Notes on Backups
  19. ## Basic Operations
  20. ### Log in
  21. To log into a network switch while in the lab, enter its IP address into your browser.
  22. A current table of addresses:
  23. Switch Name | IP Address
  24. ---- | ----
  25. swm1 | [](
  26. swm2 | [](
  27. swm3 | [](
  28. swm4 | [](
  29. For these examples, we will be logging into `swm4`.
  30. Once you get to the login page, log in with the typical lab credentials for `csguest`.
  31. ![login screen](images/TL-SG3424/login-screen.png "login screen")
  32. Click `Login`.
  33. ### Overview
  34. This is what you see when you log in.
  35. ![overview](images/TL-SG3424/overview.png "overview")
  36. On the left are the menus that allow you to navigate to different parts of the configuration interface. On the top are the tabs that allow you configure that particular part of the configuration interface, and change the current view.
  37. In this view, we can see what ports are connected. Ports 1 and 18 currently have gigabit connections. 100M connections and 10M connections will look different.
  38. Below that, we have information about the system itself, as well as the configuration IP address and the system uptime, among other tidbits of information.
  39. ## Managing VLAN Configurations
  40. These instructions are for utilization of the VLAN configuration panel.
  41. ### View VLAN configuration
  42. If you click on VLAN, and then 802.1q VLAN, you will see the following:
  43. ![vlan config overview](images/TL-SG3424/vlans-overview.png "vlans overview")
  44. This view shows you what VLAN tags the switch knows about. By default, it only knows about "Default VLAN", and all of the ports will be in ACCESS mode on that VLAN.
  45. If you click on the tab to the right of that, you will see the VLAN port config.
  46. ![vlan port config overview](images/TL-SG3424/vlan-port-config-overview.png "vlan port ovewview")
  47. This view will show you much more detailed information about the ports themselves.
  48. ### Adding and Removing VLAN ID's
  49. To create a VLAN, on the VLAN config overview, click the "Create" button.
  50. You will be greeted by the following screen:
  51. ![add vlan screen](images/TL-SG3424/create-vlan.png "create vlan")
  52. Next, select an unused VLAN ID, and enter it into the first box. In the second box, enter a description. Typcially, in COSI, these are in the following format:
  53. ```
  54. v[vlan ID]_[purpose]
  55. ```
  56. Some examples:
  57. ```
  58. v2_cosi_priv (the private COSI network)
  59. v3_cosi_pub (the public COSI network)
  60. ```
  61. After that, click Apply below the port listing. Adding ports at this screen tends to (unintuitively) fail.
  62. ### Adding VLAN ID's to a port
  63. Depending upon whether your port in question is in ACCESS or TRUNK mode will change the behavior of this step.
  64. In ACCESS mode, when you change the VLAN ID, it will replace any existing VLAN ID with the one you select.
  65. In TRUNK mode, when you change the VLAN ID, it will add/remove the VLAN ID to a list of VLAN ID's that the port is allowed to access.
  66. To add the port to a VLAN, go to the VLAN Config tab, and click Edit under the VLAN you want to add/remove the port from.
  67. You will see the following configuration panel:
  68. ![add or remove ports from vlan](images/TL-SG3424/add-ports-vlan.png "add or remove ports from vlan")
  69. Once you do that, select/unselect the ports you want to change (and remember the behavior as listed above).
  70. Click "Apply" to finish and apply the changes.
  71. ### Set up an ACCESS port
  72. Click on the Port Config tab. You will see the following:
  73. ![port config](images/TL-SG3424/vlan-port-config-overview.png "port config")
  74. To change to ACCESS, select the ports on the left that you want to change, then click ACCESS from the dropdown, and then click "Apply".
  75. Do not try to change the PVID here. It will fail (inexplicably).
  76. ### Set up a TRUNK port
  77. Click on the Port Config tab. You will see the following:
  78. ![port config](images/TL-SG3424/vlan-port-config-overview.png "port config")
  79. To change to TRUNK, select the ports on the left that you want to change, then click TRUNK from the dropdown, and then click "Apply".
  80. Do not try to change the PVID here. It will fail (inexplicably).
  81. ### Troubleshooting
  82. If you get errors about the PVID when changing VLANs accessible on a TRUNK port, change it to a VLAN that will be on the TRUNK after the changes.
  83. ## Managing LAG and LACP Configurations
  84. **TODO**
  85. ## Managing STP configurations
  86. These instructions are for utilization of the STP configuration panel.
  87. **IMPORTANT NOTE:** The OIT link we have will administratively go down automatically if it recieves ANY STP packets! **DO _NOT_** allow STP packets to touch OIT's network. You **MUST** disable STP for these interfaces!
  88. Note: Some of these configs are probably broken in some ways, and need to be fixed in order to operate properly (example, topography of the network is not propogating the way it's supposed to).
  89. ### View STP configuration
  90. Click on the Spanning Tree menu on the left hand side. It looks like this:
  91. ![stp overview](images/TL-SG3424/stp-overview.png "stp overview")
  92. ### Edit STP Configuration
  93. Most of the relevant edits to the switch configuration itself are made on the main STP Config page. You can select whether it's enabled or not, the version (we use `STP`), and some other parameters.
  94. ![stp overview](images/TL-SG3424/stp-overview.png "stp overview")
  95. The CIST Priority is probably the most important - the higher up the network you go, the higher the priority should be. For example, the root of our network is 0, M1 is 4096, and other switches are bigger numbers.
  96. #### Per Port Configurations
  97. If you click on the Port Config link in the left menu, you will be greeted with this.
  98. ![stp port config](images/TL-SG3424/port-config-stp.png "stp port config")
  99. Most of the time, you only need to select the ports, and set the status to Enable or Disable, but sometimes you want to set the path costs and the priority of the link itself.
  100. ## Saving Switch Config
  101. To save the config, click on the "Save Config" option on the left menu. When you click it, it will ask you if you're sure and then save the config. This will take at least a few minutes.
  102. ![save config](images/TL-SG3424/save-config.png "save config")
  103. This step is important, since **if the switch reboots, it will reset to this saved config**, rather than any config you have without saving. This is important, because if you lock yourself out of the switch, it resets when you reboot it, so that you don't need to get to the console and reset the switch entirely and lose ALL of the configuration.
  104. ## Notes on Backups
  105. The best thing to do is NOT screw up the configuration or do a reset. The switch hardly stores any information about how it was configured in the "backup" file, so if you have a reboot, and you didn't save the config to the switch (as above), it can't be restored. Everything besides the root password will be forgotten. The "backup" and "restore" configuration is seriously lacking in any features (and puts out what looks to be an extremely minimal Cisco-style interface listing and config)