Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Trouble uplinking a cisco catalyst 2960 to a 3600



Matt Brodeur wrote:
> On Wed, Jun 14, 2006 at 07:43:04PM -0400, John Abreau wrote:
>>> I didn't see any match for dot1q in the 2960 settings, and no reference
>>> to either that or to 802.1q in the pdf manuals.
> 
> A quick google reminded me that the newer switches (like your 2960)
> don't do ISL, only dot1q.  You might still need the "switch trunk
> allow vlan blah" bit, though.
> 
> 
>>> Following that, I reconfigured the 3500's port to use access mode
>>> instead of trunk mode, and the 2960 worked fine that way.
>>>
>>> But if I understand correctly, I'm limited to the one VLAN with these
>>> settings; I can add machines to vlan4 through the new switch, but not
>>> to vlan1, vlan2, vlan8, or vlan12 which the 3500 also uses.
> 
> That's correct.  Access mode means that you get the traffic of one
> VLAN.  Multi mode means you get multiple VLANs dumped to one port.
> Trunk mode gets you multiple VLANs with each frame tagged so you can
> tell them apart.

One of the parts that confused me was the fact that the trunk settings
worked with a couple of the servers. Earlier this afternoon I did a
sanity check by plugging in a laptop on a port with the trunk settings.

When that failed to work, I examined holden's network settings to see
why it worked on a trunk port, and I found the setting "VLAN=yes" in
/etc/sysconfig/network.

So it seems I was starting with a false expectation to begin with.
I shouldn't be able to ping the 3500 or anything past it until
I've configured the vlan settings on the 2960.

Is there anything more accessible than the Cisco manuals you can
recommend to get me pointed in the right direction? The Cisco manuals
seem to focus either on the low-level ISO commands without giving
enough context to be useful, or on a higher level of designing a
network infrastructure from scratch. I haven't found anything useful
to help me figure out how to just cluster the two switches.


-- 
John Abreau / Executive Director, Boston Linux & Unix
ICQ 28611923 / AIM abreauj / JABBER jabr at jabber.org / YAHOO abreauj
Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jabr.vcf
Type: text/x-vcard
Size: 294 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20060615/ad05f3af/attachment.vcf>



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org