Routing Options Question

[Smack2k]

If I have a single managed Switch with some devices setup in VLANs, but also a few that arent in a VLAN (VLAN1 by default I guess, but nothing VLAN configured on their access ports, and I want to get all traffic from the switch up to the Router and then out, what are my options?  Do I need to use two seperate Router Ports, one that will receive all the VLANs traffic and a seperate one that receives the traffic from the devices not in a particular VLAN?  Or can I setup a trunk that will take both types of traffic and if so, how?

[balaji.bandi]

You can make Router as Routing point for your network to go out.

Router---Trunk---Switch ( Create VLAN for the required VLAN)

in the Router create VLAN related IP address. If the router doing NAT, then add those IP address to NAT so user can reach to Internet.

below example guide help you to configure :

https://www.cisco.com/c/en/us/support/docs/lan-switching/inter-vlan-routing/14976-50.html

[Alan Ng'ethe]

Hi!

You may use a router on a stick.

On the interface connecting the router to the switch;

interface <interface id>

switchport mode trunk

switchport trunk allowed vlan all

switchport trunk native vlan 1

In order to allow vlans to traverse the trunk;

interface <interface id>.vlan id--match to vlan id for consistency

encapsulation dot1q vlan_id

ip address <ip address and mask>

Configuring InterVLAN Routing and ISL/802.1Q Trunking

Hosts would then use the router subinterface ip address as their default gateway.

It is possible to use one port per vlan, but in a large network the possibility of running out of phhsical ports on the router is very real and is made even more real because such networks may have a large number of vlans.

[Dennis Mink]

Yes you can use a single port configured as trunk, but try to refrain from using VLAN1 as much as you can

[Mohamed Alhenawy]

Hello Dear, 

You can used that way

interface GigabitEthernet x/x/x
no ip address
!
interface GigabitEthernetx/x/x.10
encapsulation dot1Q 10
ip address x.x.x.x x.x.x.x
!
interface GigabitEthernet x/x/x.20
encapsulation dot1Q 20
ip address x.x.x.x x.x.x.x 
!
interface GigabitEthernet x/x/x.30
encapsulation dot1Q 30
ip address x.x.x.x x.x.x.x 

[Smack2k]

Sorry, replied to wrong post.....

[Joseph W. Doherty · Accepted solution]

Unless your managed switch supports non-VLAN ports (also sometimes called routed ports), all its ports are in a VLAN. You correctly note, by default, such VLAN ports not explicitly defined would be in VLAN 1, which is a VLAN, just like other ports with a VLAN number assigned.

So, getting those ports, from a default VLAN, would be not different from explicitly defined VLAN ports. If you only have one VLAN on the switch, you would configure the port to the router to be in the same VLAN. If you have multiple VLANs, your choices (also described by the other posters) are use a trunk port on the switch (and the "trunk" equivalent on the router port [you use sub interfaces]) to get you desired VLANs to the router or you would need one port on both the router and switch to carry each VLAN on a non-trunk port.

If bandwidth is a concern between the switch and the router, you could have multiple trunk ports between the switch and router (where you decide which ports carry which VLANs) or you might be able to define a logical link, access or trunk, across an Etherchannel port between the switch and router.