PDF user manual for CopperEdge 150

&RQILJXULQJ:$19&VVirtual Circuits, either Frame Relay or ATM, used only as destinationsof policy IP routes do not need to be elaborately configured.For those VCs, simply specify the Frame Relay DataLink Circuit Identifier (DLCI) or ATM virtual circuit number associatedwith the circuit in the destPii of the DSL links. Activatethe circuit as described below.In this mode, the CE150 has no knowledge of IP addresses atthe far end of the VC. As a result, the CE150 is fully independentof the far-end IP numbering scheme. In fact, two differentVCs can have duplicate, overlapping IP addresses (impossiblewith full IP routing), and the CE150 will not be affected.If you wish, you can give IP addresses to the VCs. The CE150treats each VC as a separate point-to-point (unnumbered) IPlink. Unnumbered IP links are ones with no IP subnet number.Each end of an unnumbered IP link may have an IP address,and if both are present, the two addresses can be on differentsubnets.However, the preferred way to configure an unnumbered IP linkis to assign it a FarEndAddr, but not an IP address. TheFarEndAddr tells the CE150 what the IP address of the deviceat the far end of the point-to-point link is. The WAN port at thenear (CE150) end of the link typically has no use for an IP address.See the configuration below:Group: cmIfaceTableInstance: [1.2.1.32]PII = 1.2.1.32IfIndex = 1.2.1.32Name = ....AdditionalInfo = ....GroupName = ....NetModel= IPIpAddr = 0.0.0.0NetMask = 0.0.0.0MacAddr= ff.ff.ff.ff.ff.ffBurnedInMacAddr= ff.ff.ff.ff.ff.ffFarEndAddr = 192.166.101.8DestPii = 0.0.0.0CMCPCompatible= NoEncapsulationType = rfc1490FwdMode= Full-IPPix = 141Once the FarEndAddr is defined for the VCs, you can use thoseIP addresses as the next-hop for route table entries. For moreinformation, see the ipRoute table description in the Copper-Edge 150 CopperCraft Reference and MIB Definitions manual.For example:CRAFT> set iproute [192.168.250.0] nexthop=192.166.101.8&RSSHU(GJH,QVWDOODWLRQDQG2SHUDWLQJ*XLGH