29
[Sysname-rta-template-rtcserver] quit
# Apply the template to the interface.
[Sysname] interface Serial 2/1/0
[Sysname-Serial2/1/0] link-protocol stlp
[Sysname-Serial2/1/0] rta terminal rtcclient 1
[Sysname-Serial2/1/0] quit
3.
Configure the UDP_1N_Server (Router B):
# Enable terminal access.
<Sysname> system-view
[Sysname] rta server enable
# Create a terminal template and enter terminal template view.
[Sysname] rta template rtcserver
# Configure the VTY.
[Sysname-rta-template-rtcserver] vty 0 rtc-multipeer 10.111.21.13 3000
# Configure the IP addresses and port numbers of the two initiators.
[Sysname-rta-template-rtcserver] rtc-multipeer 0 remote 10.111.0.12 3001
[Sysname-rta-template-rtcserver] rtc-multipeer 0 remote 10.111.33.12 3001
[Sysname-rta-template-rtcserver] quit
# Apply the template to the interface.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol stlp
[Sysname-Serial2/1/0] rta terminal rtcserver 1
[Sysname-Serial2/1/0] quit
Verifying the configuration
# Send data from Terminal B to Terminal A and Terminal C.
# Check that both Terminal A and Terminal C can receive the data.
Troubleshooting RTC terminal access
Failure to establish a terminal connection
Symptom
The terminal displays that the connection toggles between
Established
and
Establishing
state, and
ultimately goes down.
Analysis
The initiator and receiver are not configured consistently. Most mistakes result from inconsistent
configurations.
Solution
•
Verify that the same application mode (many-to-one or one-to-one) is configured on both the
initiator and the receiver.
•
Verify that the initiator and receiver are configured consistently, and that the configurations
comply with the parameter configuration conventions.
•
Verify that the router IP address configured on the receiver is the bound IP address if the source
address binding is configured on the initiator.
•
Verify that the initiator and receiver can reach each other.
