VLAN, Subnet & Routing

This video discussed how VLAN & Routing works.

[@MrKeano4]

Thank you very much, much appreciated. First part was fine as far as RVI, but then in one comment, the first reference to subnets was we have defined these subnets, without ever having mentioned subnet in the entire video previous to this! Was lost after that!

[@IreshDissanayakaM]

I appreciate your efforts a lot because I learned a lot out of this. Thank you!

[@cybersecurityentertainment]

Welcome

[@sweetdivine2701]

Thanks for sharing i arappreciate the video, but really can't and did not get anything, all the number are not on there so is difficult for us newbie to even understand what you are talking about.

[@cybersecurityentertainment]

Vlan number doesn't matter, it's the choice of network engineer, he can choose any b/w 0-4095 (12 bit). What matters is that Ports on the switch with same vlan id communicate with each other & ports with different vlan id requires gateway (RVI) to communicate with each other. For this video, I have used same color for same vlan id.

[@sheh-zoo1974]

Good but would have better if animated

[@udayjkc]

Do we still need trunking after establishing RVI/SVI ?

[@cybersecurityentertainment]

RVI operates at Layer 3 and trunk operates at Layer 2 . Both augment each other for end-end communication. For remote traffic we need RVI. For local traffic we may need trunk if using multiple vlans on single physical link. So flow is like this end point1> Access1>Trunk1> RVI 1> RVI 2> Trunk 2>Access 2>end point 2

[@udayjkc]

@@cybersecurityentertainment Thanks that helps.

[@MBAKB]

RVI 1 on Switch A and Switch B have to be in same IP subnet but have different address with in that subnet .. is this right !

[@cybersecurityentertainment]

RVIs should be in same subnet but each on different device. It is recommended to have single RVI/ip for a vlan on switch/router/firewall which is communicating outside. Rest all local switches should operate L2 vlan traffic (acces/trunk). Because then there is no need of configurating routes on L2 switches. It also provide device security if u configure RVI on local firewall only which can block ssh/telnet to RVI from endpoints.

[@cybersecurityentertainment]

If u configure an access port in vlan X on Switch A and then do same on Switch B. Then connect both ports of these two different switches. All devices on Vlan X will communicate on these two different switches. So I don't need trunking for that. We use trunking once we want to use single port on a switch to carry multiple vlans. RVI is a gateway IP, incase a vlan wants to communicate outside, even to another Vlan which has its own RVI. U can have multiple RVIs for a vlan but each RVI has to be on different L3 switch. However you can have multiple RVIs on single L3 switch but each RVI to be associated with different Vlan.