Talk:Network topology

From Citizendium
Revision as of 11:39, 12 May 2008 by imported>Howard C. Berkowitz (→‎Emphasis on topology vs. on failure/recovery modes: new section)
Jump to navigation Jump to search
This article is developing and not approved.
 Main Article
 Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
To learn how to update the categories for this article, see here. To update categories, edit the metadata template.
 Definition:  Defines the method in which a computer network is architected; topologies can be either physical (meaning how the actual hardware is interconnected) or logical (meaning how that network is implemented by protocols in software) [d] [e]
Checklist and Archives
 Workgroup category:  Computers [Editors asked to check categories]
 Talk Archive:  none  English language variant:  British English

Need some ideas for more topologies? Think wireless: broadcast, multi-hop. Markus Baumeister 15:17, 2 April 2007 (CDT)

Ugh I just need more time lol! --Eric M Gearhart 12:02, 8 April 2007 (CDT)

Emphasis on topology vs. on failure/recovery modes

There are a number of topologies that apply when high availability is involved, not just in physical media such as SONET/SDH/NGN, but in things like the MPLS recovery framework (RFC3469 Framework for Multi-Protocol Label Switching (MPLS)-based Recovery. V. Sharma, Ed., F. Hellstrand, Ed.. February 2003)

Some things to consider, with fault tolerant rings, are:

  • 1+1 data flows concurrently on both rings, and the endpoint decides which to use
  • 1:1 data flows on an active ring, but can fail over to a protection ring. The failover, incidentally, can be for less than the entire ring--a failing station or media segment can be bypassed
  • N:M there are N active rings protected by M backup rings, such that N>M

Howard C. Berkowitz 12:39, 12 May 2008 (CDT)

Retrieved from "https://citizendium.org/wiki/index.php?title=Talk:Network_topology&oldid=181276"