RE: ATM - pvc 'broadcast'

From: Brian Dennis (brian@labforge.com)
Date: Wed Jun 11 2003 - 16:26:47 GMT-3


If you are using a point-to-point sub-interface why would you need to
add the broadcast keyword? I do not know the question but the solutions
seem to have commands that aren't needed.

Rack6R6#sho run int atm1/0.1
Building configuration...

Current configuration : 92 bytes
!
interface ATM1/0.1 point-to-point
 ip address 54.254.1.6 255.255.255.0
 pvc 1/34
 !
end

Rack6R6#ping 54.254.1.6

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 54.254.1.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
Rack6R6#ping 255.255.255.255

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 54.254.1.254, 4 ms
Reply to request 1 from 54.254.1.254, 1 ms
Reply to request 2 from 54.254.1.254, 1 ms
Reply to request 3 from 54.254.1.254, 1 ms
Reply to request 4 from 54.254.1.254, 1 ms
Rack6R6#

Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Jason Cash
Sent: Tuesday, June 10, 2003 8:05 PM
To: ccielab@groupstudy.com
Subject: ATM - pvc 'broadcast'

I am working on a lab and one of the requirements is "broadcasts should
be
enables over the PVC".

R6(a4/0.69)------(a1/0.69)R9

The solution sets up 'protocol ip xxx' to ping across the interface:

interface ATM0/0.69 point-to-point

 ip address 172.16.56.5 255.255.255.252

 ip ospf authentication-key ipexpert

  pvc 0/32

   protocol ip 172.16.56.5

   protocol ip 172.16.56.6 broadcast

   ubr+ 3000 128

   oam-pvc manage 3

   encapsulation aal5snap

I chose to just to do the following:

interface ATM4/0.69 point-to-point

 ip address 172.16.56.6 255.255.255.252

 pvc 0/32

  ubr+ 3000 128

  broadcast

  oam-pvc manage 3

  encapsulation aal5snap

I guess am I wondering if, functionally, there is any difference. I am
able
to ping across this interface as well as est. neighbors without the
'protocol ip xxx' so is this a viable solution to this task?



This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:10:56 GMT-3