English dropdown-ico

Allied Telesis AlliedWare Plus manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Allied Telesis AlliedWare Plus, 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 AlliedWare Plus 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 AlliedWare Plus. 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 AlliedWare Plus should contain:
- informations concerning technical data of Allied Telesis AlliedWare Plus
- name of the manufacturer and a year of construction of the Allied Telesis AlliedWare Plus item
- rules of operation, control and maintenance of the Allied Telesis AlliedWare Plus 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 AlliedWare Plus 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 AlliedWare Plus, 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 AlliedWare Plus.

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 AlliedWare Plus 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-16120-00 REV A www .alliedtelesis.com AlliedW ar e Plus TM OS Ov er vie w of | Intr oduction This How T o Note describes the main f e atures of QoS on s witches running the AlliedW ar e Plus OS. The main features include: z Prioritisation and marking Right at the point of ingr ess into the QoS proc ess, pac k ets classified to par ticular clas[...]

  • Page 2

    Page 2 | AlliedW are Plus™ OS: Ov er view of QoS z Ability to see the curr en t state of egress queues There are commands that enable y ou to see statistics relating to e very egress queue on ever y p o r t . Each of these featur es is di scussed in much mor e detail later on in this document. Contents Intr oduction .......... ...................[...]

  • Page 3

    Page 3 | AlliedW are Plus™ OS: Ov er view of QoS Which pr oducts and softwar e version does this Note appl y to? z Pr oducts: SwitchBlade x908, x900-12XT/S, and x900-2 4 series switches z Software v ersions: AlliedW ar e Plus version 5.2.1-0.1 and abov e The pr ocess flo w and methodolog y of the QoS system Befor e discussing the details of the v[...]

  • Page 4

    Page 4 | AlliedW are Plus™ OS: Ov er view of QoS P ack et mark ers There ar e four items tha t are used to mark pack ets as they pass th rough the QoS sys tem. z T wo mark ers tha t are car ried within fields of the p ack et itself: z 802. 1 p: The 802. 1 p or User Priority field in the VLAN tag of an Ethernet frame . This is a 3-bit number , so [...]

  • Page 5

    Page 5 | AlliedW are Plus™ OS: Ov er view of QoS Outline of the QoS pr ocessing flo w Let's look at each QoS pr ocess in the order that they ar e applied to a packet. The f ollowing figure giv es a quick view of the QoS featur es we ar e about to discuss. Initial mapping to an egr ess queue, based on 802. 1 p value Immediately after ingr ess[...]

  • Page 6

    Page 6 | AlliedW are Plus™ OS: Ov er view of QoS Classification Classification is simply a method of dividing the incoming traffic into traffic flows so that pack ets of one type can be treated differ ently to pack ets of another type. T o do this, you create class ma ps and if desi r ed A CLs. Inc oming packets ar e inspected and ma y be classif[...]

  • Page 7

    Page 7 | AlliedW are Plus™ OS: Ov er view of QoS P olicing P olicin g inv olves measuring the ba ndwidth us ed by a policer and comparing the measurement to the bandwidth limits that ha v e been set for the policer . The policing process allocates a temporary bandwi dth class value to packets. It is important to note that the policing pr ocess do[...]

  • Page 8

    Page 8 | AlliedW are Plus™ OS: Ov er view of QoS Queue shaping Each egre ss por t has eight egress queues, wh ich are n umbered 0-7 with 7 being the highest priority queue. Unfor tunately , the queues are of a limited length, so packets cannot be added to them indefinitely; if the switch is congeste d, the queues ma y fill up and no mor e packets[...]

  • Page 9

    Page 9 | AlliedW are Plus™ OS: Ov er view of QoS Scheduling In addition to managing the wa y in which pack ets can be dropped when the egr ess queues for a given port start to fill up, y ou can also configure the method that is used to allocate bandwidth to each of the queue s to transm it pack ets onto the line . There ar e two wa ys that the qu[...]

  • Page 10

    Page 10 | AlliedW are Plus™ OS: Over view of QoS Details of the component pr ocesses, and ho w to configur e them QoS elements: policy maps, class ma ps, policers, matches Some aspects of QoS are configured globall y , such as default mapping of CoS to egress queue. How ever , most aspects are configur ed on a per -por t basis, m ostly as part of[...]

  • Page 11

    Page 11 | AlliedW are Plus™ OS: Over view of QoS Dia gram of the o v erall QoS pr ocess flo w The following figur e summarises the QoS proc ess flow and the commands to configure each stage . The following sections describe the configuration in detail. trust dscp (& set dscp) F rom L2 switch class-map premarking Look up mark-DSCP map Markers [...]

  • Page 12

    Page 12 | AlliedW are Plus™ OS: Over view of QoS Enabling QoS globall y Befor e configuring QoS, you need to enable it by entering the f ollowing command in global configuration mode: awplus(config)#mls qos enable Initial mapping to queue based on ta g When pack ets arrive at a port, they ar e assigned to an egress queue. This is done by the swit[...]

  • Page 13

    Page 13 | AlliedW are Plus™ OS: Over view of QoS awplus(config)#interface < port -number > awplus(config-if)#mls qos cos <0-7> The value you change the CoS to is not used to look up the initial egr ess queue setting; the mls qos queue command still determines the queue for untagged pack ets. Classification The pr ocess of assigning pa[...]

  • Page 14

    Page 14 | AlliedW are Plus™ OS: Over view of QoS Setting new values explicitl y T o explicitly set new values for a particular clas s map , first create the class map (if necessar y), by entering the f ollowing command: awplus(config)#class-map < name > Then simply ente r the following commands: awplus(config)#policy-map < nam e > awp[...]

  • Page 15

    Page 15 | AlliedW are Plus™ OS: Over view of QoS Note that there is just a single mark-dscp ma p f or the whole switch—separate class maps do not ha ve separate mark-dscp maps. The configuration required to use the mark-d scp map is a little mor e complex than the configuration for setting the values explicitly . 1. First, write entries into th[...]

  • Page 16

    Page 16 | AlliedW are Plus™ OS: Over view of QoS Example For the class map called “example” , if y ou wa nt to tak e all traffic with a DSCP of 34, 36 or 38 and premark it to CoS 4, queue 4; CoS 5, qu eue 5; and CoS 6, queu e 6 respectivel y , then enter the following commands: awplus(config)#mls qos map mar k-dscp 34 to new-cos 4 new-queue 4[...]

  • Page 17

    Page 17 | AlliedW are Plus™ OS: Over view of QoS Applying or dinar y policers to class ma ps Ordinar y policers are used when policing traffic in a single class map in a single policy map on a single port. Y ou create them in policy map class configuration mode , which means they ar e attached to that policy map and class ma p at th e time they a[...]

  • Page 18

    Page 18 | AlliedW are Plus™ OS: Over view of QoS Single-rate policing Both ordinar y and aggregate policers can be single-rate . Single-rate policing uses three parameters: z a verage ba ndwidth (in kbps) z minimum burst size (in bytes) z maximum burst size (in bytes) With this combination, the algorithm used to determine the temporar y bandwidth[...]

  • Page 19

    Page 19 | AlliedW are Plus™ OS: Over view of QoS T win-rate policing Both ordinary a nd aggregate policers can be twin-rate. T win-rate policing uses four parameters: z minimum bandwidth (in kbp s) z maximum bandwidth ( in kbps) z maximum burst size (in bytes) z minimum burst size (in bytes) With this combination, the algorithm used to determine [...]

  • Page 20

    Page 20 | AlliedW are Plus™ OS: Over view of QoS Counting policed pack ets T o see the count of policed packets: 1. T urn on the QoS counters enhanced mode by entering global configuration mode and using the command: awplus(config)#platform enhanc edmode qoscounters 2. Restart the switch 3. Return to privileged ex ec mode and use the command: awp[...]

  • Page 21

    Page 21 | AlliedW are Plus™ OS: Over view of QoS Counting pack ets for aggr egate policers If a pack et is processed b y an aggregate policer , it is counted in the output for e ver y por t that the aggregate policer a ppl ies to , not just for the port that received the pack et. The following figure shows output for the example from "Applyi[...]

  • Page 22

    Page 22 | AlliedW are Plus™ OS: Over view of QoS Remarking Remarking happens after the traffic has been policed. It sets the pack et’ s QoS mark ers depending on how w ell the flow conforms to its bandwidth limits. Remarking is performed by looking up the polic ed-dscp map and assigning values to the four mark ers (802. 1 p , DSCP , egress queu[...]

  • Page 23

    Page 23 | AlliedW are Plus™ OS: Over view of QoS Queue shaping—queue sets, RED , and tail-drop A queue set defines ho w the switch determines what traffic to dr op when a por t’ s queues become congested. The queue set applies to one or more of the port’ s queues, and specifies the queue size thr esholds at which the port star ts to drop tr[...]

  • Page 24

    Page 24 | AlliedW are Plus™ OS: Over view of QoS Note that by default ports only use the maxi mum thre shold, because they ar e in tail-drop mode . The other settings are random-detect mode settings. Having defaults means that y ou can change to random-detect mode without ha ving to configure a queue set (see "Applying RED cur ves to ports&q[...]

  • Page 25

    Page 25 | AlliedW are Plus™ OS: Over view of QoS These fundamental cur ves ar e collected into RED cur ve gr oups. A group is a collection of three cur ves, one for each of the thr ee possible bandwidth classes, as sho wn in the following figure. Additionall y , one other parameter is defined on each RED cur ve gr oup . This parameter is the aver[...]

  • Page 26

    Page 26 | AlliedW are Plus™ OS: Over view of QoS Specifying which queues to act on T o specify which queues to configure, use the optional queues parameter : awplus(config)#mls qos queue-s et <1-4> queues ... Specify the desire d queues as a space-separated list. For example: awplus(config)#mls qos queue-s et <1-4> queues 1 3 4 ... T [...]

  • Page 27

    Page 27 | AlliedW are Plus™ OS: Over view of QoS T o specify the av eraging factor , use the command: awplus(config)#mls qos queue-s et <1-4> [queues < list >] averaging-factor <0-15> T ail-drop mode By default, por ts use tail-drop mode and the default queue-set for th at port type (see "Default settings" on page 23 )[...]

  • Page 28

    Page 28 | AlliedW are Plus™ OS: Over view of QoS Strict priority scheduling Then, to set queues to use strict priority scheduling, use th e command: priority-queue < queue-list > Specify the queues as a space-separated list. For e xample , to put queues 3, 5, and 6 into the strict-priority gr oup of queues, use the command: awplus(config-if[...]

  • Page 29

    Page 29 | AlliedW are Plus™ OS: Over view of QoS The first of these numbers is th e percentage limit for queue 0, the second number is the limit for queue 1 , and so on. For example, to give queue 0 less of the buffer space and queues 3 and 4 more, you could use the command: wrr-queue queue-limit 6 12 12 17 17 12 12 12 Y ou can use this command t[...]

  • Page 30

    Page 30 | AlliedW are Plus™ OS: Over view of QoS P olicing Examples P olicing is the process of counting the n umber of pack ets that the switch pr ocesses and determining their lev el of conformance with th eir bandwidth limits. The AlliedW ar e Plus OS enables y ou to police ports and differ ent types of traffic separately (with “ordinary” [...]

  • Page 31

    Page 31 | AlliedW are Plus™ OS: Over view of QoS Use the following commands to configur e this policing scenario: mls qos enable class-map cm1 match access-group 3000 class-map cm2 match access-group 3001 policy-map pm1 class cm1 police twin-rate 1000 200 50 00 1000 exceed-action drop class cm2 police single-rate 3000 200 4000 exceed-action drop [...]

  • Page 32

    Page 32 | AlliedW are Plus™ OS: Over view of QoS 2: P olicing one traffic type on combined por ts In this scenario , one ty pe of traffic is collectivel y policed on sev eral por ts. The policer counts all the pack ets that match the type ’ s class map on an y of the ports. This scenario uses an aggregate policer . Use this type of scenario whe[...]

  • Page 33

    Page 33 | AlliedW are Plus™ OS: Over view of QoS 3: P olicing one traffic type on separate por ts, and another traffic type on the same por ts combined In this scenario , one type o f traffic is collectiv el y policed on sev eral por ts, while another type of traffic is individually policed on those por ts. For the first traffic type , the police[...]

  • Page 34

    Page 34 | AlliedW are Plus™ OS: Over view of QoS Use the following commands to configur e this policing scenario: mls qos enable mls qos aggregate-police aggr1 twin-rate 1000 200 5000 1000 exceed-action drop class-map cm1 match ip-dscp 35 class-map cm2 match access-group 3000 policy-map pm1 class cm1 police aggregate aggr1 class cm2 police single[...]

  • Page 35

    Page 35 | AlliedW are Plus™ OS: Over view of QoS 4: P olicing combined traffic types on separate por ts In this scenario , two types of traffic ar e collectiv el y policed on a per -port ba sis. The policing is done on se veral diff erent ports. On each po rt, the policer counts all packets that match either type’ s class map . This scenario us[...]

  • Page 36

    Page 36 | AlliedW are Plus™ OS: Over view of QoS Use the following commands to configur e this policing scenario: mls qos enable mls qos aggregate-police pol1 twin-rate 1000 4000 256000 1000000 exceed-action drop mls qos aggregate-police pol2 single-rate 3000 750000 1000000 exceed-action drop class-map cm1 match access-group 3008 class-map cm2 ma[...]

  • Page 37

    Page 37 | AlliedW are Plus™ OS: Over view of QoS 5: P olicing combined traffic types on combined por ts In this scenario , two types of traffic are collectivel y policed on multiple ports collectively . The policer counts all the pack ets that match ei ther type’ s class map on any of the ports. This scenario uses an aggregate policer . For exa[...]

  • Page 38

    Page 38 | AlliedW are Plus™ OS: Over view of QoS Use the following commands to configur e this policing scenario: mls qos enable mls qos aggregate-police pol1 twin-rate 1000 4000 256000 1000000 exceed-action drop class-map cm1 match vlan 10 class-map cm2 match vlan 20 policy-map pm1 class cm1 police aggregate pol1 class cm2 police aggregate pol1 [...]

  • Page 39

    Page 39 | AlliedW are Plus™ OS: Over view of QoS Mapping the queues in the s w itching instances to queues in the fabric By default, the mapping of the egr ess queues of the switching instances to the queues in the fabric is: T o alter this mapping, enter global configuration mode and use the command: awplus(config)#mls qos map inp ut-queue q0 q1[...]

  • Page 40

    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 [...]