VLAN, TRUNKING, VTP

Vlan trunking

-Vlan divides the broadcast domain
-In New switch, Default Vlan = Native Vlan = Vlan 1
-Native Vlan can be changed from Vlan 1 to Vlan10, 20 etc.
-Vlan 1 cannot be deleted even after entering command
-Vlan 1 carries critical traffic like CDP, VTP etc.
-Access port carries traffic of only one vlan
-Trunk port carries traffic of more than one vlan
-Voice vlan can carry traffic of two vlan’s
-Layer 3 vlan required for Inter-Vlan communication
-On Router, For Inter-Vlan comunication, “Router on Stick” is implemented
-On Switches, For Inter-Vlan comunication,”Layer 3 vlan or SVI” is implemented
-To allow end to end communication, we need to allow Vlan on all the trunk ports in between
-Vlan can be created on Router, Switch, Firewall etc.
-Trunking is the process to enable multiple vlan’s traffic between different switches
-Conditions -Connected Port should be trunk, Encapsulation should match, Allowed Vlans on trunk port should be same

VTP key points

-VTP is Virtual Trunking Protocol, configured to manage Vlan’s
-VTP different versions -V1, V2, V3
-In VTP, different switch roles are Server, Client, Transparent, Off Mode
-Default mode of switch is Server mode
-Recommended to add new switch in Client Mode with Revision number=0
-Revision number can be made zero, if VTP domain name is changes to some bogus name
-Revision number can be made zero, if VTP mode is changes to Transparent mode
-Latest Revision number means Latest Vlan configuration
-Server Mode, we can create, modify & delete vlans
-Client Mode, When client gets update, switch will update itself & passes update further
-Client Mode, We cannot do vlan related changes on client mode, switch will give error message
-Transparent Mode, When Transparent gets update, switch will not update itself & passes update further
-Transparent Mode, Changes performed on the Transparent will not be replicated to other switches
-Off Mode, When switch in Off mode gets update, switch will not update itself and do not pass further

VTP -Different versions

V1,V2 : Support upto Vlan number 1001, V3: Support upto Vlan number 4095
V1,V2 : Cannot transfer details of Private Vlans, V3 : Can transfer details of Private vlan as well
V1,V2 : Cannot carry MSTP region information, V3 : Can carry MSTP region information
V1,V2 : There is no option to make multiple Servers as Primary & secondary,
V3 : We can make Primary server out of multiple Server modes available

Comments

CLI Commands for Troubleshooting FortiGate Firewalls

CLI Commands for Troubleshooting FortiGate Firewalls 2015-12-21 Fortinet , Memorandum , Network Cheat Sheet , CLI , FortiGate , Fortinet , Quick Reference , SCP , Troubleshooting Johannes Weber This blog post is a list of common troubleshooting commands I am using on the FortiGate CLI . It is not complete nor very detailled, but provides the basic commands for troubleshooting network related issues that are not resolvable via the GUI. I am not focused on too many memory, process, kernel, etc. details. These must only be used if there are really specific problems. I am more focused on the general troubleshooting stuff. I am using it personally as a cheat sheet / quick reference and will update it from time to time. Coming from Cisco, everything is “show”. With Fortinet you have the choice confusion between show | get | diagnose | execute . Not that easy to remember. It is “ get router info6 routing-table” to show the routing table but “ diagn...

Check Throughput of Interfaces - Palo Alto Networks NGFW

Check Throughput of Interfaces - Palo Alto Networks NGFW Following command shows brief interface throughput. > show system statistics session To see the complete statistics, run the show system state browser command > show system state browser Press Shift+L and click on Ports To enable tracking and updates press Y and U To see additional ports, press space bar

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking The way we do business is changing. As critical business applications migrate to the cloud, and the mobile workforce continues to grow, networking and security solutions need to evolve in order to meet the changing business needs. Gartner believes (and we agree) that the future of networking lies with SASE (Secure Access Service Edge) – the convergence of networking and security into one cloud service. Here’s why. 1990s – 2000s: MPLS and the Era of Clear Network Boundaries? Back in the day, networking models were hardware-centric and manually configured. Applications, data, and services lived within private datacenters and relied on remote access solutions to connect remote workers. Dedicated network connectivity, known as MPLS, was the preferred approach for connecting remote locations. MPLS provides predictable performance, low latency and packet loss, and central management. However, MPLS is ...

Secure IT

Search This Blog