show voice port - Tecnológico de Costa Rica
show voice port - Tecnológico de Costa Rica show voice port - Tecnológico de Costa Rica
10 - 2 Aironet 340 Series Bridge Overview Client nodes and repeater bridges request to be associated with a parent bridge so the parent will forward data frames. This exchange of radio packets passes back and forth information such as a node’s address, device, association type, and ASCII name. This information is entered into the bridge’s association table along with the address of the parent bridge. Each bridge maintains entries in its table for all nodes associated to it and all nodes associated to any repeater serving it. There may be up to 2048 entries in the table. A bridge will accept an association from any node that requests it. The operator may set up entries in the association table to control which nodes are allowed to associate. Using the information in the association table, the bridge can perform a variety of traffic-control functions in moving packets to their proper destination on the infrastructure. When packets are received from the Ethernet or radio network, the bridge will look in its table for the packet’s destination address and do one of the following: n If the entry shows the radio node is associated to this unit, the packet can be forwarded directly. n If the entry indicates that the entry is associated to a repeater serving this unit, the packet is forwarded to the repeater. n If the address is not found, a root unit will forward the packet to the wired LAN, while a repeater will forward the packet to its own parent bridge.
Using the Association Menu Setting Up the Association Table 10 - 3 The Association Menu contains options that allow you to view the table entries, add entries, and control the routing of packets on your radio network. To access this menu, select Association from the Main Menu. Association Menu Option Value Description 1 - Display - Display the table 2 - Summary - Display the table summary 3 - Maximum [ 1024 ] - Maximum allowable child nodes 4 - Autoassoc [ on ] - Allow automatic table additions 5 - Add - Control node association 6 - Remove - Remove association control 7 - Staletime [ 350 ] - Backbone LAN node stale out time 8 - Niddisp [ numeric ] - Node Ids display mode Enter an option number or name, "=" main menu, previous menu Displaying the Association Table (Display) Use the display option to view the association table entries. Select “display” to enter the type of entries to be displayed. n All: Displays all entries in the table. n Connected: Displays only nodes that are actively connected to the Aironet 340 Series Bridge. n Heirachy: A special shortened display which shows the association tree with children indented from their parents. n Static: Displays only nodes for which a static entry has been made to control the nodes’ association. n Multicast-filters: Displays only those entries for multicast addresses for which filters have been added. See Chapter 11 “Using Filters”. n Node-filters: Displays only those entries for node address for which filters have been added. See Chapter 11 “Using Filters”.
- Page 363 and 364: Viewing Errors (Errors) Configuring
- Page 365 and 366: Configuring the Radio Network 4 - 1
- Page 367 and 368: Roaming Notification Mode (Roaming)
- Page 369 and 370: Chapter 5 - Configuring the Etherne
- Page 371 and 372: Configuring the Ethernet Port 5 - 3
- Page 373 and 374: 6 - 2 Aironet 340 Series Bridge Usi
- Page 375 and 376: 6 - 4 Aironet 340 Series Bridge 2.
- Page 377 and 378: Chapter 7 - Configuring Mobile IP C
- Page 379 and 380: Configuring Mobile IP 7 - 3 On a fo
- Page 381 and 382: Configuring Mobile IP 7 - 5 work. T
- Page 383 and 384: Chapter 8 - Using the Spanning Tree
- Page 385 and 386: Understanding Loops Using the Spann
- Page 387 and 388: Using the Spanning-Tree Protocol 8
- Page 389 and 390: Establishing Timeouts Node Address
- Page 391 and 392: Using the Configuration STP Menu (R
- Page 393 and 394: Using the Spanning-Tree Protocol 8
- Page 395 and 396: Using the Spanning-Tree Protocol 8
- Page 397 and 398: Setting the Local Port Priority (Pr
- Page 399 and 400: Viewing the Port State (State) Usin
- Page 401 and 402: Chapter 9 - Viewing Statistics CHAP
- Page 403 and 404: Throughput Statistics (Throughput)
- Page 405 and 406: Error Statistics Viewing Statistics
- Page 407 and 408: Displaying Overall Status (Status)
- Page 409 and 410: Viewing Statistics 9 - 9 2. Type th
- Page 411 and 412: Displaying Node Information (Node)
- Page 413: Chapter 10 - Setting Up the Associa
- Page 417 and 418: Setting Up the Association Table 10
- Page 419 and 420: Setting Up the Association Table 10
- Page 421 and 422: Chapter 11 - Using Filters CHAPTER
- Page 423 and 424: Using Filters 11 - 3 n Both: Packet
- Page 425 and 426: Filtering Node Addresses (Node) Usi
- Page 427 and 428: Displaying the IP to Network Addres
- Page 429 and 430: Setting the Default Action (Default
- Page 431 and 432: Í To Add a Filter Using the Monito
- Page 433 and 434: If you type llc: a. When you select
- Page 435 and 436: Using Filters 11 - 15 The contents
- Page 437 and 438: Chapter 12 - Setting Up Event Logs
- Page 439 and 440: Setting Up Event Logs 12 - 3 Node
- Page 441 and 442: Error Logs Severe Error Logs “Cat
- Page 443 and 444: Lost our association, new specified
- Page 445 and 446: Setting Up Event Logs 12 - 9 NOTE:
- Page 447 and 448: Setting Statistic Parameters (Stati
- Page 449 and 450: The following trap messages will be
- Page 451 and 452: Chapter 13 - Performing Diagnostics
- Page 453 and 454: Performing Diagnostics 13 - 3 are d
- Page 455 and 456: Physically Locating a Unit (Find) P
- Page 457 and 458: Performing Diagnostics 13 - 7 4. Th
- Page 459 and 460: Performing Diagnostics 13 - 9 5. Se
- Page 461 and 462: Performing Diagnostics 13 - 11 4. I
- Page 463 and 464: Performing Diagnostics 13 - 13 If t
10 - 2 Aironet 340 Series Bridge<br />
Overview<br />
Client no<strong>de</strong>s and repeater bridges request to be associated with a parent<br />
bridge so the parent will forward data frames. This exchange of radio<br />
packets passes back and forth information such as a no<strong>de</strong>’s address,<br />
<strong>de</strong>vice, association type, and ASCII name. This information is entered<br />
into the bridge’s association table along with the address of the parent<br />
bridge. Each bridge maintains entries in its table for all no<strong>de</strong>s associated<br />
to it and all no<strong>de</strong>s associated to any repeater serving it. There may be up<br />
to 2048 entries in the table.<br />
A bridge will accept an association from any no<strong>de</strong> that requests it.<br />
The operator may set up entries in the association table to control<br />
which no<strong>de</strong>s are allowed to associate.<br />
Using the information in the association table, the bridge can perform a<br />
variety of traffic-control functions in moving packets to their proper<br />
<strong>de</strong>stination on the infrastructure. When packets are received from the<br />
Ethernet or radio network, the bridge will look in its table for the<br />
packet’s <strong>de</strong>stination address and do one of the following:<br />
n If the entry <strong>show</strong>s the radio no<strong>de</strong> is associated to this unit, the<br />
packet can be forwar<strong>de</strong>d directly.<br />
n If the entry indicates that the entry is associated to a repeater<br />
serving this unit, the packet is forwar<strong>de</strong>d to the repeater.<br />
n If the address is not found, a root unit will forward the packet to the<br />
wired LAN, while a repeater will forward the packet to its own<br />
parent bridge.