Solved

Issue trunking VLANs between AdTran Netvanta 1234 Layer 2 switch and Cisco Small Business SG300-52P switch

Posted on 2014-04-06
1
2,457 Views
Last Modified: 2014-04-30
Hello,

I have an existing, older layer 2 AdTran Netvanta 1234 switch that I am trying to trunk into a new Cisco Small Business SG300-52P switch.

It should be a standard operation as the setup is not very complicated:

DATA:  VLAN1
Voice: VLAN3
Edge:  VLAN4

The EDGE network is the ISP...we have it setup this way because a few devices need to be plugged into the edge with public IP addresses.

I am trying to trunk this setup to a Cisco Small Business SG300-52P switch.  No matter what I do, when I trunk, things will not work correctly between the switches.

The SG300-52P switch is setup in Layer-3 mode, and I am trying to get the switch to do routing between the VLAN's.  Anything plugged into the Cisco switch works exactly as expected, but anything in the AdTran does not work, and the trunks don't seem to line up.

- I've created the same VLAN's in the Cisco
- I've named them the same as well (although this shouldn't matter)
- I'm uplinking with a single GIG port setup as a trunk
- I've set the allowed VLAN's to ALL

On Cisco Catalyst switches, I usually have to specify the trunk protocol (802.1q) but on the SG300-52P switch, this command is not an option, and the GUI does not seem to have a corresponding option as well.  There is the standard PVID (Native VLAN), trunk vs access, and trunk membership...everything seems to be lined up correctly with the trunk port as a member of ALL VLAN's, and I've tried with and without a NATIVE VLAN set (native VLAN set to DATA when it was set).

Can anyone give any insight into this issue?

Note:  The AdTran later 2 DOES have a VLAN setup for each VLAN as well, and there is no VLAN setup that does not exist in both switches.
0
Comment
Question by:jkeegan123
1 Comment
 
LVL 5

Accepted Solution

by:
jkeegan123 earned 0 total points
ID: 40032810
Issue is that data vlan was vlan 1, which is the default VLAN.

- Created VLAN 200 (not used for anything)
- Set uplink port to TRUNK
- Set all VLAN's to TAG (switchport trunk allow vlan add all)
- Set native VLAN to 200

Default VLAN (native VLAN) will NOT tag, as that is the point of the native VLAN...it is the VLAN that all traffic defaults to if the traffic is NOT tagged.  

I set the upstream switch to the same settings, and everything is resolved.
0

Featured Post

Easy, flexible multimedia distribution & control

Coming soon!  Ideal for large-scale A/V applications, ATEN's VM3200 Modular Matrix Switch is an all-in-one solution that simplifies video wall integration. Easily customize display layouts to see what you want, how you want it in 4k.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
How to choose hardware firewall 5 60
VIRL IP adress 3 79
Can't ping New Linux Servers 40 89
Patch panel 7 48
AWS has developed and created its highly available global infrastructure allowing users to deploy and manage their estates all across the world through the use of the following geographical components   RegionsAvailability ZonesEdge Locations  Wh…
Creating an OSPF network that automatically (dynamically) reroutes network traffic over other connections to prevent network downtime.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

791 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question