From: Kenneth Wygand (KWygand@customonline.com)
Date: Thu Feb 05 2004 - 12:35:24 GMT-3
Hey Scott,
Nothing crazy in the config, which I can send you offline if you'd like.
Here is the detailed follow-up response I received from Cisco's TAC:
---------------------------------------------------------------
Hi Kenneth,
There's a bug filed for the appletalk multilink scenario (CSCdp43172),
but because of the way appletalk is designed, the only option is to
disable the appletalk route-cache.
This Fastswitching of AppleTalk over multilink ppp is unsupported if
there is more than one interface in the multilink bundle.
PPP code expects the protocol's route cache to be updated prior to
encapsulating in multilink.
This works for most protocols because they add their cache update
routines to this registry. AppleTalk's cache update routine is not
invoked via this registry. It is invoked after the packet has been
successfully encapsulated and sent. Hence, the AppleTalk route cache
gets an incorrect entry due to the multilink encap.
AppleTalk was not modified to use this registry when it became
available, probably for good reasons. No enhancements to AppleTalk are
being done.
Please let me know if you need anything else.
Thank you,
Brian Severn
----------------------------------------------------------------
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
Network+, A+
Custom Computer Specialists, Inc.
"Success is to be measured not so much by the position one has reached
in life as by the obstacles which he has overcome while trying to
succeed."
-Booker Taliaferro Washington
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Wednesday, February 04, 2004 4:37 PM
To: Kenneth Wygand; ccielab@groupstudy.com
Subject: RE: Appletalk over PPP Multilink Bundle
If you could e-mail me offline, I'd be interested in seeing (edited) the
rest of your config. The "no appletalk route-cache" simply disables
fast-switching of the appletalk protocol. There shouldn't be any
inherent
reason to do that just because you are doing multilink PPP. The fact
that
you are creating a logical interface for your appletalk commands should
assist a long way in handling any funky route-cache issues.
Anyway, I'm curious now why that would be the solution... Or, on the
other
hand, what the actual problem was where this was the solution for it.
Thanks!
Scott
-----Original Message-----
From: Kenneth Wygand [mailto:KWygand@customonline.com]
Sent: Wednesday, February 04, 2004 3:08 PM
To: Scott Morris; ccielab@groupstudy.com
Subject: RE: Appletalk over PPP Multilink Bundle
Hey Scott (and everyone else interested),
The problem was.............
Needed to add "no appletalk route-cache" on all appletalk enabled
interfaces.....
Gotta luv TAC... :)
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
Network+, A+
Custom Computer Specialists, Inc.
"Success is to be measured not so much by the position one has reached
in
life as by the obstacles which he has overcome while trying to succeed."
-Booker Taliaferro Washington
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Tuesday, February 03, 2004 5:57 PM
To: Kenneth Wygand; ccielab@groupstudy.com
Subject: RE: Appletalk over PPP Multilink Bundle
The dialer map would only be necessary if you're going to dial. If
these
are P2P circuits, they're always up, so that L3/L2 mapping shouldn't
need to
take place (unless you have something else going on that you aren't
mentioning!).
As long as your multilink circuit is up, then things should be good to
go.
Remember that PPP negotiates protocols when it first starts up. So if
this
is something you are adding on to an existing multilink IP circuit,
you'll
need to bring the link down and back up in order to renegotiate these
things.
The cable range in appletalk is kinda like a subnet in IP. You'll have
a
net.node address. And the cable range specifies multiple "net"'s that
will
exist on that cable. You really only need one for a p2p circuit. It
has to
be unique (kinda like subnets) or routing gets all messed up.
So look at the existing ranges you have throughout your network and pick
something different! It's been a long time since I've really worked on
a
live Appletalk network, so the "best practices" are escaping me at the
moment. :) But just remember it's like a subnet and must be unique.
You can ping appletalk #.# to reach the other end of your circuit and
test
reachability locally. Then you just worry about your appletalk routing
(use
EIGRP, it's MUCH better than then inherent Appletalk routing protocol
(RTMP
I think)).
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
CISSP,
JNCIS, et al.
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
-----Original Message-----
From: Kenneth Wygand [mailto:KWygand@customonline.com]
Sent: Tuesday, February 03, 2004 5:38 PM
To: Scott Morris; ccielab@groupstudy.com
Subject: RE: Appletalk over PPP Multilink Bundle
Thanks Scott. By "it" in "Then it would be on your virtual interface"
(and yes it is a multilink interface), would my configuration also have
to
include a dialer-map for some reason? Right now I just have the CABLE
RANGE
and ZONE defined...
This worked fine when I had a different cable range on both physical
circuits and the same zone configured on both circuits. When I
multilinked
the channels, I used one of the cable ranges that was on one of the
physical
interface for the virtual interface and I scrapped the other cable
range. I
also transferred over the Appletalk zone. Now there is no appletalk
communication between sites.
Having VERY limited knowledge of Appletalk, I figured some routing
information might be cached on workstations that were using the cable
range
I removed from the second circuit. I figured I would trash the
preferences,
etc. and see if it works, but now that you mentioned watching out for
the
Dialer Map, that might be where my problem is...
So that was the long way of asking if I still need to configure a
dialer-map
with my current set up. :)
Thanks a billion. (a thousand times more than last time... :) )
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
Network+, A+
Custom Computer Specialists, Inc.
"Success is to be measured not so much by the position one has reached
in
life as by the obstacles which he has overcome while trying to succeed."
-Booker Taliaferro Washington
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Tuesday, February 03, 2004 5:34 PM
To: Kenneth Wygand; ccielab@groupstudy.com
Subject: RE: Appletalk over PPP Multilink Bundle
Ahhhh... Then it would be on your virtual interface (multilink
interface?)
wherever you have the rest of your L3 stuff.
Cheers,
Scott
-----Original Message-----
From: Kenneth Wygand [mailto:KWygand@customonline.com]
Sent: Tuesday, February 03, 2004 5:30 PM
To: Scott Morris; ccielab@groupstudy.com
Subject: RE: Appletalk over PPP Multilink Bundle
Thanks for your prompt reply, Scott.
The multilinked circuits are PPP encapsulated PTP Serial Interfaces...
do I still need a dialer-map if its not a DDR interface?
Thanks a million!
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
Network+, A+
Custom Computer Specialists, Inc.
"Success is to be measured not so much by the position one has reached
in
life as by the obstacles which he has overcome while trying to succeed."
-Booker Taliaferro Washington
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Tuesday, February 03, 2004 5:13 PM
To: Kenneth Wygand; ccielab@groupstudy.com
Subject: RE: Appletalk over PPP Multilink Bundle
Oooooo.. Oooo... Appletalk. I remember this. :)
It will depend on what the rest of your configuration is, but those
commands
will go the same place in your config as your IP and any other L3
addressing
schemes.
Don't forget a dialer map though if you're configuring in that fashion!
Appletalk is a different protocol than IP!
Wow... I miss having that on the lab. I mean, where else do you get
martians randomly appearing in your network? :)
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
CISSP,
JNCIS, et al.
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Kenneth Wygand
Sent: Tuesday, February 03, 2004 4:36 PM
To: ccielab@groupstudy.com
Subject: Appletalk over PPP Multilink Bundle
Hello everyone!
Quick question - if I create a PPP multilink bundle and I want to enable
Appletalk routing over it, do I configure the following on both physical
interfaces, the virtual interface, or both:
appletalk cable-range 100-100 100.1
appletalk zone ZONENAME
I would think just the virtual interface, but that's the way its
configured
and its not working right now.
Thanks in advance!
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
Network+, A+
Custom Computer Specialists, Inc.
"Success is to be measured not so much by the position one has reached
in
life as by the obstacles which he has overcome while trying to succeed."
-Booker Taliaferro Washington
This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:46 GMT-3