Table of Contents
Advertisement
Additional Features
8. To delete a single alert string from a port, leaving other configured alert strings intact:
•
Type: show ports alert port[#]
•
Select and copy the desired string to be deleted, using the Telnet client copy command.
•
Type: configure ports alert delete port[#] ["quoted string"]
(where the selected alert string is pasting into the command line.)
9. To clear all of the alert strings configured for a port, type:
configure ports alert clear port[#]
Note
Use the "find-alert" command to display a string or partial string by port. This command is generally helpful
to customers using multiple ports.
Testing Port Alert Strings
Port alert strings may be tested for a configured port if the connected device echoes received
characters, as is the case with CLI console ports.
1. Telnet to the connected device and type any port alert strings for that port, followed by a CR.
2. Even if the string results in an error, the connected device echoing the typed characters will
generate a port alert by the SC-ADT.
3. The SC-ADT will wait up to five seconds before generating a port alert for the current line if a
line terminating character (CR or LF) has not been seen. This allows capturing as much of the
current line as possible to be included in the SNMP trap.
4. If the connected device is a GDC CLI product, (SCIP, SCES, etc.), enter Supervisor or Admin
mode and use the batch comment character # followed by a space to type an arbitrary string.
Port Alert Limitations
Without Port Alerts, ADT can process about 150,000 characters per second across multiple ports.
With Port Alerts, string match comparisons require many CPU cycles, so that excessive use of Port
Alerts can have an adverse impact on some applications. The following guidelines should help
avoid problems in your Terminal Server or Transport applications that use Pert Alerts.
Terminal Server Applications
Terminal Server applications may be considered "lightly loaded" applications where users Telnet
or modem into the SC-ADT to connect to a port, and the connected device normally responds only
when the user types something or occasionally prints out information such as interface state
changes. The connected baud rate is typically 19200 bps or less.
•
In most Terminal Server applictions, using port alerts should not cause problems even with
multiple users connected at once.
•
If all ports are configured for port alerts with all five strings configured per port and all ports
are in use simultaneously, there may be a throughput problem. It depends on how much data
the connected devices actually generate.
Transport Applications
Transport applications should be considered "heavily loaded" applications, where multiple ports are
configured to transport all received data via TCP to remote ADTs for transmit out on a port. In such
applications, the data stream operates continuously at or near line rates, and port baud rate is
typically greater than 19200 bps.
•
In Transport applications, port alerts should only be used sparingly.
•
Try to use the shortest strings possible and as few strings as necessary.
•
Use "match-case" so that the SC-ADT does not have to convert case.
5-22
SpectraComm ADT
Installation and Operation Manual
Port Monitoring & Port Alerts
076R172-000
Issue 6
Advertisement
Table of Contents
