show voice port - Tecnológico de Costa Rica
show voice port - Tecnológico de Costa Rica show voice port - Tecnológico de Costa Rica
12 - 2 Aironet 340 Series Bridge Overview Information Logs The Aironet 340 Series Bridge produces logs that record the occurrence of significant events occurring within your unit and on the infrastructure. The type of events that are recorded as logs are: n Information Logs: Records status changes that occur in the normal operation of the system. For example, when an end node associates to an Aironet 340 Series Bridge. n Error Logs: Records errors that occur occasionally, but are easily recovered from by the unit. For example, errors that occur during the reception and transmission of packets to and from the unit. n Severe Error Logs: Records errors which drastically affect the operation of the system. The system will continue to run, but action is required to return the unit to normal operating standards. BOOTP/DHCP set new IP address The BOOTP/DHCP server answered the request and assigned the unit an IP address different than the configured value. Node “node address” “device name” added A non-volatile entry was added to the association table. Node “node address” “device name” added locally “ASCII name” A new node associated with the local unit. Node “node address” “device name” restarted “ASCII name” A node that is currently associated to the local unit was reset. Node “node address” “device name” “ASCII name” removed, max radio retries A node was removed from the table because a response was not received from the node after attempts were made to transmit a packet to it. The node may have failed or moved to another cell.
Setting Up Event Logs 12 - 3 Node “node address” “device name” “ASCII name” removed, staled out A node was removed from the table because data was not received from the node within the stale-out period. Different devices have different stale-out times. PSP nodes have very short stale-out times (around 10 seconds). Non-PSP nodes have longer times (usually several minutes). Node “node address” “device name” “ASCII name” removed, NV removed A node was removed from the association table because the operator used the “association remove” command. Node “node address” “device name” “ASCII name” removed, deassoc notice from “address” The node was removed from the association table because another bridge reported that it now has the node associated locally. This log is produced whenever a node handoff occurs. RARP set new IP address A RARP server answered a request for an IP address with an address different from the one currently saved. The currently saved value is overwritten. Associated to router “node address” This log is produced when the unit, configured as a repeater, associates to its parent node. SNMP: “command text” A SNMP management node sent the unit a “set” variable request which was successfully executed. The “command text” is a similar menu command that has the same effect as the SNMP request. SNMP access failure from “community name” “IP address” (node address) A SNMP management node attempted to access the SNMP agent with an invalid community name or a name that it was not allowed to use.
- 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 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: Chapter 12 - Setting Up Event Logs
- 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
- Page 477 and 478: C-4 Aironet 340 Series Bridge The I
- Page 479 and 480: C-6 Aironet 340 Series Bridge The U
- Page 481 and 482: C-8 Aironet 340 Series Bridge The S
- Page 483 and 484: C-10 Aironet 340 Series Bridge MIBI
- Page 485 and 486: C-12 Aironet 340 Series Bridge The
- Page 487 and 488: C-14 Aironet 340 Series Bridge The
12 - 2 Aironet 340 Series Bridge<br />
Overview<br />
Information Logs<br />
The Aironet 340 Series Bridge produces logs that record the occurrence<br />
of significant events occurring within your unit and on the infrastructure.<br />
The type of events that are recor<strong>de</strong>d as logs are:<br />
n Information Logs: Records status changes that occur in the normal<br />
operation of the system. For example, when an end no<strong>de</strong> associates<br />
to an Aironet 340 Series Bridge.<br />
n Error Logs: Records errors that occur occasionally, but are easily<br />
recovered from by the unit. For example, errors that occur during<br />
the reception and transmission of packets to and from the unit.<br />
n Severe Error Logs: Records errors which drastically affect the<br />
operation of the system. The system will continue to run, but action<br />
is required to return the unit to normal operating standards.<br />
BOOTP/DHCP set new IP address<br />
The BOOTP/DHCP server answered the request and assigned the unit an<br />
IP address different than the configured value.<br />
No<strong>de</strong> “no<strong>de</strong> address” “<strong>de</strong>vice name” ad<strong>de</strong>d<br />
A non-volatile entry was ad<strong>de</strong>d to the association table.<br />
No<strong>de</strong> “no<strong>de</strong> address” “<strong>de</strong>vice name” ad<strong>de</strong>d locally “ASCII name”<br />
A new no<strong>de</strong> associated with the local unit.<br />
No<strong>de</strong> “no<strong>de</strong> address” “<strong>de</strong>vice name” restarted “ASCII name”<br />
A no<strong>de</strong> that is currently associated to the local unit was reset.<br />
No<strong>de</strong> “no<strong>de</strong> address” “<strong>de</strong>vice name” “ASCII name” removed, max<br />
radio retries<br />
A no<strong>de</strong> was removed from the table because a response was not received<br />
from the no<strong>de</strong> after attempts were ma<strong>de</strong> to transmit a packet to it. The<br />
no<strong>de</strong> may have failed or moved to another cell.
Change language