Thanks Ryan for clarifying what Justin said. I get it now. I hope they can accomodate that. Johnny
--- On Tue, 8/19/08, Ryan Lambert <[EMAIL PROTECTED]> wrote: From: Ryan Lambert <[EMAIL PROTECTED]> Subject: RE: [c-nsp] Unable to connect VLAN traffic To: [EMAIL PROTECTED], "'Justin Shore'" <[EMAIL PROTECTED]> Cc: [email protected] Date: Tuesday, August 19, 2008, 11:25 PM Johnny, I think the better solution if your provider can accommodate, is to do Q-in-Q instead of having to dictate what tags you can use. This allows you, as Justin mentioned, to use your own tags across the circuit instead of having to coordinate with them every time you need to add another VLAN, or change something. -Ryan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Johnny Ramirez Sent: Tuesday, August 19, 2008 11:55 PM To: Justin Shore Cc: [email protected] Subject: Re: [c-nsp] Unable to connect VLAN traffic Justin, I appreciate your well explained answer. So basically they would tell me what VLANs I should use for me to match them. Thanks John--- On Tue, 8/19/08, Justin Shore <[EMAIL PROTECTED]> wrote: From: Justin Shore [EMAIL PROTECTED] Subject: Re: [c-nsp] Unable to connect VLAN traffic To: "Johnny Ramirez" <[EMAIL PROTECTED]> Cc: [email protected] Date: Tuesday, August 19, 2008, 9:41 PM Johnny Ramirez wrote: > We have layer 2 connectivity from our main office to an offsite facility where our servers reside. We are connected via fiber but is not a dedicated circuit. > > Recently I created a VLAN with same ID on both switches (main office and Offsite facility) . I trunked the port on both ends but not traffic passes on this VLAN. Obviously only VLAN 1 works. According to a consultant the provider of the fiber connection needs to turn "something" on for us to be able to pass VLAN traffic other than VLAN 1's. What would be that "something", he does not even kow it himself. > > Can anybody shed any light on this?. We are urgently needing to have a separate VLAN for our VOIP traffic. John, Basically what this amounts to is that your transport provider is only accepting untagged Ethernet frames and thus only the one VLAN you previously used on your access interface. You need the provider to accept tagged Ethernet frames so that tagged frames from each of your VLANs will be accepted for transport. The provider may either dictate to you what VLAN IDs you must use. They may use Q-in-Q (aka VLAN stacking) to assign their own tag in front of your tags. This would give you the most flexibility and will keep you from having to work with them to allow future VLANs across the trunk. Justin _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
