A brand new switch just arrive at my place.
Boss said it’s going to replace some old HP switch that’s been bothering me. After some configurations has been done, I think it’s time to write about how to do a basic onfiguration of Dell’s Force10 switch. Learning it’s command is rather easy, especially If you’ve been used tinkering with Cisco routers and switch. Let’s begin from the basic.
First do a hard console and set the IP address if you want to connect it to your existing network and to be able to remotely configure it via internet. Decide which port you would use, and then you can “tag” the vlan to make it a trunk or access depending on your needs.
No port configuration needed if you want to allow the vlans.
For example if you want to allow vlan 1313 into port 10, you must first enter the vlan hierarchy and tag (or un-tag) the port. For better understanding, please look at the sample below:
SW-F10(conf-if-gi-0/9)#show config ! interface GigabitEthernet 0/9 no ip address switchport no shutdown
As you can see the port had only default parameters, and you shouldn’t tinker more with it at this time:
- no ip address : you have the idea. This command doesn’t allowed to have an IP on them
- switchport : this command makes the port acted like a layer 2 switch
- no shutdown : this command makes the port alive
Then how do you allow the vlans? Firstly you have to create them. Look at the sample below:
SW-F10#conf t SW-F10(conf)#int vlan 1313 SW-F10(conf-if-vl-1313)#description "V-1313 Test" SW-F10(conf-if-vl-1313)#untagged gigabitethernet 0/9 SW-F10(conf-if-vl-1313)#tagged gigabitethernet 0/11 SW-F10(conf-if-vl-1313)#show config ! interface Vlan 1313 description "V-1313 Test" no ip address tagged GigabitEthernet 0/11 untagged GigabitEthernet 0/9
In this example, I’m creating vlan 1313 and set it to be allowed in port number 9 and 11. If you want to trunk it, you should use the tagged command. Otherwise, you can use the untagged command. You can put IP in vlan by changing the “no ip address” command to “ip address x.x.x.x/x”.
If you have an existing network of 10.0.0.0/24 and gateway of 10.0.0.1, you can put, for example, 10.0.0.5/24 in the ip address and making it reachable within your network. Remember to set the default route so you can remote this switch via telnet. Try this command below:
! ip route 0.0.0.0/0 10.0.0.1 !
Now that the Switch’s IP have been set and you can remote via telnet, it’s time to set your username.
There are many categories that you can choose, known as privilege level, from super-admins to read only user. Now, I would like to show you how to set the super-admin user for your switch. simply set by following input
SW-F10(conf)#username arya privilege 15 password 7 aryaganteng
privilege is ranging from 0 to 15. 0,1 and 15 are the defaults. I personally think that 0 is for read, 1 is for write, and 15 for full access. 2 to 14 are for custom privilege which you can decide on what he can and can not do.
After deciding your privilege level, just write “password” followed by 0 for unencrypted password or 7 for encrypted password. What’s the difference? well, for safety reasons obviously. Other users may see your password through “show running-configuration” command if you decide to not encrypting your password. Below are the differences between encrypted and unencrypted password when you show all configurations
username arya password 7 84035fbc955ac45e privilege 15
username arya password 0 aryaganteng privilege 15
Don’t forget to create and enable SNMP.
Creating SNMP community can be handy. Especially if you want to graph an interface or two. Graphing is quite important if you want to know how much traffic that flows through certain interface.
SW-F10(conf)#snmp-server community arya rw
Congratulations! now that the basic configuration is done. You can now assign the ports and remotely access it with your own credentials anywhere, anytime.