Assuming you are utilizing a heritage Inter-VLAN steering, guarantee that switch ports associate with the switch connection point ought to be arranged in the right VLAN. This is an exceptionally normal issue with a switch port and required investigating. On the off chance that a switch port isn’t arranged to address VLAN, the gadgets on that VLAN can’t impart outside its VLAN.
The figures underneath outline the switch port miss designs. Figure 1 shows that have 1 is associated with switch0 port F0/1 which is the piece of VLAN 100, and switch port F0/2 is associated with Router interface F0/0, and the switch F0/2 isn’t the piece of VLAN-100.
Have 2 is associated with F0/6, and the Router0 interface F0/1 is associated with F0/10, the two F0/6 and F0/10 is essential for VLAN 200. So host0 can send information up to the switch, yet the switch can’t advance the information to have 1, in light of the fact that VLAN 100 isn’t actually associated with Router0. To determine this issue do the accompanying on switch0.
Swithc>enable
Swithc#configure terminal
Switch(config)#interface FastEthernet 0/2
Switch(config-if)#switchport access vlan 100
Switch(config-if)#exit
Switch(config)#exit
Switch# compose
Figure 2 likewise shows the issue with the switch port, where the switch ports are appropriately arranged. In any case, we simply associate some unacceptable switch port with some unacceptable point of interaction of the switch.
The figures show that F0/2 is the piece of VLAN 200, and interface F0/1 is arranged for VLAN 200, however all things considered, we associate switch port F0/2 with switch interface F0/1. So we likewise wrongly associate the Switch port F0/2 rather than switch port F0/10. So both can’t send their information to Router0. To address this issue, simply associate F0/10 with switch interface F0/1 and F0/2 with Router interface F0/0.
The geography in Figure 3 shows the switch on-a-stick steering model. Yet, the port associated with the switch isn’t designed as a trunk. The port associated with the switch for the traffic of different VLANs should be designed as a trunk.
In any case, G0/1 on switch0 isn’t designed as a trunk and it is in the default VLAN. So the switch can’t course between VLANs in light of the fact that every one of its designed subinterfaces can’t send or get VLAN-labeled traffic. To determine this issue arrange G0/1 as a trunk.
Swithc>enable
Swithc#configure terminal
Switch(config)#interface G0/1
Switch(config-if)#switchport mode trunk
Switch(config-if)#exit
Switch(config)#exit
Switch# compose
At the point when the storage compartment is really settled, gadgets associated with every one of the VLANs can speak with the subinterface appointed to their VLAN, accordingly empowering between VLAN directing.
The geography in Figure 3 shows the storage compartment connect between Switch is designed yet is going down may because of a link or perhaps because of the Router point of interaction is closed down. So there are no excess associations or ways between these gadgets, So all VLANs can’t speak with one another.
Confirm Switch Configuration
We can confirm the switch setup when an issue happens. To check the design we can utilize different confirmation orders to inspect the arrangement and recognize the issue.
These check orders I have as of now clarified in the article Common Show Command – Cisco IOs, so follow these orders for confirmation. We can utilize the show interfaces interface-id switchport to actually look at the port VLAN enrollment. We can likewise utilize show running-config order to check the switch port mode.
Investigating Inter-VLAN Interface Issues
The most well-known points of interaction issue utilizing inheritance between VLAN steering is to associate the actual switch point of interaction to some unacceptable switch port. Associating the switch interface in the wrong VLAN the traffic to arrive at the switch and to advance them to other VLANs.
This is a similar issue as I examined in the switch port issue, to address this issue no further arrangement and testing are required. It just necessities to put the links accurately.
Check Router Configuration – Interface Issues
The setup of the Sub-connect with some unacceptable VLAN ID is one of the most widely recognized issues in the switch on-a-stick design. We can check interface issues utilizing show orders.
The <show interfaces> and just the <show running-config> orders are helpful in investigating between VLAN directing issues. The figure underneath delineates the <show interfaces> order yield. The order creates a ton of result for all interfaces be that as it may, you want to look for your expected point of interaction and required line as displayed in the figure.
We can simply enter the order utilizing the connection point ID like <show interfaces fastEthernet 0/0.100>. Figure 2 represents the result of an order utilizing point of interaction ID.
We likewise utilize the <show running-config> order to check and confirm the point of interaction issues. The figure beneath shows the result of <show running-config> order. We can undoubtedly track down the expected data under the connection point FastEthernet 0/0.100.
Thus, in the event that we found the inaccurate VLAN task into sub interface, we can address this issue, to re-design the subinterface into the right VLAN utilizing the <encapsulation dot1q VLAN ID> in subinterface setup mode. We can resolve the issue by legitimate confirmation rapidly and permitting between VLAN steering to work appropriately.
IP Addresses and Subnet Masks Errors
Each VLANs required interesting subnets on the organization. Each VLAN should be associated with the switch for between VLAN steering. The VLANs can associate with the switch by utilizing actual points of interaction or subinterfaces. Thus, every connection point or subinterface should be arranged with a special IP address of that subnet allocated to the VLAN.
This makes it conceivable that the gadgets on the VLAN to speak with the switch interface. The point of interaction empowers the steering of traffic to other VLANs associated with the switch. The normal issues of IP tending to mistakes are the accompanying:
The switch interface and subinterface have been arranged with an erroneous IP address. The wrong IP address on the connection point forestalls the VLAN has from having the option to speak with the switch. Relegate the right IP address to the switch interface utilizing the order <ip address IP ADDRESS SUBNET MASK>. After the adjustment of the IP address, the hosts on the comparing VLAN can speak with the switch.
A few hosts on the VLAN can’t convey to the switch, confirm their IP addresses. On the off chance that the IP address is erroneous as per the subnet saved and as per the location of the point of interaction or subinterface, the hosts can’t impart. Allot the right IP address has on the VLAN.
Confirming IP Address and Subnet Mask Configuration Issues
We can without much of a stretch confirm the IP address setup for the switch interface or subinterface utilizing the show orders. The figure beneath delineates the result of <show ip interface brief> order. You can see the IP address allocated to every communicate and subinterface here. The <show running-config> order can likewise show the IP addresses alloted to the connection point or subinterface. For reference see figure 2 above. Now and again the IP address arrangement of the host side is inaccurate. For this, you ought to check the arrangement by utilizing the <ip config/all> order in the order brief of the working framework.
