From: Chris Lewis \(chrlewis\) (chrlewis@cisco.com)
Date: Thu Jul 14 2005 - 11:32:49 GMT-3
Brian's solution creates a multilink interface which can be viewed via
the show ip interface brief command and all protocol configurations are
placed under the multilink interface. In your configuration, the links
are bundled, but no multilink interface is created; protocol
specifications are still under the virtual-template. In my experience,
multilink interfaces have less problems, even though a virtual-template
is configured for multilink interfaces, moving the protocol
configuration to the multilink interface seems to make things more
reliable.
Chris
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Jacky Murphy
Sent: Thursday, July 14, 2005 5:07 AM
To: ccielab@groupstudy.com
Cc: Jacky Murphy
Subject: "multilink virtual-template 1" and "interface multilink 1"
Hi group,
Task 2.5 - 2.8 Brian's IEWB
what different between "multilink virtual-template 1" and "interface
multilink 1"?
can i use command "multilink virtual-template 1" ?
case 1: (My solution)
-------------------------------------------------------
multilink virtual-template 1
!
interface Virtual-Template1
ip address 174.1.45.5 255.255.255.0
ppp multilink
ppp authendication chap
-------------------------------------------------------
case 2: (Brian's Solution)
-------------------------------------------------------
interface Multilink 1
ip address 174.1.45.5 255.255.255.0
ppp multilink
multilink-group 1
!
interface Virtual-Template1
ppp multilink
multilink-group 1
ppp authendication chap
-------------------------------------------------------
Thanks,
Jacky
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:29 GMT-3