Difference between revisions of "Category:Network Hardware"
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[File:Datashed Network Diagram.png|thumb|right|Network Diagram]] | [[File:Datashed Network Diagram.png|thumb|right|Network Diagram]] | ||
== Summary == | == Summary == | ||
| Line 5: | Line 4: | ||
=== Data Network === | === Data Network === | ||
The Datashed network is designed around the following rough organization: | The [[:Category:1DCA|Datashed]] network is designed around the following rough organization: | ||
* Each rack has one or more top-of-rack Ethernet switches. All of these are Foundry FastIron Edge models (2 x448, 1 4802). | * Each rack has one or more top-of-rack Ethernet switches. All of these are Foundry FastIron Edge models (2 x448, 1 4802). | ||
| Line 15: | Line 14: | ||
* The core router is also connected to the ChivaNet router, [[rt-chivanet-01]], which acts as a firewall, router, and NAT device for ChivaNet WISP clients. | * The core router is also connected to the ChivaNet router, [[rt-chivanet-01]], which acts as a firewall, router, and NAT device for ChivaNet WISP clients. | ||
* VPN access from the outside is provided by a Cisco ASA-5520, called [[fw-edge-01]]. | * VPN access from the outside is provided by a Cisco ASA-5520, called [[fw-edge-01]]. | ||
* The house has a closet, called the [[:Category:IDF|IDF]], which contains [[sw-tor-04]], a Foundry FastIron Edge x448, uplinked to the datashed by way of 2x Cat5e cables running through conduits (this is changing soon). | * The [[:Category:House|house]] has a closet, called the [[:Category:IDF|IDF]], which contains [[sw-tor-04]], a Foundry FastIron Edge x448, uplinked to the datashed by way of 2x Cat5e cables running through conduits (this is changing soon). | ||
* The IDF also contains an Arris DOCSIS modem/router, which handles connectivity to the Internet for non-hosting devices through [[Xfinity Cable]]. | * The IDF also contains an Arris DOCSIS modem/router, which handles connectivity to the Internet for non-hosting devices through [[Xfinity Cable]]. | ||
| Line 39: | Line 38: | ||
* Connectivity to the house is provided by 2x 25-pair Cat3 cables, running through conduit. | * Connectivity to the house is provided by 2x 25-pair Cat3 cables, running through conduit. | ||
* The cross-connect fields are 66 blocks, as I prefer them to 110 blocks for various reasons. | * The cross-connect fields are 66 blocks, as I prefer them to 110 blocks for various reasons. | ||
* The outside line, from [[:Category:ILEC CenturyLink|CenturyLink]], is a [[POTS Line]]. | |||
== Historic Network (Trailer Era) == | |||
{{HistoricalSummary}} | |||
My home network is a 10-megabit Ethernet consisting of: | |||
* (1) [[Cabletron SEHI-24]] 24-port hub with 10base-2 EPIM slot | |||
* (2) [[HP EtherTwist Hub PLUS]] 16-port hubs with 10base-2 capability | |||
* (1) [[Boca Research BEN-210|Boca 8-port 10base-T concentrator]] | |||
* (1) [[DECserver 200/MC]] terminal server | |||
The hubs, with the notable exception of the Boca, are connected via coaxial cable. The coax provides connectivity for the VAXen and the HP. Everything else runs off typical category 5 cable. | |||
Internet access is provided by a shared dialout connection on the [[zeus|G4]]. It is running ipfw and natd (Mac OS X provides these out of the box). All I have to do to get a machine on the 'net is to set its default gateway to the IP address of the G4, and off you go. | |||
The DECserver 200/MC provides a console for all the VAXen. I can set up virtual connections on it, and use my VT-420 as the console. This saves a lot of space. | |||
My plan is to get the SCO box running BIND, LDAP, NIS, etc. All the back-end services that make a network easier to use. It's still a pain to have to set up hosts files for each box. DNS would be a much more elegant solution. Right now, my laptop is providing MOP remote booting capacity for the [[hermes|MicroVAX 3100]]. I'd like to move this functionality to either the [[Odin|SCO box]] or the [[atlantis|HP 9000]]. I had originally planned to use the [[VAX 11/750]] for this, but I'm opposed to running BSD on it (preferring to run VMS), and I don't have the needed skill with VMS administration to get all this running. UNIX just seems to be a more natural choice for such services. | |||
Latest revision as of 13:52, 14 April 2019
Summary
Data Network
The Datashed network is designed around the following rough organization:
- Each rack has one or more top-of-rack Ethernet switches. All of these are Foundry FastIron Edge models (2 x448, 1 4802).
- The ToR switches connect to the core switch, sw-core-01, via redundant multimode fiber optic links.
- The core switch does inter-VLAN routing for the entire network.
- The core switch is also uplinked to the core router, rt-core-01.
- The core router can get packets to and from the non-Ethernet segments of the network (Token Ring, ATM, FDDI, etc.), as well as to the edge routers.
- The edge routers handle connectivity to the Internet, via the GTT T1 line on rt-edge-01 and the ZiaNet ADSL on rt-edge-02.
- The core router is also connected to the ChivaNet router, rt-chivanet-01, which acts as a firewall, router, and NAT device for ChivaNet WISP clients.
- VPN access from the outside is provided by a Cisco ASA-5520, called fw-edge-01.
- The house has a closet, called the IDF, which contains sw-tor-04, a Foundry FastIron Edge x448, uplinked to the datashed by way of 2x Cat5e cables running through conduits (this is changing soon).
- The IDF also contains an Arris DOCSIS modem/router, which handles connectivity to the Internet for non-hosting devices through Xfinity Cable.
Top-Of-Rack Switches
Edge Routers
Core Router
ChivaNet Router
Voice Network
The voice network is built around an AT&T Merlin Legend PBX:
- Connectivity to the house is provided by 2x 25-pair Cat3 cables, running through conduit.
- The cross-connect fields are 66 blocks, as I prefer them to 110 blocks for various reasons.
- The outside line, from CenturyLink, is a POTS Line.
Historic Network (Trailer Era)
Note that the information presented in this section was retrieved from my old personal website, The VAX Pirate's Lair, and is not likely to be entirely accurate or timely. Spelling errors have been kept intact for the purposes of historical preservation.
My home network is a 10-megabit Ethernet consisting of:
- (1) Cabletron SEHI-24 24-port hub with 10base-2 EPIM slot
- (2) HP EtherTwist Hub PLUS 16-port hubs with 10base-2 capability
- (1) Boca 8-port 10base-T concentrator
- (1) DECserver 200/MC terminal server
The hubs, with the notable exception of the Boca, are connected via coaxial cable. The coax provides connectivity for the VAXen and the HP. Everything else runs off typical category 5 cable.
Internet access is provided by a shared dialout connection on the G4. It is running ipfw and natd (Mac OS X provides these out of the box). All I have to do to get a machine on the 'net is to set its default gateway to the IP address of the G4, and off you go.
The DECserver 200/MC provides a console for all the VAXen. I can set up virtual connections on it, and use my VT-420 as the console. This saves a lot of space.
My plan is to get the SCO box running BIND, LDAP, NIS, etc. All the back-end services that make a network easier to use. It's still a pain to have to set up hosts files for each box. DNS would be a much more elegant solution. Right now, my laptop is providing MOP remote booting capacity for the MicroVAX 3100. I'd like to move this functionality to either the SCO box or the HP 9000. I had originally planned to use the VAX 11/750 for this, but I'm opposed to running BSD on it (preferring to run VMS), and I don't have the needed skill with VMS administration to get all this running. UNIX just seems to be a more natural choice for such services.
Pages in category "Network Hardware"
The following 9 pages are in this category, out of 9 total.