Testing The Configuration - Digi PortServer CM User Manual

Testing the Configuration

After having executed the command signal_ras hup to activate the changes you have made to the
configuration files, test the configuration by performing the following test:
1. Since RADIUS authentication was chosen, create a new user on the RADIUS authentication server
called test and provide him with the password test.
2. From the console, enter the command:
ping 200.200.200.2
to make sure the RADIUS authentication server is reachable.
3. Verify that the physical connection between the PortServer CM and the servers is correct. A cross cable
(not the modem cable provided with the product) should be used. Refer to the hardware specifications
for pin-out diagrams.
4. Verify that the PortServer CM has been set for communication at 9600 bps, 8N1. The device must also
be configured to communicate on the serial console port with the same parameters.
5. Verify that the computer is configured to route console data to the serial console port.
6. From a server on the LAN (not from the console), telnet to the device connected to the first port of the
PortServer CM using the following command:
telnet 200.200.200.1 7001
For both telnet and ssh sessions, the devices can be reached by either:
• Ethernet IP of the PortServer CM and assigned socket port or
• Individual IP assigned to each port.
If everything is configured correctly, a telnet session should open on the device connected to port 1. If not,
2-16 Execute the command signal_ras hup to activate the changes.