show voice port - Tecnológico de Costa Rica
show voice port - Tecnológico de Costa Rica show voice port - Tecnológico de Costa Rica
11 - 6 Aironet 340 Series Bridge Setting the Default (Source) Source address filtering is “Off” by default. This saves processing power since the unit has to look up the source address of each incoming packet to see if a filter is to be applied. Before any individual source filters can be made active, one of the other values for the default must be chosen. You may set the action to off, forward or discard. Setting Specific Node Address Filters (Add/Remove) Use the add option to add filters for specific addresses to the filter table. You will be prompted for the infrastructure address or IP address of the node to which the filter applies. You are then asked whether this is a source address, radio destination address or ethernet destination address filter. Finally you are be asked for the filter action to be applied to this address which may be off (for remove the filter), forward or discard. To remove one or all specific node filters use the remove option. You may enter either the keyword “all”, a single nodes infrastructure address, or a single node’s IP address. Once removed, the filter action for the removed addresses will revert to the default value. Displaying The Node Address Filters (Display) Use the display option to view the table of controlled addresses. The filters are stored in the association table so that they may be accessed quickly. The display of the filters follows the format of the normal association display. At the end of each line the filter action for each address will be displayed. This same display may also be produced using the “association display” command with either the “all” or “multicast-filters” information. See Chapter 10 “Setting Up the Association Table”. NODE FILTERS Address Device Type Parent Name Src ------------- --------- ---- ------------ ------------------ --- N000102030405 Unkwn Fwd Enter space to redisplay, q[uit]:
Displaying the IP to Network Address Table (IPdisplay) Using Filters 11 - 7 When a node address filter is entered by IP address, the Aironet 340 Series Bridge first determines the infrastructure address associated with this IP address. The actual filtering is done based on the infrastructure address. IP ADDRESS FILTERS IP Address MAC Address Src --------------- ------------ --- 149.023.165.186 004096206892 Fwd Enter space to redisplay, q[uit]: Filtering Protocols (Protocols) Protocol filtering bases the filtering decision on the type of protocol used to encapsulate the data in the packet. This type of filtering can have the most value in almost all situations and is the preferred method of filtering. With this type of filtering you may set the Aironet 340 Series Bridge to only forward those protocols, over the radio, that are being used by the remote radio nodes. Selecting protocols is easier than setting up filters based on addresses. The Aironet 340 Series Bridge may be set up to monitor and record the list of protocols currently being forwarded over the radio. It will record the protocols found, how may packets were encountered and whether the packet came from the LAN or the radio. To set up the protocol filters, start the monitor and let it run for a while under normal use. Add filters by selecting the protocols from the monitor list. There is a default action for those protocols not in the list of explicitly filtered protocols. If you know exactly which protocols are going to be used by the radio nodes, set the default action to discard and add filters to forward only those protocols that will be used. If you are not sure of all the protocols that will be used but you know that there are certain protocols you will not use, you would set the default to forward and add filters to discard only those protocols you will not use. For filtering purposes the bridge assumes that the data portion of the packets is in one of two forms:
- 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 and 414: Chapter 10 - Setting Up the Associa
- Page 415 and 416: Using the Association Menu Setting
- 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: Filtering Node Addresses (Node) Usi
- 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
- Page 465 and 466: Appendix A - Aironet 340 Series Bri
- Page 467 and 468: Console Port Pin-Out The Console Po
- Page 469 and 470: B-2 Aironet 340 Series Bridge Conti
- Page 471 and 472: B-4 Aironet 340 Series Bridge Broad
- Page 473 and 474: B-6 Aironet 340 Series Bridge Desti
- Page 475 and 476: C-2 Aironet 340 Series Bridge The I
Displaying the IP to Network Address Table (IPdisplay)<br />
Using Filters 11 - 7<br />
When a no<strong>de</strong> address filter is entered by IP address, the Aironet 340<br />
Series Bridge first <strong>de</strong>termines the infrastructure address associated with<br />
this IP address. The actual filtering is done based on the infrastructure<br />
address.<br />
IP ADDRESS FILTERS<br />
IP Address MAC Address Src<br />
--------------- ------------ ---<br />
149.023.165.186 004096206892 Fwd<br />
Enter space to redisplay, q[uit]:<br />
Filtering Protocols (Protocols)<br />
Protocol filtering bases the filtering <strong>de</strong>cision on the type of protocol<br />
used to encapsulate the data in the packet. This type of filtering can have<br />
the most value in almost all situations and is the preferred method of filtering.<br />
With this type of filtering you may set the Aironet 340 Series<br />
Bridge to only forward those protocols, over the radio, that are being<br />
used by the remote radio no<strong>de</strong>s. Selecting protocols is easier than setting<br />
up filters based on addresses.<br />
The Aironet 340 Series Bridge may be set up to monitor and record the<br />
list of protocols currently being forwar<strong>de</strong>d over the radio. It will record<br />
the protocols found, how may packets were encountered and whether the<br />
packet came from the LAN or the radio.<br />
To set up the protocol filters, start the monitor and let it run for a while<br />
un<strong>de</strong>r normal use. Add filters by selecting the protocols from the<br />
monitor list.<br />
There is a <strong>de</strong>fault action for those protocols not in the list of explicitly<br />
filtered protocols. If you know exactly which protocols are going to be<br />
used by the radio no<strong>de</strong>s, set the <strong>de</strong>fault action to discard and add filters<br />
to forward only those protocols that will be used. If you are not sure of<br />
all the protocols that will be used but you know that there are certain<br />
protocols you will not use, you would set the <strong>de</strong>fault to forward and add<br />
filters to discard only those protocols you will not use.<br />
For filtering purposes the bridge assumes that the data <strong>port</strong>ion of the<br />
packets is in one of two forms:
Change language