Net Worker World

R1 ---------------------R2 R2(config-router)# do sh ip bgp nei 100.100.12.1 BGP neighbor is 100.100.12.1,  remote AS 100, external link   BGP version 4, remote router ID 10.10.30.1   BGP state = Established, up for 00:44:20   Last read 00:00:20, last write 00:00:20, hold time is 180, keepalive interval is 60 seconds   Neighbor capabilities:     Route refresh: advertised and received(old & new)     Address family IPv4 Unicast: advertised and received     ...... Without soft-reconfiguration, clear ip bgp * soft command sends Refresh Request, as long as the peer router has Route Refresh capability, it sends back updates with entire BGP table. this command does the same work with command clear ip bgp * in . R2# debug ip bgp BGP debugging is on for address family: IPv4 Unicast R2# debug ip bgp up BGP updates debugging is on for address family: IPv4 Unicast R2# R2# R2# clear ip bgp * soft R2# *Mar  1 00:06:01.987: BGP: 100.100.12.1 sending REFRESH_REQ (5) for a

As we know, K1 and K3 are set to a value of 1 by default, and other values are set to 0. Armed with that information, we can reduce our formula to the following: EIGRP Metric = 256*(10000000/Bw + Delay) Bw in kilobits, delay in tens of microseconds Note the Bw is the MINIMUM bandwidth from point A to point B. For a packet from R1 to R10, R3 s1/0 interface and R10 f0/0 interface use the same Bw value which is R3 s1/0 bandwidth to calculate their own metric. So for a given path, when calculate each metric on each router inbound interface, the metric difference is the difference of Delay portion. For example, the difference between R10 f0/0 metric and R3 s1/0 metric is Metric Difference =  256 * (R10-cumulated-delay - R3 cumulated-delay) for the neighbor router like R10 and R3, the increased metric on R10 f0/0 interface is 256x local interface Delay calculated value. So R10 f0/0 interface metric = R3 reported metric + R10 f0/0 local delay calculated value. In case of F0/0

     R5 is PPPoE server and R6 is PPPoE client:   R6# interface FastEthernet0/0  no ip address  duplex auto  speed auto  pppoe enable      >>> added automatically when issue pppoe-client command   pppoe-client dial-pool-number 1    >>>assign physical interface to dialer pool end ! interface Dialer1   mtu 1492   ip address negotiated     >>>> get IP address via PPP/IPCP from the server   encapsulation ppp   dialer pool 1                   >>>> specify dialer pool for logical interface  ppp pap sent-username R6 password 0 cisco end    R5# R5(config)# bba-group pppoe global R5(config-bba-group)# virtual-template 1 ! interface Virtual-Template1  mtu 1492  ip address 56.56.56.5 255.255.255.0  peer default ip address pool PPPoE_Pool  ppp authentication pap end R5(config)#ip local pool PPPoE_Pool 56.56.56.6 56.56.56.10 R5(config)#int f0/0 R5(config-if)# pppoe enable R5(config-if)#^Z R5#sh run

PAP R6 requires authentication: interface Multilink1  ip address 69.69.69.6 255.255.255.0  ppp authentication pap  ppp multilink  ppp multilink group 1 end R6(config)# username R9 password cisco R9 presents login and credential: interface Multilink1  ip address 69.69.69.9 255.255.255.0   ppp pap sent-username R9 password 0 cisco  ppp multilink  ppp multilink group 1 end CHAP R6 requires authentication: interface Multilink1  ip address 69.69.69.6 255.255.255.0  ppp authentication chap  ppp multilink  ppp multilink group 1 end R6(config)# username R9 password cisco R9 responses R6 CHAP challenge, the account much exists on both challenger and responder, the username is peer hostname and the password much be same.  interface Multilink1  ip address 69.69.69.9 255.255.255.0   ppp multilink  ppp multilink group 1 end R9(config)# username R6 password cisco Or configure CHAP responder at interface level: interface Multilink1  ip address 69.69.69.9