Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

simple ethernet question.

Hi,

I have a confusion if the statement below is true ?

"If a hub is connected to port 0/1, and a

workstation connected to the hub transmits a packets to another workstation connected to the hub, port 0/1 will not forward this packet anywhere

because the destination MAC resides

on the same port. "

reference doc :

http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a008015bfd6.shtml

  • LAN Switching and Routing
3 REPLIES
Purple

Re: simple ethernet question.

Hi,

That is perfectly correct behaviour and is considered the process of "filtering" in bridging/switching terminology. Consider the following example: you have an ethernet hub connected to port 0/1 of a switch. There are two devices on the hub, with MAC addresses A and B. If A sends a frame to packet B, then the hub will forward that frame to all other ports on the hub (which is how hubs work), which means it will get to B. It will also reach the switch on port 0/1. There is no need for the switch to forward the frame anywhere since B has already received it.

Paresh.

PS> Pls do remember to rate posts

New Member

Re: simple ethernet question.

thanks , actually I got confused with the statement, yes ur right, I remember it.

New Member

Re: simple ethernet question.

Hi,

This is a fairly old issue but could not help knowing how the switch would know that the B wiil receive the frame. Only way switch would know is to check its CAM to see whether the B is in the CAM. Will the switch has a list of all the MACs of devices attached to the HUB. Is so how would it(switch) learn/build its CAM to include those addresses.

Thsnks

Sunil

125
Views
18
Helpful
3
Replies
This widget could not be displayed.