VLAN Setup First Time Help Needed!!!!

Small Network in my home using Cisco SG 200-18 also have Meraki MX60 Router.

2  of my Windows 2008 Server have Dual network adapters.

Need to put the second network adapter on another subnet.

My primary network is 10.2.8.x/22  10.2.8.1 is Gateway 255.255.252.0 is the subnet

New network is 10.1.8.x/22 Gateway is 10.1.8.1 Subnet 255.255.252.0

I need both networks to be able to talk to each other.

On one server I have both network adapters configured properly

My Meraki MX60 is configured with a VLAN of 1018 MXIP 10.1.8.1 one LAN port on the Meraki MX60 we tested and made it on the new VLAN

If I plug the second network adapter from my test server into the Meraki MX60 Lan Port and  it all works from my pc on 10.2.1.x I can ping 10.1.8.1 which is the Meraki MX60 and I can ping 10.1.8.23 which is the test server.
My PC (10.2.8.99) can ping 10.1.8.23 also

 
Now for my Question

When I plug my Test Server second network adapter into port 13, 14 15 or 16 of the SG 200 I can not:

1. from my pc (10.2.8.99) ping 10.1.8.23

2. From the Meraki (10.2.8.1) I can not ping 10.1.8.23

3. From the Test server (10.1.8.23) can not ping 10.1.8.1

How do I configure the SG200 correctly?

I created a VLAN named 1018 (See the attached screen images)

How does my config look?

What am I missing????


Thanks in advance
SG-VLAN-Create-VLAN.png
SG-VLAN-Interface-Settings.png
SG-VLAN-Port-to-VLAN-1.png
SG-VLAN-Port-to-VLAN-1018.png
SG-VLAN-Port-VLAN-Membership.png
LVL 23
Thomas GrassiSystems AdministratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Fred MarshallPrincipalCommented:
First, I think I would try to keep things as simple as possible.  You should only need tagging if you expect the VLANs to work through cascaded devices with trunking.  I'm not sure you need that.

In my simple mind, it's best to think of a VLAN as a separate copper LAN.  It's "Virtual" because switches and routers maintain the separation between ports internally.  You can think of the switches (the router has a "switch" inside) as separate physically but built into the same box and having distinct/separate Ethernet ports.

So, keeping things simple, I would plug an Ethernet cable from each separate LAN / VLAN from the router and into matching switch ports.
There may be a way to do this more elegantly with one cable between the router and the switch but this is *simple*.

Then, I would plug .... whatever ... into the remaining switch ports according to which VLAN they will belong.

Since the interactions seem to be working just fine within the router, this would be a simple extension of that implementation.

I didn't see where you'd connected the Meraki VLANs to the switch VLANs....
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Thomas GrassiSystems AdministratorAuthor Commented:
Fred

KISS method is the best.

I plugged a cat 6 cable into the LAN Port on My Meraki MX 60 that was Tagged for VLAN 1018 into my Cisco SG 200 smart switch port 16 which is tag for VLAN 1018

The I plugged my Test Server into Port 17 on the Cisco SG 200 smart Switch
and it is working like a champ.

That was it my configuration was correct just needed a network cable in the switch from the router.

Just think of the Vlan as another switch that makes it very clear.


Thanks
0
Netman66Commented:
This is pretty simple.

You need to create the new vlans on each device.
You need to tag this vlan on the same ports connecting your router and switch.
You need to add access ports into this new vlan (these are untagged)
Then you need a layer 3 interface for this new vlan on the router.

To make them route without a routing protocol, you add static routes between each network on the router.
0
What were the top attacks of Q1 2018?

The Threat Lab team analyzes data from WatchGuard’s Firebox Feed, internal and partner threat intelligence, and a research honeynet, to provide insightful analysis about the top threats on the Internet. Check out our Q1 2018 report for smart, practical security advice today!

Netman66Commented:
I had a look at the files you attached and only ports that carry one or more vlans between devices (switches or routers) need to be a trunk.  

Ports where end device connect are untagged in the vlan you want them in.  Only the link from your switch to the router needs to be a trunk for vlan 1, 15 and 1018 (tagged) - I'm not sure you can remove vlan 1 from these switches so it's likely going to have to stay.

If you have a way to backup the config to text and post that, we could mod it for you to restore.
0
Thomas GrassiSystems AdministratorAuthor Commented:
Netman66

So let me see if I understand your posts

1. Only Ports 1 & 13 should be Trunk and Untagged
2. All other ports Access
3. Port 1 and 15 to be tagged for both vlan 1 and vlan 1018

I can not save the configuration to a txt file

I tried to change one of the ports to access mode but it failed

Port gi14: Default Vlan Tagged prevents executing Access Mode.

This happens to only the ports I tagged to vlan 1018

Thoughts
0
Netman66Commented:
Close.  You only need one connection between the switch and router.

This connection is a trunk (tagged port) passing vlans you want.

Each client port should be a member of the appropriate vlan for your needs.  These are untagged (access) ports.

You probably need to untag (un-trunk) all the ports before you change things. I'm not a fan of those business switches due to the crazy UI.  I prefer the CLI so I can do what I need without trying to understand what the UI is showing - which isn't all that intuitive.

You may be able to use Putty and access the console or telnet to copy the config from the console to attach here.
0
Fred MarshallPrincipalCommented:
It sounds like you have it working with 2 cables between the router and the switch.  That's good!

Obviously, in some situations, it's "neater" to have but one cable.
As you can see, that can be done if you want to move forward to a more elegant solution.
0
Netman66Commented:
It can work with 2 cables but you would have to isolate vlan traffic on each or you create a loop that spanning-tree will block.
0
Thomas GrassiSystems AdministratorAuthor Commented:
Thanks Guys

All working

Was able to setup each port on it proper vlan with Access not trunk

Have two ports 1 and 13 as trunk  port 1 used for vlan 1 and port 13 used for vlan 1018

Ports 14 thru 18 are on vlan 1018 only now

I can communicate across both subnets (vlans) in both directions.

This is great.

Have cables on order hope they get here soon so I can plug the other servers into the newly created vlan.


Thanks again for all your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking Hardware-Other

From novice to tech pro — start learning today.

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.