Go to page of
Similar user manuals
-
Switch
Allied Telesis AT FS709FC AT-FS709FC AT-FS709FC
46 pages 0.26 mb -
Switch
Allied Telesis SB251-13
66 pages 0.31 mb -
Switch
Allied Telesis AT -8000S/24
3 pages 0.27 mb -
Switch
Allied Telesis X3112
104 pages 4.11 mb -
Switch
Allied Telesis AT-GS950/48
60 pages 1.92 mb -
Switch
Allied Telesis AT-GS950/16
44 pages 1.64 mb -
Switch
Allied Telesis AT-9000/12POE
86 pages 0.42 mb -
Switch
Allied Telesis Patch 54266-02
14 pages 0.26 mb
A good user manual
The rules should oblige the seller to give the purchaser an operating instrucion of Allied Telesis Layer 3 Switches, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.
What is an instruction?
The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Allied Telesis Layer 3 Switches one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.
Unfortunately, only a few customers devote their time to read an instruction of Allied Telesis Layer 3 Switches. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.
What should a perfect user manual contain?
First and foremost, an user manual of Allied Telesis Layer 3 Switches should contain:
- informations concerning technical data of Allied Telesis Layer 3 Switches
- name of the manufacturer and a year of construction of the Allied Telesis Layer 3 Switches item
- rules of operation, control and maintenance of the Allied Telesis Layer 3 Switches item
- safety signs and mark certificates which confirm compatibility with appropriate standards
Why don't we read the manuals?
Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Allied Telesis Layer 3 Switches alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Allied Telesis Layer 3 Switches, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Allied Telesis service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Allied Telesis Layer 3 Switches.
Why one should read the manuals?
It is mostly in the manuals where we will find the details concerning construction and possibility of the Allied Telesis Layer 3 Switches item, and its use of respective accessory, as well as information concerning all the functions and facilities.
After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.
Table of contents for the manual
-
Page 1
C613-16103-00 REV A www .alliedtelesis.com How T o | Intr oduction Allied T elesis switches include a range of sophisti cated security features at la y er 2 and la yer 3. This How T o Note des cribes these featur es and includes brief examples of ho w to configure them. The implementations shown in this Ho w T o Note should be thought of as industr[...]
-
Page 2
Which pr oducts and software v ersions does this information apply to? Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 2 Appendix: Configuration scripts for MA C-for ced forwarding example ... ................................ 27 Edge switch 1 ............... ............................ ........................... .........[...]
-
Page 3
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 3 Securing the de vice Securing the de vice The first step towar ds making a secur e network is to secur e the netw orking equipment itself. There ar e two aspects to this. Firstly , ph ysical security is vital—lock your netw orking equ ipment a wa y . Secondly , straight af[...]
-
Page 4
Pr otecting the network Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 4 Ser vice pro viders need to pre vent storms fr om disrupting ser vices to customers. AlliedW are offe rs t he fo llow ing op ti ons for m iti gat in g st orm s: z limiting broadcasts and m ulticasts on a por t ( “Bandwidth limiting” on page 4 ) z [...]
-
Page 5
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 5 Pr otecting the network Using QoS policy-based storm pr otection P olicy-based storm protection lets y ou specify one of a range of actions for the s witch to take when it detects a br oadcast storm. It is a par t of the QoS functionality . P olicy-based storm protection is [...]
-
Page 6
Pr otecting the network Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 6 Example The following example applie s storm protection to classified br oadcast traffic on por t 1 . If there is a storm, it tak es the link down f or 60 seconds. set switch enhancedmode=qoscounters Reboot after turning on enhanced mode. create class[...]
-
Page 7
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 7 Pr otecting the network 2. Set the sensitivity in detecting rapid MA C mo vement, by using the f ollowing command to tell the switch how many times a MA C addr ess can move ports in one second: set switch thrashlimit=5..255 Configuration on trunk groups Rapid MA C movement p[...]
-
Page 8
Pr otecting the network Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 8 IGMP filtering IGMP filtering lets you dictate exac tly which multicast gr oups a spec ific port can receiv e , by cr eating a fil ter list and applying it to the port. Differ ent por ts ma y ha ve diff erent filter lists applied to them. If desire d,[...]
-
Page 9
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 9 Managing the de vice securel y Mana ging the de vice securel y In Ethernet and br oadc ast netw orks the pri vacy of traffic is not g uaranteed. Hubs and networks outside the administrator's contr ol ma y leak sensitive data to unwanted r ecipients. A hack er ma y even [...]
-
Page 10
Managing the de vice securel y Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 10 Using SSL for secur e w eb access If you pr efer to configur e the switch using the conv enient we b-based GUI, then this is un encr ypted by default. SSL lets y ou use the GUI securely , by using HTTPS instead of HTTP . 1. Add a security offi[...]
-
Page 11
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 11 Managing the de vice securel y Examples T o allow the user “ste ve” full r ead, write and notify SNMP access to the switch: enable snmp add snmp view=full oid=1.3.6.1 type=include add snmp group=super-users securitylevel=authPriv readview=full writeview=full notifyview=[...]
-
Page 12
Managing the de vice securel y Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 12 Whitelisting telnet hosts For an y remote management of a netw ork de vice, Allied T elesis recommends y ou use SSH, Secure HTTP ( SSL), or SNMPv3. Theref ore, we recommend y ou block all telnet access to the switch by disabling the telnet ser[...]
-
Page 13
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 13 Managing the de vice securel y Building a whitelist thr ough QoS On A T -8948, A T -9900, A T -990 0s, and x900 Series switches, use classifiers to build a whitelist and QoS to apply it. 1. Create classifiers to mat ch telnet traffic fr om permitted IP addr esses to the swi[...]
-
Page 14
Identifying the user Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 14 Identifying the user This section describes methods for authorising and tracking users and pre venting them fr om changing their identi ty on the netw ork. IP spoofing and tracking Unknown users who attempt to change IP ad dres s—to cir cumvent billin[...]
-
Page 15
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 15 Identifying the user Rejecting Gratuitous ARP (GARP) Hosts can use GARP to anno unce th eir presence on a subnet. It is a helpfu l mechanism, par ticularly when ther e is a chance of duplicate addresses. Ho wev er , attack ers can use GARP to penetrate the networ k b y addi[...]
-
Page 16
Identifying the user Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 16 For mor e information about setting up DHCP snooping, see How T o Use DHCP Snooping, Option 82 and Filtering on Rapier , A T -8800 and A T -8600 Ser ies Switc hes or How T o Use DHCP Snooping, Option 82 and Filtering on x900 Ser ies Switches . These How[...]
-
Page 17
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 17 Identifying the user Using DHCP snooping to track clients If yo u r D H C P s e r ve r s u p po r ts i t , yo u c an u s e “option 82” to record mor e information about DHCP clients. This enhances y o ur ability to track users. The switch can pass option 82 information [...]
-
Page 18
Pro tecting the user Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 18 Pr otecting the user This section describes the following methods of pr otecting users fr om other users on the network: z “Using private VLANs” on page 18 . This feature isolates s witch por ts in a VLAN from other switch ports in the same VLAN. z [...]
-
Page 19
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 19 Pro tecting the user Example T o create a private VLAN with por ts 2-6 in it, with an uplink trunk group of por ts 24 and 2 5: create vlan=example vid=2 private add vlan=2 port=24-25 frame=tagged uplink add vlan=2 port=2-6 T o re move ports from the VLAN: # remove port 4: d[...]
-
Page 20
Pro tecting the user Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 20 The following figur e shows a network that can use either local pr oxy ARP or MA C-for ced forwar ding—the examples in both the fo llowing sections r efer to this netw ork. Local pr oxy ARP In a network configuration lik e the pre vious figure, each e[...]
-
Page 21
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 21 Pro tecting the user Configuration of edge swi tc hes 1. Create the VLANs, specifying that the y are pr ivate. Mak e a different VLAN for each type of traffic that y o u want to contr ol differentl y . 2. Add the uplink and private por ts to the VLANs as tagged ports. 3. Co[...]
-
Page 22
Pro tecting the user Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 22 Use the following configuration f or edge s witches 2 and 3 (A T -8648 s witches in this example): ena stp=default set stp=default mode=rapid create vlan="voice" vid=101 private add vlan=101 port=49-50 uplink frame=tagged add vlan=101 port=1-4[...]
-
Page 23
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 23 Pro tecting the user # Create a classifier to match all traffic in VLANs 101-104 create class=10 ipsa=192.168.0.0/16 ipda=192.168.0.0/16 # Create a classifier to match voice traffic create class=100 ipsa=192.168.1.0/24 ipda=192.168.1.0/24 # Create a classifier to match mana[...]
-
Page 24
Pro tecting the user Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 24 Configuration of edge swi tc hes 1. Create a VLAN f or each type of ser vice (for example , voice, video, and data). With so ftw are vers io ns 2 91 -04 and ea rli er , th e V LAN s mu st b e pr iv ate VLA Ns . W ith so ftw are versions 291-05 and later[...]
-
Page 25
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 25 Pro tecting the user z Ho w T o Configure Micr osoft® Windows XP Vir tual Private Network (V PN) c lient inter operability without NA T -T suppor t z Ho w T o Configure Micr osoft® Windows XP Vir tual Private Network (V PN) c lient inter operability with NA T -T suppor t [...]
-
Page 26
Pro tecting the user Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 26 T o block the W32.Slammer worm on port 1 , which does not ha ve an SQL client or s er ver attached to it: create classifier=1 udpdport=1434 protocol=ip iport=1 add switch hwfilter classifier=1 action=discard Blocking worms thr ough QoS actions On A T -8[...]
-
Page 27
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 27 Appendix: Configuration scripts for MA C-forced f orwarding example Appendix: Configuration scripts for MA C-for ced forwar ding example In this example (fr om page 23 ), the edge switches can be an y of the following switches: z Rapier 1 6fi and Rapier 24i (but not Rapier [...]
-
Page 28
Appendix: Configuration scripts for MA C-forced f orwarding example Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 28 Edge s witch 2 Edge switch 2 is connected to port 50 of edge switch 1 . The configuration is similar to edge swi tc h 1 —differ enc es are in bold : # System configuration set system name="Edge Swit [...]
-
Page 29
Create A Secure Netw ork With Allied T elesis Managed La yer 3 Sw itches 29 Appendix: Configuration scripts for MA C-forced f orwarding example Edge s witch 3 Edge switch 3 is connected to port 49 of edge switch 1 . The configuration is similar to edge swi tc h 1 —differ enc es are in bold : # System configuration set system name="Edge Swit [...]
-
Page 30
Appendix: Configuration scripts for MA C-forced f orwarding example Creat e A Secure Netw ork With Allied T elesis Managed La yer 3 Switches 30 Access Router set system name="Access Ro uter" # Create a VLAN for access ing the Internet, SIP server and multicast groups create vlan=CoreNetwork vi d=28 # Create the other VLANs create vlan=Voi[...]
-
Page 31
USA Headq u ar ters | 19800 Nor th Cr eek Parkwa y | S u ite 200 | Bothell | WA 98011 | USA | T: +1 800 424 4284 | F: +1 425 481 3895 E u r opea n Headq u ar ters | Via Motta 24 | 6830 Chiasso | Switzerla n d | T: +41 91 69769.00 | F: +41 91 69769.11 Asia-Paci f ic Headq u ar ters | 11 T ai Se ng Li n k | Si ng apor e | 534182 | T : +65 6383 3832 |[...]