From: Darby Weaver (darbyweaver@yahoo.com)
Date: Sun Apr 22 2007 - 00:56:42 ART
Nope - I turned up R3 and R4.
I even added a secondary IP to R3 - which gets no
mapping as expected. Only the primary ip address did.
R4 has only Frame enabled and CDP and had no fram
mapping till ip address was added.
All as expected and normal fair.
However, how does one artificially create the 0.0.0.0
inverse are mappings.
Do I need to do something special?
I always assumed (Ass out of U and Me) than they were
just the by-product of unconfigured frame spokes.
Now I wonder...
I guess I better go back and review the NMC COD and
the IE COD and see if these guys explained this to me
somehwere and I missed it.
Of course the goal is typically to remove them and not
create them.
So - if I never had them and thought I was doing
something correctly, perhaps I was not as correct as I
had thought I was.
However, since I learned to not create the problem and
a couple of techniques that worked I thought this
topic closed.
But if I cannot create them, then, I stand reason of
being in Todd's boat of not being able to correct them
should they come up sometime.
However, I must say in the past, I have resolved this
issue successfully. But what if it does persist?
Anyone can add more to "how to create 0.0.0.0 inverse
arp mappings if we do not get them by default"?
Hate to ask for the opposite of what we normally want,
but I ma curious and I'm not sure I will find this
where I am going back to look.
I do have my Cisco Press Frame Relay Solutions book on
hand and I'll hit it too - I normally do not have to
many questions.
But this was a given that is not working the way I
understood it to work.
This archive was generated by hypermail 2.1.4 : Tue May 01 2007 - 08:28:36 ART