Mark,
My first paragraph in my reply was a bit unclear, sorry.
I noted, ' I have seen issues with using vlan-id 0 on the Juniper, because Cisco doesn't start VLAN numbering until VLAN 1 even though Juniper supports VLAN id 1.'
I mean to relate, 'I have seen issues with using vlan-id 0 on the Juniper, because Cisco doesn't start VLAN numbering until VLAN 1 even though Juniper supports VLAN id 0'.
Sorry for the confusion.
Bob
-----Original Message-----
From: Robert O'Hara
Sent: Thursday, September 27, 2001 3:51 PM
To: 'mark forest'; juniper-nsp@puck.nether.net
Subject: RE: [j-nsp] vlan-tagging
Hi Mark,
A few possibilities:
I have seen issues with using vlan-id 0 on the Juniper, because Cisco doesn't start VLAN numbering until VLAN 1 even though Juniper supports VLAN id 1. So, VLAN-ID 0 is to be avoided whenever connecting Juniper to Catalyst.
Also, VLAN 1 has a special use by default for Cisco Catalyst - Cisco uses it for BPDU's and other control functions. I have no details on this last point as I am not a Catalyst expert, but I know for sure that if you want to use VLAN-ID 1 between Cisco and Juniper, you have to disable the Cisco administration (control) traffic. It is not intuitive how to do this, as the Cisco SE at one account had to poke around for a quite a while to find out how to turn this traffic off. He finally figured it out, but there were a couple of places he had to touch to do it. Here's a hint, if you are having this problem: this particular problem will show up as L2 channel errors on the Juniper sub-interface. This can be observed by issuing a 'show interface <int-name.unit> extensive details'.
Finally, I have seen one other problem where .1q was not configured properly on the Cisco, and the Juniper would count the MAC frames and show no errors at the MAC layer, but the IP or 'traffic counters' would not register any incrementation of the counters. This can be observed by issuing a
'show interface <int-name.unit> extensive details'.
The only other issue I can think of related to Catalyst was a problem with
using a large MTU with Gig-e trunking. There were some pretty nasty bugs with the Catalyst and you have to have the correct software release to do this.
This is a known issue to Cisco, so if you are trying to do this, give them a call
and make sure you have the right version of code to make this work.
I hope this helps.
Thanks,
Bob O'Hara
Systems Engineer
Juniper Networks
Northeast Sales Region
.........................................
. email: rohara@juniper.net .
.........................................
-----Original Message-----
From: mark forest [mailto:milo279@yahoo.com]
Sent: Monday, September 24, 2001 11:09 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] vlan-tagging
I am currently working on a project where I need to
configure trunking/tagging between a cisco cat 5500
and Juniper. As is, when I set up a vlan on the
cat5500 and configure routing on the rsm, I can
communicate with the Juniper no problem. Once I
attempt to configure the trunking on the cisco to
dot1q and set vlan-tagging up on the juniper I loose
connectivity. I suspect I am missing something rather
simple. If anyone has experience with
trunking/tagging between cisco and Juniper pls let me
know.
Milo
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:37 EDT