Thank you to everyone who took the time to make suggestions. I seem
to have fixed the problem, but I can't pinpoint exactly which command
or configuration change worked the magic.
As you suggested, I made sure that portfast was on, port channel was
off, and that the ports were not set to trunk and the problem still
persisted. The next step I took was to make sure the ports broadcast
limit was at 100%(set port broadcast <mod_num/port_num>
<threshold>[%]). By default this should have, and apparently was,
already set to 100%. But after I manually typed in the command the
problem went away. And the real mindtwister is that the problem went
away on ALL of the affected Macs in that VLAN(including on an
upstream switch), not only the Mac on the interface I had specified.
I'm guessing that something must have propagated all the way to the
RSM.
When the Macs boot up now they still get a window that says "Your
AppleTalk network has become available". But it's just an FYI
message. It doesn't require you to go into the AppleTalk control
panel.
Thank you for taking the time to write back,
Dave
>Hi again,
>
>A few last points before I sign off for the night:
>
>1) You do indeed have to ask your users to pay attention to the
>error message and do as it says (open and close the Control Panel).
>The person who told me it was just an FYI message was forgetting the
>reality of working with AppleTalk. (It was my husband, who was
>actually one of the creators of AppleTalk. He tends to forget bad
>things about it. Just kidding.)
>
>2) The Apple white paper is indeed very vague about a real solution
>to the problem. &;-) But the solution is that you have to tweak the
>spanning tree parameters so that the switch ports don't take so long
>to start forwarding packets. Bottom line: the router's (RSM's)
>packets aren't getting through in time to the end nodes so they
>think they are on an isolated network. Then when they finally hear
>from the router, they put up that annoying message. Another solution
>would be to upgrade to Mac OS X, it sounds like?! ;-]
>
>3) Having multiple seed routers is not a problem. (Even if you had
>multiple seed routers, I mean, it wouldn't be a problem. Multiple
>seed routers is a good thing.)
>
>Good luck! By the way, thank-you for buying my book. I hope you like
>it. Talk to you later,
>
>Priscilla
>
>At 06:49 PM 10/16/00, Dave Redwood wrote:
>>Thanks to everyone who sent a response. I'm sorry I didn't give more
>>details when I wrote last night; I think I was just on the verge of going
>>to sleep.
>>
>>The exact message was:
>>
>>"Your AppleTalk network has become available. To use the network, open the
>>AppleTalk control panel, then close it. "
>>
>>So the users actually have to open the control panel in order to access
>>other AppleTalk devices(even if they are in the same VLAN or segment). And
>>no zones are displayed until after the control panel is opened and then
>>closed.
>>
>>
>>I've tried locking down the ports to all possible combinations of 10/100
>>half/full, setting the ports of the affected machines to portfast/regular
>>STP implementations, and the problem still lingers. The only thing I have
>>noticed in the last 24hrs is that the machines running OS-X beta aren't
>>having the problem, those running OS9 and earlier are)
>>
>>We don't have multiple seed routers(but thx for suggesting it Chris!).
>>Here's our layout:
>>
>>(multiple mac clients G3/G4/etc...)
>> |
>> |
>> 100/full (But i've tried all possible combinations)
>> |
>> |
>> Catalyst 5500a(VLAN 33)
>> |
>> |
>> GigE-net
>> |
>> |
>> Catalyst 5500b(VLAN 33)
>> |
>> |
>> GigE-net
>> |
>> |
>> Catalyst 5500c w/RSM ISL
>>
>>And the Apple TIL mentions this exact issue. However a clear solution isn't
>>provided. But thank you for noting it(Priscilla) and finding the link for
>>me(Daniel) it definitely is worth the read.
>>
>>Well, I think I'm stuck. But I'll keep working on the problem and let you
>>know if I find a solution.
>>
>>Thank you *all*(Ian, Daniel, Chris and Priscilla) for taking the time to
>>make the suggestions
>>
>>P.S.: Priscilla, I just started reading TDND and am loving it. I'm
>>honored(I would try to find a more subtle word, but it's true) to have had
>>your input on this issue.
>>
>>
>>_________________________________
>>FAQ, list archives, and subscription info:
>>http://www.groupstudy.com/list/cisco.html
>>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
>
>________________________
>
>Priscilla Oppenheimer
>http://www.priscilla.com
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
