Go to page of
Similar user manuals
-
Switch
Allied Telesis X900-48FE
55 pages 1.06 mb -
Switch
Allied Telesis AT-8000S
48 pages 2.22 mb -
Switch
Allied Telesis at-8116
88 pages 0.23 mb -
Switch
Allied Telesis AT-9924T/4SP-A-20
56 pages 0.46 mb -
Switch
Allied Telesis AT-GS900/24
2 pages 0.21 mb -
Switch
Allied Telesis AT-8000GS/48
4 pages 0.09 mb -
Switch
Allied Telesis AT-X510-28GSX
90 pages 1.2 mb -
Switch
Allied Telesis AT-FS750/24POE
4 pages 0.17 mb
A good user manual
The rules should oblige the seller to give the purchaser an operating instrucion of Allied Telesis x900-48 series, 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 x900-48 series 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 x900-48 series. 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 x900-48 series should contain:
- informations concerning technical data of Allied Telesis x900-48 series
- name of the manufacturer and a year of construction of the Allied Telesis x900-48 series item
- rules of operation, control and maintenance of the Allied Telesis x900-48 series 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 x900-48 series 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 x900-48 series, 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 x900-48 series.
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 x900-48 series 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-16068-00 REV B www .alliedtelesis.com AlliedW ar e TM OS How T o | Intr oduction This document descri bes some generic configur ation examples for Quality of Service (QoS) on A T -9900 and x900 serie s switches running the AlliedW ar e OS. What information will y ou find in this document? This document pr ovides information on the following se[...]
-
Page 2
Page 2 | AlliedW are™ OS Ho w T o Note: QoS co nfiguration 1 . Setting the egr ess rate 1 . Setting the egr ess rate Example 1 - 1 : Setting the egr ess limit of a switch por t Command: set switch port=24 egress limit=640 This command will set the egress limit of port 24 to 640kbps. The granularity is 640kbps. P or t 24[...]
-
Page 3
Page 3 | AlliedW are™ OS Ho w T o Note: QoS co nfiguration 1 . Setting the egr ess rate Example 1 -2: setting the maximum bandwid th limit per ingr ess por t Ingress rate limiting cannot be configur ed on the por t per se, but is achieved b y creating a QoS policy with a bandwidth limited traffic class, and applying that policy to each port. This[...]
-
Page 4
Page 4 | AlliedW are™ OS Ho w T o Note: QoS co nfiguration 1 . Setting the egr ess rate Example 1 -3: Setting the maximum band width limit for each user In example 1 - 1 , we configured an egr e ss rate on por t s. But the granularity of that bandwidth limiting was multiples of 640kbps. T o achieve a fi ner -g rained limiting on egre ss, it is ne[...]
-
Page 5
Page 5 | AlliedW are™ OS Ho w T o Note: QoS co nfiguration 1 . Setting the egr ess rate Example 1 -4: Setting the maximum bandwidth limit for each IP subnet This example is very sim ilar to example 1 -3, except that it is assu med that a whole subnet is attached to each por t, not just a single device on each port. This set of commands will set t[...]
-
Page 6
Page 6 | AlliedW are™ OS Ho w T o Note: QoS co nfiguration 1 . Setting the egr ess rate Example 1 -5: Setting the maximum ba ndwidth limit of VLANs Note: The por tgr oup feature is not supported before softwa r e release v2.7.5. If using an earlier softwar e release, use the port parameter on the policy instead. create class=1 vlan=2 create class[...]
-
Page 7
Page 7 | AlliedW are™ OS Ho w T o Note: QoS co nfiguration 2. Setting the priority on a pack et 2. Setting the priority on a pack et Example 2- 1 : Setting the La y er 2 (VLAN/802. 1 p) priority per ingress port Here we assign differ ent 802. 1 p values to pack ets a rriving on diff erent ports. These values are also known as the La y er 2 (L2) o[...]
-
Page 8
Page 8 | AlliedW are™ OS Ho w T o Note: QoS co nfiguration 2. Setting the priority on a pack et Example 2-2: Setting the La y er 2 (VLAN/802. 1 p) priority per VLAN This set of commands will set the La yer 2 pr iority of VLAN2, VLAN3 and VLAN4 traffics pack ets, received on ports 1 to 20, to 6, 5 and 4 r espectivel y . create class=1 vlan=2 creat[...]
-
Page 9
Page 9 | AlliedW are™ OS Ho w T o Note: QoS co nfiguration 2. Setting the priority on a pack et Example 2-3: Setting the La y er 3 (T OS/DCSP) priority per ingress port Use the same configu ration pro vided i n Example 2- 1 on page 7 , but change the following line: set qos dscpmap=premarkin g dscp=< incoming-dscp > newpriority=< new- pr[...]
-
Page 10
Page 10 | AlliedW are™ OS Ho w T o Note: QoS configuration 3. Setting the egr ess queues 3. Setting the egr ess queues In this section we look at methods f or direct ing certain packets into certain queues on the egress port. Example 3- 1 : Setting the egress queue accor din g to the L2 priority of the incoming pack et The priority-to-queue map i[...]
-
Page 11
Page 11 | AlliedW are™ OS Ho w T o Note: QoS configuration 3. Setting the egr ess queues Example 3-2: Setting the egress qu eue according to the ingr ess port This set of commands will set the egress queue of an y traffic receiv ed from port 1 to egress queue 6, from port 2 to egress queue 5, etc . create class=1 create qos flow=1 add qos flow=1 [...]
-
Page 12
Page 12 | AlliedW are™ OS Ho w T o Note: QoS configuration 3. Setting the egr ess queues Example 3-3: Configuring WRR for egr ess queues This example is used for configuring WRR on eg ress queues accor ding to the ingress port of the traffic. This set of commands will set the egress queue of an y traffic receiv ed from port 1 to egress queue 6, f[...]
-
Page 13
Page 13 | AlliedW are™ OS Ho w T o Note: QoS configuration Full QoS scenario 1 : tier ed ser vices for a single customer Full QoS scenario 1 : tier ed ser vices f or a single customer In this section, we will build up a r elatively complex QoS configuration to support a scenario r equiring quite precise contr ol over th e traffic passing thr ough[...]
-
Page 14
Page 14 | AlliedW are™ OS Ho w T o Note: QoS configuration Full QoS scenario 1 : tier ed ser vices for a single customer Bronz e traffic is also allow ed to burst up to the full egr ess bandwidth of the uplink port, but when congestion occurs, will be thr ottled back in fav our of Gold traffic , and will share the r ema ining bandwidth with Silv [...]
-
Page 15
Page 15 | AlliedW are™ OS Ho w T o Note: QoS configuration Full QoS scenario 1 : tier ed ser vices for a single customer The act of assigning packets in a particular traffic class to a par ticular egress queue is achiev ed in the pre-marking process. This r equ ires that the pre-marking DSCP map table be set up to send packets to a ppropriate que[...]
-
Page 16
Page 16 | AlliedW are™ OS Ho w T o Note: QoS configuration Full QoS scenario 1 : tier ed ser vices for a single customer The Gold traffic must be strictly limited to 2Mbps This is achiev ed by configuring a maxbandwid th on that traffic class, and dropping bandwidthclass 3 traffic: set qos trafficclass=3 ma xbandwidth=2mbps maxburst=20Kbytes drop[...]
-
Page 17
Page 17 | AlliedW are™ OS Ho w T o Note: QoS configuration Full QoS scenario 1 : tier ed ser vices for a single customer RED cur ves—a r efresher Random Early Disc ard cur ve s are bandwidth clas s a ware, and can drop low er priority packets when sev ere congestion occurs, with pr ogr essiv ely mor e and higher priority pack ets dropped until [...]
-
Page 18
Page 18 | AlliedW are™ OS Ho w T o Note: QoS configuration Full QoS scenario 2: bandwidth limiting of m ultiple customers Full QoS scenario 2: bandwidth limiting of multiple customers In this section, we will build up another r e lativel y complex QoS configuration to suppor t a differ ent scenario. The scenario is an ISP pr oviding connectivity [...]
-
Page 19
Page 19 | AlliedW are™ OS Ho w T o Note: QoS configuration Full QoS scenario 2: bandwidth limiting of m ultiple customers The configuration r equired to impose these bandwidth limits would be: Limiting the outgoing traffic: create qos policy=1 dtcdr opbwclass3=yes dtcmaxbandwidth=1Mbps dtcmaxburst=10Kb create qos policy=2 dtcdr opbwclass3=yes dtc[...]
-
Page 20
Page 20 | AlliedW are™ OS Ho w T o Note: QoS configuration Full QoS scenario 2: bandwidth limiting of m ultiple customers create qos traff=9 set qos traff=9 maxband=5 Mbps maxburst=10Kb dropbwc=yes add qos traff=9 flow=9 create qos traff=10 set qos traff=10 maxband= 2Mbps maxburst=10Kb dropbwc=yes add qos traff=10 flow=10 create qos poli=6 add qo[...]
-
Page 21
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 | [...]