• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 354
  • Last Modified:

VLAN Tagging Problems

I have an Edgemarc 4550 Configured for VLAN 30 going into a plain POE switch.   Attached to the same switch is an Aastra 6757i set for VLAN 30.   Even after assigning astatic IP address to the Aastra they do not appear to communicate.  

Is it possible that these devices are not compatible?  Am I missing something?
  • 2
2 Solutions
What type of PoE switch?  You need a managed switch otherwise your switch may drop the frames it doesn't understand or it may pass them through even though it does not understand the tag.
How is the connections configured between the switches? Are you trunking or just have vlan 30 on the connection? If you are not trunking and only using vlan 30 between them, then you are not tagging anything and tagging is not necessary,

The poe switch should just pass the traffic. When you say they can't communicate, are you referring to a vlan30 layer 3 interface on the switches?
kdubendorfAuthor Commented:
This is a simple network.  I am hoping to put put voice and data traffic on every drop and have my Dell PowerConnect 3524p switch (the only switch in the network) be able to recognize the difference in traffic and switch it appropriately.     I have an Edgemarc 4550 router.  Port 3 of that router is set for, serves as a DHCP server, and is set to VLAN30 with 802.1q tagging.  I am using Aastra 6757i phones and have enabled them for VLAN and have the phone traffice going out on VLAN30.  

When I wrote this question I have a unmanged Netgear POE switch in place and things weren't working.  I used the Netgear since I wasn't convinced that the Dell was configured properly.

Since this I have removed the Netgear switch and have a phone (with power adaptor) plugged directly into the Edgemarc.   They still won't talk.   The only way for me to get them to communicate is to turn off VLAN on the phone and tag switch port 3 of the Edgemarc to 802.1.

I'm not sure why VLAN will not work here.
kdubendorfAuthor Commented:
The unmanaged switch seemed to be the problem.   I configured the switch to handle VLAN 30 and untagged data traffic and things are working correctly now.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now