Network Router User Manual

Chapter 25: WAN Configuration Guide
334 SmartSwitch Router User Reference Manual
Using the same approach, a PPP high-speed serial interface (HSSI) WAN port located at
router slot 3, port 2 would be identified as “hs.3.2”.
Configuring WAN Interfaces
Configuring IP & IPX interfaces for the WAN is generally the same as for the LAN. You
can configure IP/IPX interfaces on the physical port or you can configure the interface as
part of a VLAN for WAN interfaces. However, in the case of IP interfaces, you can
configure multiple IP addresses for each interface. Please refer to “Configuring IP
Interfaces and Parameters” on page 78 and “Configuring IPX Interfaces and Parameters”
on page 252 for more specific information.
There are some special considerations that apply only to WAN interfaces; these are
detailed in this section.
Primary and Secondary Addresses
Like LAN interfaces, WAN interfaces can have primary and secondary IP addresses. For
Frame Relay, you can configure primary and secondary addresses which are static or
dynamic. For PPP, however, the primary addresses may be dynamic or static, but the
secondary addresses must be static. This is because the primary addresses of both the
local and peer routers are exchanged during IPCP/IPXCP negotiation.
Note:
There is no mechanism in PPP for obtaining any secondary addresses from the
peer.
Static, Mapped, and Dynamic Peer IP/IPX Addresses
The following sections describe the difference between static, mapped, and dynamic peer
IP and IPX addresses and provide simple command line examples for configuration.
Static Addresses
If the peer IP/IPX address is known before system setup, you can specify the peer address
when the interface is created. This disables Inverse ARP (InArp) for Frame Relay on that
source/peer address pair; however, InArp will still be enabled for any other addresses on
that interface or other interfaces. A static peer address for PPP means that the address the
peer supplies during IP Control Protocol (IPCP) or IPX Control Protocol (IPXCP)
negotiations will be ignored.
The following command line displays an example for a port:
interface create ip IPWAN address-netmask 10.50.1.1/16 peer-address
10.50.1.2 port hs.3.1