Network Router User Manual
Table Of Contents
- IOLINK-520 and IOLINK-PRO USER AND SYSTEM ADMINISTRATION GUIDE
- Installation
- Typical Applications & How to Configure Them
- 2.1 - Bridging and Routing
- Should You Bridge or Route?
- 2.2 Basic WAN Configurations
- 2.3 - Configure Remote Site Profiles
- 2.4 Advanced Features
- Introductionto Filtering
- Appendix AMenu Trees
- Appendix BOctet Locations on Ethernet Frames
- Appendix CServicing Information
- Opening the case
- Identifying the Internal Components
- To Clear a “Lost” Password
- Changing LAN or WAN Interfaces
- Selecting MDI or MDI-X LAN Interface
- Installing the ISDN Link Modules
- Processor settings for the ISDN Link Modules
- Changing the Termination Straps on the ISDN S/T Interface
- Connecting to the ISDN-U Link Module
- Performing a Software Upgrade
- Appendix DInterface Pinouts
- Pinout Information
- Link Clocking Information
- ATL-CSU/DSU Link Module Information
- Console Pinouts
- V.24 & RS232C Link Pinouts
- V.11/X.21 Link Pinouts
- RS442 & RS530 Link Pinouts
- V.35 Link Pinouts
- RS232 Null-Modem Cable Configuration
- V.35 Null-Modem Cable Configuration
- RS530 Null-Modem Cable Configuration
- RS530 To RS449 Conversion Cable
- V.11/X.21 Null-Modem Cable Configuration
- Index
- Warranty
Applications
IOLINK-520 & IOLINK-PRO Installation & Applications Guide —
2.29
2.3.2 - Configure Remote Site Profile for Frame Relay
Each of the PVC’s on the frame relay service must be configured within an individual
remote site profile on the IOLINK router. This is usually done automatically through the
auto-learning process. When the frame relay router first starts up it will query the frame
relay service to try to determine the PVC configurations. If the DLCI numbers of the
PVC’s on your service are determined during startup, the IOLINK router will
automatically create a remote site profile for each PVC. The automatically created remote
site profiles will be named “LinkxDLCIyyy” where x is the physical link number the PVC
is on and yyy is the DLCI of the PVC.
If during this learning process the maximum number of remote sites has been
reached, the IOLINK router will prompt you that there are no remote sites available.
A new remote site cannot be auto-created unless one of the existing remote sites is
manually deleted.
These automatically created remote site profiles may be renamed for easier identification
or usage by changing the Remote Site Alias.
Remote Site Profile Alias
Location: Main
!
Configuration
!
Connections up
!
Remote Site Set-up
!
Edit Remote Site
!
Remote Site Alias
Configuration: When configuring the IOLINK router to use PAP or CHAP security
Note authentication, after the IOLINK router has automatically created remote site
profiles for each of the PVC’s, either the remote site profile alias must be
changed to match the Outgoing User Name configured on the remote site
router or vice versa. If the local remote site alias and the remote site routers
outgoing user name do not match, the PVC will always fail with a security
violation. Also note that PPP encapsulation must be enabled to run security
access authentication.
With auto-learning, the above is all that is required of the user to set-up frame relay
remote site profiles. If desired, parameters may be entered manually as follows:
Each PVC defined on this IOLINK router must have a DLCI (Data Link Connection
Identifier) value assigned for proper frame relay communication.
DLCI
Location:
Main
!
Configuration
!
Connections up
!
Remote Site Set-up
!
Edit Remote Site
!
Connection Set-up
!
DLCI
"
""
"
"
""
"