Question

In: Computer Science

A student implemented scenario A simulation. However, testing intra-VLANS using ping commands did not work. Why...

A student implemented scenario A simulation. However, testing intra-VLANS using ping commands did not work. Why a ping might fail? (choose all answers which apply)

Incomplete ports configurations as tranks

Bandwidth limitations on Trunks

Missed VLAN ID in the list of allowed VLANS on a trunk link

Using apple computers instead of Microsoft as hosts

Incorrect Ip assighment for hosts in same VLANs

Not using the latest host operating system update

Solutions

Expert Solution

Answer:-

Suppose Testing connectivity using the ping command should reveal that PC A cannot ping PC B.

The first step is to configure the switch ports to access the specified VLAN, fa0/1 to VLAN 20, and fa0/2 to VLAN 30.

This is the only configuration on the switch, once this is done save the configuration and move on to the router.

On R1, we need to configure its interfaces with the default gateways corresponding to the VLANs. That is; on fa0/0 -192.168.20.1/24 and on fa0/1 – 192.168.30.1/24.

With this configuration, we should save and test for connectivity on PC A and PC B, by using the ping command, and the results should be successful. Examining the routing table of R1 should show us the two routes. This confirms that the router knows of the two VLANs and therefore traffic can flow between them.

so the possibilities that the ping command is not working can be:-

1) Incomplete ports configurations as tranks.

2) Incorrect Ip assighment for hosts in same VLANs.

This is what i think in your case can be possible.

Thanks. do upvote

Have a nice day.


Related Solutions

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT