3Com MSR 30, MSR 50 Bind vpn-instance, Syntax bind vpn-instance vpn-name Undo bind vpn-instance

900CHAPTER 70: TERMINAL ACCESS CONFIGURATION COMMANDS

Use the undo auto-linkcommand to restore the default. By default, the automatic link establishment time is 0 seconds, namely, no automatic link establishment is performed.

The terminal access feature supports the automatic link establishment function. You can enable the function and configure the automatic link establishment time in terminal template view. When the terminal is in the “OK” state (meaning the physical connection is normal), the router automatically establishes a TCP connection to the remote router or FEP after the specified period of time. If the automatic link establishment function is disabled on the terminal, a link needs to established manually (manual link establishment is the default mode). The router establishes a TCP connection to the FEP only after a user enters a character on the terminal, except the special characters for hotkeys and terminals. Special characters are the characters that the terminals process directly, such as <Shift+F2>. For details, see the related manuals of terminals.

Example # Set the automatic link establishment time to 10 seconds.

<Sysname> system-view

[Sysname] rta template abc

[Sysname-rta-template-abc] auto-link 10

bind vpn-instance

Syntax bind vpn-instance vpn-name

undo bind vpn-instance

View Terminal template view

Parameters vpn-name: VPN instance name, a string of 1 to 31 case-insensitive characters.

Description Use the bind vpn-instancecommand to bind a VPN instance with the terminal template. Use the undo bind vpn-instancecommand to remove the VPN instance binding.

By default, no VPN instance is bound with a terminal template.

This configuration is required when the TTY terminal access initiator also acts as an MPLS provider edge (PE) router at the same time. When you apply a terminal template configured with the bind vpn-instancecommand to an asynchronous interface, the terminal corresponding to the asynchronous interface is bound with the VPN instance. Thus, the terminal access initiator can group the terminals into different VPN domains. The RTC server can receive the connection request from any VPN without being configured with the bind vpn-instancecommand.

A template can be bound with only one VPN instance. If VPN instance binding is configured with this command for more than once, the latest configuration applies.

Example # Bind the VPN instance vpn1 with the terminal template.