RE: Use of the 31-Bit Prefixe in a P2P Link

From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Wed Oct 12 2005 - 02:41:07 GMT-3


Victor,
        Have you looked at the RFC to help get an understanding (RFC
3021 - Using 31-Bit Prefixes on IPv4 Point-to-Point Links)?

http://www.internetworkexpert.com/rfc/rfc3021.txt

HTH,

Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
 
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
 

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Victor Cappuccio
Sent: Tuesday, October 11, 2005 7:15 PM
To: Cisco certification
Subject: Use of the 31-Bit Prefixe in a P2P Link

Hello All, sorry for this dummy question, but could any one please
explain the use of the 31-Bit Prefixe in a P2P Link
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft
/122t/122t2/ft31addr.htm

Im trying to configure a P2P Link with a Frame-relay encapsulation, but

I think that I do not understand the addressing scheme,

R1 s0/0 ----- Transparent Line ------ s0/0/0 R2

On R1:
Interface serial 0/0
Encapsualtion frame-relay
No keepalive
No ip address
no shut
Clock rate 64000

Interface serial 0/0.1 point-to-pint
Ip address 172.16.78.0 255.255.255.254
Frame-relay interface-dlci 1

Interface serial 0/0.2 point-to-pint
Ip address 172.16.78.2 255.255.255.254
Frame-relay interface-dlci 2

On R2:

Interface serial 0/0/0
Encapsualtion frame-relay
No keepalive
no shut
No ip address

Interface serial 0/0/0.1 point-to-pint
Ip address 172.16.78.1 255.255.255.254
Frame-relay interface-dlci 1

Interface serial 0/0.2 point-to-pint
Ip address 172.16.78.3 255.255.255.254
Frame-relay interface-dlci 2

Do this only works for this kind of interfaces? Where we can use the
whole /30 as a bundle or there is another freaking application for this?

Thanks
Victor.



This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:50 GMT-3