Re: DNS replication on 2 domain on 2 forests
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Tue, 12 Dec 2006 15:49:14 GMT
However, as far as routed or switched,
They are neither mutually exclusive nor synonymous,
as switches can either router or bridge (or as devices
perform a combination of both.)
...like I said, hate to use the term because of the confusion
The correct approach is neither to "hate the term" nor
to avoid it, but rather to just use and explain it correctly.
This stuff isn't actually hard, but has just been explained
badly by so many people and so many books that beginners
have been confused by the so-called experts.
but I do want to point out that it is actually controlling the traffic by
directing it between the ports in question based on source and destination
MAC switch ports.
Then that is bridging -- or level 2 -- decision making.
Routers work at the network protocol (level 3) level to
make their decisions. (And they join multiple "broadcast
domains.")
Bridging alone implies it is connecting only two segments,
No, bridging is a connection between multiple "collision
domains" (which we casually refer to as segments).
There is NO implication of "only two" segments in bridges;
single bridges have historically connected many segments.
where a switch has mutliple segments, therefore it is essentially a
multi-port bridge, so, yes it does bridging functions, but on multiple
ports. T
Your main problem here seems to be that you really
misunderstand the KEY points of bridging and routing
and how they differ -- arguing from ignorance is not
going to make your initial mistakes go away. Only learning
the difference and how to explain it to those who come
looking to you for help will do that.
therefore it 'switches' traffic between the appropriate ports based on
source and destination MACs.
Again, SOME switches use ROUTING mechanisms to make
such switching decisions -- others use bridging mechanisms
to make these decisions when switching between two OR
MORE collision domains.
If you will just FIRST learn the differences (and similarities)
between bridging and routing you will be much better prepared
to both understand what switching really is -- and is not -- and
to explain all of this to those who seek your help.
You cannot "make yourself right" by continuing to try to explain
away your basic mistakes -- only by adopting both the correct
terminology and keying in on the key concepts will your
overcome these problem, learn, and best help others.
BTW: The MOST important difference for network admins
is that: Bridges propagate broadcasts, while Routers block*
broadcasts.
* Technically, routers don't "block" broadcasts, they just
ignore them, but the best mental picture is to treat routers
as BARRIERS to the propagation of broadcasts. This is
both a good (isolation) and a bad (steps must be taken when
broadcasts traffic or results are important) feature.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
"Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx> wrote in message
news:%23Q4eHjbHHHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
In news:O1arcHLHHHA.1252@xxxxxxxxxxxxxxxxxxxx,
Herb Martin <news@xxxxxxxxxxxxxx> stated, which I commented on below:
I did mention that I didn't like to use the word "routing" when it
comes to switched ports, but essentially
And since you both "don't like" it and it is wrong and confusing
it is best not to use the wrong word at all on a subject that
is difficult for most people to understand without first getting
at least the vocabulary correct.
Also, I didn't want to complicate it anymore by introducing layer 3
switches.
Then don't, but then avoid the word routing and stick with
the correct terms: Bridge and bridging.
For the poster, I thought to simplify it and not yet introduce Layer 3
switches, but glad YOU brought it up for him and explained it, so you get
the credit.
However, as far as routed or switched, like I said, hate to use the term
because of the confusion but I do want to point out that it is actually
controlling the traffic by directing it between the ports in question
based on source and destination MAC switch ports. Bridging alone implies
it is connecting only two segments, where a switch has mutliple segments,
therefore it is essentially a multi-port bridge, so, yes it does bridging
functions, but on multiple ports. Therefore it 'switches' traffic between
the appropriate ports based on source and destination MACs.
Bitzenbytes.com - Hub vs. Switch
A switch, in common parlance, is a multi-port bridge. That said, an
overloaded switch can stop traffic just like having no switch. Not that
the typical home ...
http://www.bitzenbytes.com/Content-Arcanum-18-1-33.html
LAN Switching
A Layer 2 LAN switch is operationally similar to a multiport bridge
but has a much higher capacity and supports many new features, such as
full-duplex ...
http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/lanswtch.htm
multiport bridge definition of multiport bridge in computing ...A
bridge with more than two ports. There is little difference between a
multiport bridge and a switch, such as used to switch Ethernet packets,
...
http://computing-dictionary.thefreedictionary.com/multiport+bridge
At the point where you have to deal with this then you must
distinguish layer 3 and layer 2 devices, or functionality within
a single physical device, by using the correct terms.
Generally, it is best to first explain these differences as
separate components, and then (only then) explain that
some switches are bridges, others are routers, and the
most sophisticated are hybrids that allow the administrator
to selectively configure both of these behaviors.
And yes, he needs an IP router, or a Layer 3 Switch. Of course it
depends on what he has to spend. Layer 3 switches are NOT cheap.
Actually he needs to CONFIGURE ROUTING -- but that
could be on a switch, a (pure) router, or even an ALL of
the individual workstations by using explicit manual routes.
The entire discussion of "switches" is largely a distraction
when the ISSUE is routing, but not even necessarily a
"router".
It's a matter of understanding these items at the basic level,
and then keeping it as simple as possible -- but no simpler.
And yes, his problem is routing. Therefore he needs a ROUTER, as already
indicated.
Ace
.
- Follow-Ups:
- Re: DNS replication on 2 domain on 2 forests
- From: Ace Fekay [MVP]
- Re: DNS replication on 2 domain on 2 forests
- References:
- DNS replication on 2 domain on 2 forests
- From: Nico2005
- Re: DNS replication on 2 domain on 2 forests
- From: Kevin D. Goodknecht Sr. [MVP]
- Re: DNS replication on 2 domain on 2 forests
- From: Herb Martin
- Re: DNS replication on 2 domain on 2 forests
- From: Nico2005
- Re: DNS replication on 2 domain on 2 forests
- From: Ace Fekay [MVP]
- Re: DNS replication on 2 domain on 2 forests
- From: Herb Martin
- Re: DNS replication on 2 domain on 2 forests
- From: Ace Fekay [MVP]
- Re: DNS replication on 2 domain on 2 forests
- From: Herb Martin
- Re: DNS replication on 2 domain on 2 forests
- From: Ace Fekay [MVP]
- DNS replication on 2 domain on 2 forests
- Prev by Date: Re: Is this a split / shadow situation resolving non routable IPs without DNS authourity.
- Next by Date: DnsModifyRecordsInSet returns error 9002
- Previous by thread: Re: DNS replication on 2 domain on 2 forests
- Next by thread: Re: DNS replication on 2 domain on 2 forests
- Index(es):
Relevant Pages
|