vlan tagging port seup / T1 link

[Anonymous]

I have a application where I would like to use vlan tagging opposed to port based vlan. I have the primary data vlan and a voip vlan. The phones support vlan tagging, and the second port of the phones can also be setup to what vlan to be on. My question is to support this, what do I set the ports to? Trunk? or is there a way to say they are on vlan 1 by default and would acknowledge the packets that are on vlan 2? Also if I set the ports to Trunk and they are connected to a normal device like a printer or computer, will it behave like a normal port without vlan tagging on the default vlan? Do you have a article on this?

Also same customer but different question, I have two 1335's, is there a article on how to set those up in bridge mode across a T1? Basically I have one at a main location and one in a different location connected via a T1 and I need them to look like they are on the same network. (and actually the far end one only needs access to one vlan instead of all of them, but it needs to see that vlan like it is local, broadcast and all)

Thanks! - Jeremy

[Anonymous · Accepted solution]

Hi Jeremy:

If your IP phones support LLDP-MED, this is your best bet.  Check out the application note for configuration examples and in-depth info.  Basically, you setup the feature on each switchport and a special VoIP-phone beacon is periodically sent out.  When you connect an compatible IP phone, it detects the LLDP-MED beacon and self-configures to tag its own traffic with the VLAN number specified.  There is no need to configure these switchports as trunks.  LLDP-MED will automatically support 802.1Q VLAN trunk per port as phones come online.  Data to/from devices connected to phone switches (pass through) will be un-tagged (default VLAN).

If your phones do not support LLDP-MED, I think the next-best choice would be to configure each switchport to be an 802.1Q trunk.  In this scenario, you would need to configure your phones for the intended VLAN (tagging for self-sourced traffic).

There may be more than one way to handle the bridge over T1 for your 1335s.  Generally, a routed WAN link is preferred to avoid broadcast traffic congesting low-bandwidth links.  For this reason, it may be most desirable to setup your WAN to connect routed segments as normal (not wide-open bridge) and then leverage the Integrated Routing and Bridging (IRB) featue of AOS to select which traffic is routed and which is bridged.  Guide:   It's a hybrid approach that provides more granular control and improved broadcast domain boundary.  That same guide covers legacy bridging too, if you think that would better fit your application.

Best,

Chris

[Anonymous]

Thank you, that was very helpful. - Jeremy

[Anonymous]

kb9mfd:

I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post to unmark it and select another in its place with the applicable buttons.  If you have any additional information on this that others may benefit from, please come back to this post to provide an update.  If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

Thanks,