Solved

A Question

Posted on 2004-10-15
6
286 Views
Last Modified: 2010-04-10
Hi,
What is the different between Failure domain and BroadCast Domain ?
I know it happend on layer 2 but what is the diffrences beteen these two
domains?


Regards
0
Comment
Question by:gomrok
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 3

Expert Comment

by:_Jochen_
ID: 12318112
hi,
failure domain :
 
Area in which a failure occurred in a Token Ring, defined by the information contained in a beacon. When a station detects a serious problem with the network (such as a cable break), it sends a beacon frame that includes the station reporting the failure, its NAUN, and everything in between. Beaconing in turn initiates a process called autoreconfiguration.  


broadcast domain:
 
 Set of all devices that receive broadcast frames originating from any device within the set. Broadcast domains typically are bounded by routers because routers do not forward broadcast frames.  

hope it helps.
jo
0
 

Author Comment

by:gomrok
ID: 12322655
dont Existed Failure domain On star Topology?
if Yes how Network(hub or switches) behave on this state.
0
 
LVL 3

Accepted Solution

by:
_Jochen_ earned 50 total points
ID: 12326283
yes it could exist on other topologies too. I´ve found another article wich maybe help you:

Failure Domain
A Layer-2 switched domain is considered to be a failure domain because a misconfigured or malfunctioning workstation can introduce errors that impact or disable the entire domain. For example, a jabbering network interface card (NIC) might flood the entire domain with broadcasts or undesirable frames at a very high rate. A protocol malfunction (for example, spanning-tree error or misconfiguration) can inhibit a large part of the network. Problems of this nature can be very difficult to localize in a flat, switched Ethernet environment. Therefore, care must be taken in terms of how this type of network is deployed.

In this model, it is strongly recommended that each enterprise customer be mapped to a virtual LAN (VLAN). This set-up affords the service provider the ability to segment the network by customer. Although it could be possible to have multiple enterprise customers per VLAN, this set-up is considered undesirable for numerous reasons. First, an unexpected broadcast storm in one customer's network could affect the performance of the other customers on that VLAN. Second, and perhaps more important, the customers will have the ability to "sniff" the other customers' traffic, providing for massive security breaches. Finally, because of the inherent ability to sniff Ethernet traffic on the wire, a malicious individual could cause significant damage to multiple customers' networks. This scenario could potentially leave the service provider open to violations in its SLAs to its customers, to say nothing of a poor customer-service situation.

Service providers can take many steps to limit the failure domain per VLAN. First, service providers can limit the number of switches that are participating in that VLAN. Cisco's VLAN trunking protocol (VTP) can enable every switch in the network to be aware of a new VLAN in the network and to autoconfigure trunk ports and spanning trees. In an enterprise network, this feature can be very helpful, but it can be highly detrimental in a service provider's Layer-2 network. Therefore, VTP should be disabled and VLANs manually configured as needed per switch. Secondly, Cisco technology can specify VLANs that are enabled on the 802.1Q trunk links. Only the VLANs of interest should be configured on a trunk link. Finally, the topology of the network should be well known and mapped out, both generally and specifically, per VLAN. This scenario allows the service provider to better isolate potential network faults.

0
Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

 

Author Comment

by:gomrok
ID: 12333763
>>A Layer-2 switched domain is considered to be a failure domain because a misconfigured or malfunctioning workstation can <<
Can you Bring me a Example about Misconfiguring that Caused Failure Domain?
0
 

Author Comment

by:gomrok
ID: 12333777
Another Thing :
is there any difference between Failure domain and Broadcast Domain From propagating
on Networks?
0
 
LVL 3

Assisted Solution

by:_Jochen_
_Jochen_ earned 50 total points
ID: 12339981
First question: >>A Layer-2 switched domain is considered to be a failure domain because a misconfigured or malfunctioning workstation can <<
Can you Bring me a Example about Misconfiguring that Caused Failure Domain?
 --> like described i the article above:
A jabbering network interface card (NIC) might flood the entire domain with broadcasts or undesirable frames at a very high rate. A protocol malfunction (for example, spanning-tree error or misconfiguration) can inhibit a large part of the network.

Second question: is there any difference between Failure domain and Broadcast Domain From propagating on Networks?
The faile Domain is the Area in which a failure occurs. The dimension of the failure depends on the type of the Failure. If you have a NIC which broadcasts into the net in very short intervals, then the Failure Domain is the same like the broadcst domain.
A broadcast domain is bordered by routers (normally). In other words it´s the part of the network (segment) in which a Broadcast (for example an ARP-Broadcast) can flood the network.

--> in some cases Failure Domain have the same dimension like the brodcast domain, but the Failure domain depends on a network error and the broadcast doamin depends on normal working network.

hope that helps you.
0

Featured Post

Turn Insights into Action

Communication across every corner of your business is essential to increase the velocity of your application delivery and support pipeline. Automate, standardize, and contextualize your communication processes with xMatters.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Data center, now-a-days, is referred as the home of all the advanced technologies. In-fact, most of the businesses are now establishing their entire organizational structure around the IT capabilities.
When it comes to security, there are always trade-offs between security and convenience/ease of administration. This article examines some of the main pros and cons of using key authentication vs password authentication for hosting an SFTP server.
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question