English dropdown-ico

Allied Telesis AT 9924SP AT-9924SP-30 AT-9924SP-30 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
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

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 AT 9924SP AT-9924SP-30 AT-9924SP-30, 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 AT 9924SP AT-9924SP-30 AT-9924SP-30 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 AT 9924SP AT-9924SP-30 AT-9924SP-30. 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 AT 9924SP AT-9924SP-30 AT-9924SP-30 should contain:
- informations concerning technical data of Allied Telesis AT 9924SP AT-9924SP-30 AT-9924SP-30
- name of the manufacturer and a year of construction of the Allied Telesis AT 9924SP AT-9924SP-30 AT-9924SP-30 item
- rules of operation, control and maintenance of the Allied Telesis AT 9924SP AT-9924SP-30 AT-9924SP-30 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 AT 9924SP AT-9924SP-30 AT-9924SP-30 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 AT 9924SP AT-9924SP-30 AT-9924SP-30, 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 AT 9924SP AT-9924SP-30 AT-9924SP-30.

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 AT 9924SP AT-9924SP-30 AT-9924SP-30 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-16092-00 REV D www .alliedtelesis.co m AlliedW ar e TM OS How T o | Intr oduction Putting a ring of Ethernet switches at the cor e of a network is a simple wa y to increase the network’ s resilience—such a netw ork is no longer susceptible to a single point of failure. How ev er , the ri ng must be pr otected fr om La yer 2 loops. T r adit[...]

  • Page 2

    Page 2 | AlliedW are™ OS Ho w T o Note: EPSR Which products and softwar e versions does it apply to? • "Example 3: EPSR and RSTP" on page 17 • "Example 4: EPSR with Nested VLANs" on page 20 • "Example 5: EPSR with manage ment stacking" on page 23 • "Example 6: EPSR with an iMAP" on page 26 Next, it [...]

  • Page 3

    Page 3 | AlliedW are™ OS Ho w T o Note: EPSR Ho w EPSR W orks Ho w EPSR W orks EPSR operates on ph ysical rings of switches (note, not on meshed netw orks). When all nodes and links in the ring are up , EPSR pr ev ents a loop by blocking data transmission acr oss one por t. When a node or link fails, EPSR detects the failure ra pidly and responds[...]

  • Page 4

    Page 4 | AlliedW are™ OS Ho w T o Note: EPSR Ho w EPSR W orks Establishing a Ring Once y ou ha ve configur ed EPSR on the s witches, the f ollowing steps complete th e EPSR ring: 1. The master node creates an EPSR Health message and sends it out the primary por t. This incr ements the master node’ s T ransmit: Health counter in the sho w epsr c[...]

  • Page 5

    Page 5 | AlliedW are™ OS Ho w T o Note: EPSR Ho w EPSR W orks Detecting a Fault EPSR uses a fault detection sc heme that alerts the ring when a break occurs, instea d of using a spanning tree- lik e calculation to determin e the best path. The ring then automatically heals itself by sending traffic over a protected r ev erse path. EPSR uses the f[...]

  • Page 6

    Page 6 | AlliedW are™ OS Ho w T o Note: EPSR Ho w EPSR W orks new configuration, the nodes (master and transi t) r e-learn their la yer 2 addr esses. During this period, the master node con tinues to se nd Health messages ov er the control VLAN. This situation continues until the faulty link or node is r epaired. For a mu ltidomain ring, this pro[...]

  • Page 7

    Page 7 | AlliedW are™ OS Ho w T o Note: EPSR Ho w EPSR W orks Restoring Normal Operation Master Node Once the fault has been fixed, the master node’ s Health messages trav erse the whole ring and arriv e at the master node’ s secondar y por t . The master node then restor es normal conditions by: 1. declaring the ring to be in a state of Comp[...]

  • Page 8

    Page 8 | AlliedW are™ OS Ho w T o Note: EPSR Ho w T o Configure EPSR Ho w T o Configur e EPSR This section first outlines, step-by-step , how to configur e EPSR. Then it discusses changing the settings for the contr ol VLAN , if yo u need to do this after initial configuration. Configuring EPSR EPSR does not in itself limit the number of nodes th[...]

  • Page 9

    Page 9 | AlliedW are™ OS Ho w T o Note: EPSR Ho w T o Configure EPSR If you lea ve all the ring port s in the default VLAN (vlan 1 ), they will cr eate a loop, unless vlan 1 is par t of the EPSR domain. T o a void l oops, you need to do one of the following: • mak e vlan 1 a data VLAN, or • remo ve the ring por ts fr om vlan 1 , or • remo v[...]

  • Page 10

    Page 10 | AlliedW are™ OS Ho w T o Note: EPSR Ho w T o Configure EPSR Modifying the Contr ol VLAN Y ou cannot modify the control VLAN while EPSR is enabl ed. If you try to remov e or add ports to the control VLAN, the switch generates an err or message as follows: Disable the EPSR domain and then mak e the requ ir ed changes. Note that disabling [...]

  • Page 11

    Page 11 | AlliedW are™ OS Ho w T o Note: EPSR Example 1 : A Basic Ring Example 1 : A Basic Ring This example builds a simple 3-switch ring wi th one data VLAN, as shown in the following diagram. Control pack ets ar e transm itted around the ring on vlan 1 000 and data packets on vlan2. Configur e the Master Node (A) create vlan=vlan1000 vid=1000 [...]

  • Page 12

    Page 12 | AlliedW are™ OS Ho w T o Note: EPSR Example 1 : A Basic Ring delete vlan=1 port=1-2 This step creates the domain, spec ifying that this switch is the master node. It also specifies which VLAN is the contr ol VLAN and which por t is the primar y por t. create epsr=test mode=master controlvlan=vlan1000 primaryport=1 add epsr=test datavlan[...]

  • Page 13

    Page 13 | AlliedW are™ OS Ho w T o Note: EPSR Example 1 : A Basic Ring This step creates the domain, spec ifying that this switch is the transit node. It also specifies which VLAN is the contr ol VLAN. create epsr=test mode=transit controlvlan=vlan1000 add epsr=test datavlan=vlan2 enable epsr=test 6. Create the EPSR domain 7. Add the data VLAN to[...]

  • Page 14

    Page 14 | AlliedW are™ OS Ho w T o Note: EPSR Example 2: A Double Ring Example 2: A Double Ring This example adds to the previous ring by making two domains, as shown in the following diagram. The master node for domain 1 is the same as in the pre v ious example (except that the domain has been r enamed). create vlan=vlan1000 vid=1000 add vlan=10[...]

  • Page 15

    Page 15 | AlliedW are™ OS Ho w T o Note: EPSR Example 2: A Double Ring This transit node is the same as in the pr ev ious example (except that the domain has been re n am e d ) . create vlan=vlan1000 vid=1000 add vlan=1000 port=1-2 frame=tagged create vlan=vlan2 vid=2 add vlan=2 port=1-2 frame=tagged delete vlan=1 port=1-2 create epsr=domain1 mod[...]

  • Page 16

    Page 16 | AlliedW are™ OS Ho w T o Note: EPSR Example 2: A Double Ring Configur e EPSR: create epsr=domain2 mode=transit controlvlan=vlan40 add epsr=domain2 datavlan=vlan50 enable epsr=domain2 T wo separate EPSR domains are configur ed on this switch. Configur e the control VL AN for domain 1 : create vlan=vlan1000 vid=1000 add vlan=1000 port=1-2[...]

  • Page 17

    Page 17 | AlliedW are™ OS Ho w T o Note: EPSR Example 3: EPSR and RSTP Example 3: EPSR and RSTP This example uses EPSR to pr otect one ring and RSTP to protect another o verla pping ring. The master node is the same as in the previous example. create vlan=vlan1000 vid=1000 add vlan=1000 port=1-2 frame=tagged create vlan=vlan2 vid=2 add vlan=2 por[...]

  • Page 18

    Page 18 | AlliedW are™ OS Ho w T o Note: EPSR Example 3: EPSR and RSTP This transit node (B) is the sa me as in the pr evious example . create vlan=vlan1000 vid=1000 add vlan=1000 port=1-2 frame=tagged create vlan=vlan2 vid=2 add vlan=2 port=1-2 frame=tagged delete vlan=1 port=1-2 create epsr=domain1 mode=transit controlvlan=vlan1000 add epsr=dom[...]

  • Page 19

    Page 19 | AlliedW are™ OS Ho w T o Note: EPSR Example 3: EPSR and RSTP Configure the contr ol VLAN for EPSR: create vlan=vlan1000 vid=1000 add vlan=1000 port=1-2 frame=tagged Configure the data VLAN f or EPSR: create vlan=vlan2 vid=2 add vlan=2 port=1-2 frame=tagged Remov e the ring por ts from the default VLAN: delete vlan=1 port=1-2 Configur e [...]

  • Page 20

    Page 20 | AlliedW are™ OS Ho w T o Note: EPSR Example 4: EPSR with Nested VLANs Example 4: EPSR with Nested VLANs In this example: • client switches A and C ar e in the same end-user VLAN (vlan20) • client switches B and D are in the same end-user VLAN (vlan200 ) • traffic for vlan20 and vlan200 is nested insi de vlan50 f or transmis sion a[...]

  • Page 21

    Page 21 | AlliedW are™ OS Ho w T o Note: EPSR Example 4: EPSR with Nested VLANs Configure the EPSR contr ol VLAN: create vlan=vlan100 vid=100 add vlan=100 port=1-2 frame=tagged Configure vlan50. This VLAN acts as both th e neste d VLAN and the EPSR data VLAN. The following commands cr eate vlan50 and configure it as a nested VLAN: create vlan=vla[...]

  • Page 22

    Page 22 | AlliedW are™ OS Ho w T o Note: EPSR Example 4: EPSR with Nested VLANs create vlan=vlan20 vid=20 add vlan=20 port=20 frame=tagged enable ip add ip interface=vlan20 ip=192.168.20.10 create vlan=vlan200 vid=200 add vlan=200 port=10 frame=tagged enable ip add ip interface=vlan200 ip=192.168.200.1 create vlan=vlan20 vid=20 add vlan=20 port=2[...]

  • Page 23

    Page 23 | AlliedW are™ OS Ho w T o Note: EPSR Example 5: EPSR with manage ment stacking Example 5: EPSR with manag ement stacking In this example: • three switches are stack ed together , so you can manage all three switches by entering commands into the CLI of an y one of them • the three s witches are also configur ed as an EPSR domain • [...]

  • Page 24

    Page 24 | AlliedW are™ OS Ho w T o Note: EPSR Example 5: EPSR with manage ment stacking The following commands mu st be entered in to the CLI of this particular switch. First, give the switch a host ID n umb er so that the stack can identify it: set system hostid=1 serialnumber=12345678 set system name=host1 Create the stacking VLAN and add the r[...]

  • Page 25

    Page 25 | AlliedW are™ OS Ho w T o Note: EPSR Example 5: EPSR with manage ment stacking The stack now exists, so you can configure all thre e switches from the CLI of the master node (or any other of the s witches). How ev er , the por ts and IP addr esses ar e differ ent for each switch, so y ou need to make most of the commands host-directed. C[...]

  • Page 26

    Page 26 | AlliedW are™ OS Ho w T o Note: EPSR Example 6: EPSR with an iMAP Example 6: EPSR with an iMAP This example is the same as "Example 1 : A Basic Ring" on pag e 11 except that one of the three s witches is an iMAP . W e used an A T -TN7 1 00 iMAP running 6. 1 . 1 0. The ring ports on the iMAP are 5.0 and 5. 1 . The example first [...]

  • Page 27

    Page 27 | AlliedW are™ OS Ho w T o Note: EPSR Example 6: EPSR with an iMAP Checking the Master Node Configuration T o see a summar y , use the command: show epsr The following diagram sho ws the expected output. T o see details, use the command: show epsr=test The following diagram sho ws the expected output. --- EPSR Domain Information ---------[...]

  • Page 28

    Page 28 | AlliedW are™ OS Ho w T o Note: EPSR Example 6: EPSR with an iMAP Configur e the A T -TN7 1 00 iMAP as a T ransit Node The following diagram shows a partial script fo r the iMAP , with the commands for configuring it as a transit node. Checking the T ransi t Node Configuration T o see a summar y , use the command: show epsr The following[...]

  • Page 29

    Page 29 | AlliedW are™ OS Ho w T o Note: EPSR Classifiers and Ha rdwa re F ilt er s T o see details, use the command: show epsr=test The following diagram sho ws the expected output. Classifiers and Hard war e Filters On A T -8948, A T -9900, A T -9900s, and x900 series switches, the s witching hardwar e has a limit of 1 6 bytes to use for matchi[...]

  • Page 30

    Page 30 | AlliedW are™ OS Ho w T o Note: EPSR P or ts and Reco ve r y Times P or ts and Reco v er y Times In practice, recove r y time in an EP SR ring is generally b etween 50 and 1 00 ms. How eve r , it depends on the por t type , because this determines how long it tak es for the port to report that it is down and send a Link-Do wn message . T[...]

  • Page 31

    Page 31 | AlliedW are™ OS Ho w T o Note: EPSR IGMP Snooping and Reco very Times IGMP Snooping and Reco ver y Times Since Software V ersion 28 1 -03, IGMP snooping includes quer y sol icitation , a new fe ature that minimises loss of multicast data after a topology change. When IGMP snooping is enable d on a VLAN, and EPSR changes the underlying l[...]

  • Page 32

    Page 32 | AlliedW are™ OS Ho w T o Note: EPSR EPSR State and Setting s EPSR State and Settings T o display the EPSR state , the attached VLANs, the ring ports, and the timer values, use the command: show epsr Master Node in a Complete Ring The following diagram shows the output for a mast er node in a ring that is in a state of Complete. As well [...]

  • Page 33

    Page 33 | AlliedW are™ OS Ho w T o Note: EPSR EPSR State and Setting s Master Node in a Failed Ring In contrast, the following diagram sho ws the output for a master node in a ring that is in a Failed state . Both ring por ts are now f orwarding. EPSR Information ---------------------------------- -------------------------------------- Name .....[...]

  • Page 34

    Page 34 | AlliedW are™ OS Ho w T o Note: EPSR SNMP T raps SNMP T raps Y ou can use SNMP traps to notify you when ev ents occur in the EPSR ring. Download the latest version of the Allied T elesis Enterprise MIB from www .alliedtelesis.co.nz/sup port/updates/patches.html . The EPSR Gr oup is contained in the sub-file called atr -epsr .mib. The EPS[...]

  • Page 35

    Page 35 | AlliedW are™ OS Ho w T o Note: EPSR Counters Counters The EPSR counters r ecord th e n umber of EPSR messages that the CPU receiv ed and transmitted. T o display th e counters, use th e command: show epsr=domain1 count Master node in a Complete ring The following diagram sho ws the counters for a master node in a ring that has ne ver ha[...]

  • Page 36

    Page 36 | AlliedW are™ OS Ho w T o Note: EPSR Debugging Debugging This section walks you thr ough the EPSR debuggi ng output as links go down and come back up again. The debugging output comes from the ring in "Example 1 : A Basic Ring" on page 11 . The output shows what happened when we took down tw o separate links in turn: • first,[...]

  • Page 37

    Page 37 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The master node contin ues sending Health me ssages, and incr ements the Hello Sequence number with each message. If all nodes and links in the ring are intact, these He alth messages are the onl y debugging output you see. The link betw een the master node’ s primar y port and the neighbo[...]

  • Page 38

    Page 38 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The master node receiv es a Link-Down message on its secondar y po rt (por t 2) from transit node B, which is at the other end of the br ok en link. In the System field, this output shows the MA C addr ess of the sour ce of the message—the transit node in this case. The master switch respo[...]

  • Page 39

    Page 39 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The Hello timer expir es, which w ould normally trigger the mas ter node to send a Health message out the primar y port. Howev er , the link between the primary por t and the neighbouring transit node is down , so the ma ster node does no t se nd the Health message. The primar y por t comes [...]

  • Page 40

    Page 40 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The master node receiv es the Health message on its secondar y port (por t 2). This tells it that all links on the ring are up again. The master node blocks its secondary por t for the data VLAN, unblock s its primar y por t, transmits a Ring-Up -Flush-FDB message , flushes its FDB, sends a [...]

  • Page 41

    Page 41 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The master node continues transmitting and rece iving Health messages for as long as the ring sta ys in a state of Complete . 12. The master node transmits and receiv es Health messages Manager x900-48-A> epsrHelloTimeout: EPSR test Hello Timer expired EPSR Port1 Tx: 00e02b00 00040000 cd2[...]

  • Page 42

    Page 42 | AlliedW are™ OS Ho w T o Note: EPSR Debugging T ransit Node (Node B) Debug Output The following debugging shows the same e vents as the pr evious section, but on the transit node instead of the master node. It starts with the ring establis hed and in a state of Complete. The transit node receiv es Health messages on port 1 , because tha[...]

  • Page 43

    Page 43 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The transit node detects that por t 1 (between the transit node and the master n ode) has gone do wn. The transit node flus hes its forwar ding database, blocks por t 1 for th e dat a VLAN (to pre vent a loop fr om forming when th e master node comes back up), sends a Link- Down message towa[...]

  • Page 44

    Page 44 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The transit node detects that port 1 has come back up. It sends a trap and changes the EPSR state to Pre-f orwarding. Note that it lea ves port 1 block ed for vlan2, to mak e sure ther e are no loops. Now that the master node’ s primar y por t is up again, it sends a Health message . Now t[...]

  • Page 45

    Page 45 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The Health message from the pre vious step re aches the master node and shows it that all links in the ring are no w up . The master node sends a Ring-Up-Flush-FDB mes sage . When it r eceives the message, the tr ansit node unblocks port 1 for vlan2, flushes its FDB, sends a trap , and chang[...]

  • Page 46

    Page 46 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The transit node continues r eceiving Health messages for as long as the ring sta ys in a state of Complete. This is the pack et shown in step 12 on page 41 of the master node debug output. 7. The transit node receiv es Health messages Manager 9924-B> EPSR Port1 Rx: 00e02b00 00040000 cd28[...]

  • Page 47

    Page 47 | AlliedW are™ OS Ho w T o Note: EPSR Debugging Link Do wn Betw een T w o T ransit Nodes This section sho ws the debugging output when the link betw een transit node B and transit node C goes do wn and comes back up again. It s hows the debugging output for the comple te failure and r ecovery cycle: • on the master node, and then • on[...]

  • Page 48

    Page 48 | AlliedW are™ OS Ho w T o Note: EPSR Debugging When the link goes down, the master node tr ansmits a Health message but does not receiv e it on its secondar y port. The master node receiv es a Link-Down message , which tells it that a link in the ring is brok en. This m essage came from the transi t node on one side of the brok en link. [...]

  • Page 49

    Page 49 | AlliedW are™ OS Ho w T o Note: EPSR Debugging In re sponse to the Link-Do wn message, the master node transmits a Ring-Down-Flush-FDB message out both its primar y and second ar y por ts. The message has to go out both ports to mak e sure it r eaches the nodes on both side s of the brok en link. The master node also unblocks its second [...]

  • Page 50

    Page 50 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The master node continues se nding Health mess ages out its primar y por t. It does not r eceive any of these at the secondary por t, whic h tells it tha t the link is still down. The master node transmits a Health message an d receives it at the secondary por t. This indicates that the link[...]

  • Page 51

    Page 51 | AlliedW are™ OS Ho w T o Note: EPSR Debugging Now that the ring is back up , the master node blocks its secondar y port for the data VLAN, transmits a Ring-Up -Flush-FDB message , flushes its FDB, sends a trap , and changes the EPSR state to Complete . The master node r eceiv es the Ring-Up-Flush-FDB message back on its s econdar y por [...]

  • Page 52

    Page 52 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The master node continues transmitting and receiv ing Health messages for as long as the ring sta ys in a state of Complete . 10. The master node transmits and receiv es Health messages Manager x900-48-A> epsrHelloTimeout: EPSR test Hello Timer expired EPSR Port1 Tx: 00e02b00 00040000 cd2[...]

  • Page 53

    Page 53 | AlliedW are™ OS Ho w T o Note: EPSR Debugging T ransit Node (Node B) Debug Output The following debugging shows the same e vents as the pr evious sectio n, but on the transit node instead of the master node. It starts with the ring establis hed and in a state of Complete. The transit node receiv es Health messages on port 1 , because th[...]

  • Page 54

    Page 54 | AlliedW are™ OS Ho w T o Note: EPSR Debugging In the meanwhile, the master node has received a Link-Down message fr om the switch at the other end of the br oken link (in step 3 on page 48 ). Therefor e, the master node realises that the ring is brok en and acts accordingly . As pa rt of the recov er y process, the master node sends a R[...]

  • Page 55

    Page 55 | AlliedW are™ OS Ho w T o Note: EPSR Debugging The transit node receiv es Heal th messages fr om the master node . These ha ve a state of Failed, which shows that the ring is still brok en. This is the pack et shown in step 6 on page 50 of the master node debug output. The transit node detects that the br ok en link has come back up . It[...]

  • Page 56

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