Opening a COM (Console) Session
only the first error will be reported, along with a count of the sum of errors incurred. In the case of a single error, only the error line will be reported. Error messages will be logged as well. Because the result of continuing to process a flawed
•Router ports and protocol stacks are initialized based on startup configuration.
•Alarms and messages reported during initialization are logged.
•COM is up.
•The XSR is up.
To view the screen output produced when the XSR reboots, refer to “XSR Rebooting
Characteristics” on page
Opening a COM (Console) Session
1.Open a COM session to the XSR using Procomm or another program.
Set the session properties as follows: BPS - 9600, Data bits - 8, Parity - none, Stop bits - 1, Flow control - none. Refer to “Initialization Output” on page
2.When the XSR login appears, enter admin and enter no (blank) password. Note that logins and passwords can be changed later.
Note: You can abort RAI at any time by pressing any key.
Refer to the following section for quick configuration of RAI. For a full description of RAI including how it works, refer to “Chapter 2: Managing the XSR” in the XSR User’s Guide.
Optional: Configuring Remote Auto Install
In short, the RAI application transports a startup configuration file from a TFTP server for use in configuring the remote XSR. This file is placed in the Flash: directory as the
For remote XSR setup, you need only hook up cabling as described in ”Chapter 2: Hardware Installation” of this guide.
Configuring RAI for Frame Relay
To configure two remote XSRs with RAI over Frame Relay, perform the following setup on the central site. On
This configuration supports two remote XSRs connected on DLCIs 16 and 18. Make sure with your Frame Relay provider that these DLCIs terminate at the location of the remote XSRs. To add more remote XSRs, you will need additional DLCIs.
XSR Getting Started Guide