- Hewlett-Packard User Guide Printer LCS60
Table Of Contents
- TR.PDF
- 1.PDF
- 2.PDF
- Hardware Installation
- Introduction
- Site Preparation
- Assembly
- Installing the LCS60
- Rack Mounting
- Wall Mounting
- Table-Top Mounting
- Connecting the System Console
- Direct Connection to the LCS60
- Connection through a Data Switch
- Connection through Modems
- Connection through StarKeeper II NMS
- Connecting the Fiber Interface
- Configuration of the Lucent Technologies Data Switch ± LCS60
- Power and Grounding
- Verify LCS60 Console Connection
- Verify Fiber Connection
- Configure the LCS60
- LAN Connections
- Hardware Installation
- 3.PDF
- 4.PDF
- 5.PDF
- 6.PDF
- 7.PDF
- 8.PDF
- Administration
- Basics
- Logging On
- lcsadm Interface
- Typical Administrative Tasks
- Backup and Restore Operations
- Network Access Password Option
- Status
- Error Messages
- Administration
- 9.PDF
- 10.PDF
- 11.PDF
- 12.PDF
- 13.PDF
- 14.PDF
- 15.PDF
- 16.PDF
- IX.PDF
ROUTE ROUTE ( 1M )
DIAGNOSTICS
Exit status is zero for normal termination, a positive number for error termination.
add host destination: gateway gateway
add network destination: gateway gateway
The specified route was successfully added to the route table.
del host destination: gateway gateway
del network destination: gateway gateway
The specified route was successfully deleted from the route table.
destination gateway done
This message is displayed for each route deleted by the flush command.
not in table
A delete operation was attempted for an entry that wasn’t present in the tables.
MTU too large
The entry was not added to the table because the MTU value requested was too
large.
no current route to gateway
The entry was not added to the table because there is no route to gateway.
routing table overflow
The entry was not added to the table because the table is full.
already exists.br The entry was not added to the table because the same route
already exists.
illegal flags set
RTF_UP flag not on.
NOTES
Using the flush command of route(1M) while routed(1M) is running will cause
inconsistencies in the route tables. If this happens, the route daemon, routed(1M),
must be restarted.
SEE ALSO
netstat(1)
named(1M), routed(1M)
Issue 3 E-41