Scribd
Upload
4 views8 pages

Network Troubleshooting for MLS B Issues

The document outlines network troubleshooting for communication issues between MLS A and MLS B, detailing the network topology and identified problems such as misconfigured routes and VLAN accessibility. It provides specific fixes for routing, VLAN, and trunking configurations, including adding static routes and ensuring proper trunking settings. Verification steps are also included to test connectivity and address common questions related to the issues encountered.

Uploaded by

Nicholas Kayode
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
4 views8 pages

Network Troubleshooting for MLS B Issues

The document outlines network troubleshooting for communication issues between MLS A and MLS B, detailing the network topology and identified problems such as misconfigured routes and VLAN accessibility. It provides specific fixes for routing, VLAN, and trunking configurations, including adding static routes and ensuring proper trunking settings. Verification steps are also included to test connectivity and address common questions related to the issues encountered.

Uploaded by

Nicholas Kayode
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

Network Troubleshooting & Fixes

Resolving MLS B Communication


Issues
Network Topology Overview
• • Devices: MLS A, MLS B, Router A, Router B
• • VLANs configured on MLS A
• • Routing between MLS A & MLS B via Router
B
• • IP Addressing and Trunking
• • Identified Issues: MLS B could not reach MLS
A or VLANs
Identified Issues
• 1. MLS B could not ping MLS A or its VLANs
• 2. Router B could only partially communicate
with MLS A
• 3. VLANs on MLS A were not accessible from
MLS B
• 4. Misconfigured routes and trunking settings
Fixes: Routing Issues
• • Add static routes on Router B:
• ip route [Link] [Link]
[Link]

• • Add static route on MLS B:


• ip route [Link] [Link]
[Link]

• • Ensure Router A forwards MLS B traffic:


Fixes: VLAN & Trunking
Configuration
• • Ensure Trunking on MLS A & MLS B:
• interface FastEthernet0/24
• switchport mode trunk
• switchport trunk allowed vlan all
• no shutdown

• • Check VLAN Configurations:


• show vlan brief
Fixes: Default Gateway Verification
• • VLANs on MLS A should have a proper
default gateway
• • Example:
• VLAN 10 ([Link]/24) → Default
Gateway: [Link]
• • Ensure MLS A and MLS B have correct
routing back
Verification & Testing
• • On MLS B:
• ping [Link]
• ping 192.168.x.x (VLANs in MLS A)

• • On Router B:
• ping [Link]
• ping MLS A’s VLANs

• • On MLS A:
Likely Questions & Answers
• Q1: Why did MLS B fail to communicate with
MLS A?
• A: No proper routing from MLS B to MLS A;
static routes were needed.

• Q2: Why was VLAN communication broken?


• A: Missing trunk configuration between MLS A
& MLS B.

You might also like