Ronneil Camara wrote:
> First of all, latency are common problems with switches. When switches are
> turned on, it goes into three levels, listening, learning, then forwarding.
> These includes learning the MAC address and putting it on the CAM and IP
> address if it supports VLAN. Let say a machine is up and running but not
> connected to the switch, if you connect this machine to the switch, it will
> not immediately be able to ping anyone. It must go through the above process
> which takes 30 to 45 seconds.
yes thats true but you can still configure that to a lower value.
> Remember, 10BaseT mode will not be able to talk to a
> 100BaseT mode.
a mix of 10mpbs, 100mpbs or 1gigabit, yes it can. its the switch job to communicate
mix port pipe. the bottleneck there is at the smaller pipes port when a big pipes
suddenly burst a big data to that smaller pipe or the summation of smaller pipes
burst at the same time is greater than the big pipe bandwidth. this is mostly true
for a udp packets but not in the tcp packets because of tcp congestion control.
> Check also the setting
> of the port on the switch, if a machine is connected directly to the switch
> port, the setting shouldn't be STP (Spanning Tree Protocol), but if a hub is
> connected to it, then it should be STP.
>
actually STP wont harm your network even if you dont have a hub or other bridge
connecting to it.
fooler.
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
