I think I got some hints, sharing.
====================================================================================================
- ! "no arp frame-relay" is a deprecated and abandoned command so it is
useless and unfunctional in most versions of IOS.
- It does NOT act as the rumour said "stop to response the inverse-arp
request from other end".
====================================================================================================
<Cisco Frame Relay Configurations>
http://blog.ine.com/tag/inverse-arp/
====================================================================================================
1. On a Cisco router, by default, physical interfaces are multipoint
interfaces.
2. Frame Relay multipoint subinterfaces created on Cisco routers behave very
much like the physical interfaces.
3. By default, the Cisco IOS software allocates all unassigned DLCIs
advertised by the Frame Relay switch to the physical interface on the
router.
4. It is also not required to enable or disable Inverse ARP, because there
is only a single remote destination on a point-to-point PVC and discovery is
not necessary.
- => "frame-relay inverse-arp" is only relative with MULTIPOINT and does
only work on MULTIPOINT interface/subinterface.
5. "frame-relay interface-dlci" is used to assign one individual DLCI to
particular multipoint/point-to-point subinterface from the physical
interface's DLCI pool.
- It's required on point-to-point subinterface for this logical
subinterface to recognize its own PVC to the other end.
- It can be used on physical interface or multipoint subinterface to
specify paticular PVC the frame-relay map-class or individual encapsulation
type.
"frame-relay inverse-arp"
1. Definitely used on point-to-point subinterfaces
2. Can be used on multipoint subinterfaces if Inverse ARP works
3. Not used on physical interfaces because all DLCIs belong there by
default.
====================================================================================================
On Tue, Dec 14, 2010 at 11:28 AM, Parahexen <parahexen_at_gmail.com> wrote:
> Hi, all!
>
>
> ----------------------------------------------------------------------------------------------------
> ? Which clock rate should be assigned to DCE commonly?
>
> ! "no arp frame-relay" is a deprecated and abandoned command so it is
> useless and unfunctional in most versions of IOS.
> It does NOT act as the rumour said "stop to response the inverse-arp
> request from other end".
>
> ? Does frame-relay subinterface inherit the inverse-arp behavior from its
> parent frame-relay physical interface?
> Does this inheritance act differently between point-to-point subinterface
> and point-to-multipoint subinterface?
> ? When parent frame-relay physical interface encapsulated in IETF standard,
> what happens actually if "frame-relay interface-dlci {dlci-number}" command
> without "ietf" keyword entered?
> We can observe the difference between with and without "ietf" keyword
> under the command "show frame-relay map", and in both conditions ping works.
>
> ! means solved, where ? means unsolved.
>
> ----------------------------------------------------------------------------------------------------
>
> Does anybody meet these questions before and did some experiments to prove?
>
> Thanks!
Blogs and organic groups at http://www.ccie.net
Received on Wed Dec 22 2010 - 09:27:56 ART
This archive was generated by hypermail 2.2.0 : Sat Jan 01 2011 - 09:37:49 ART