NO MORE UPDATES TO THIS PAGE PLEASE. SUBMIT ALL FUTURE COMMENTS TO

18.1 pg 374

Worth noting new technologies, like infiniband?

18.1.1 pg 374

Worth noting the OSI model is just a guideline. It's very common to get "layering violations" in the real world. eg a VPN connection made through a HTTPS proxy (see "openVPN" for a trivial example) will send layer 3 and 4 traffic over a layer 7 application. Bleh. The OSI model is a useful guideline for approximations, but don't be too wedded to it.

Logical Networks pg 380

VLANs and "LAN extention" technology can make it almost impossible to draw network topology diagrams accurately. These technologies are vital in large multi-site HA networking environments.

Worth recommending limitting network traffic protocols? ie pick and stick with IP networking and don't use Novell IPX or Appletalk protocols on the network at all. Simplifies things. Sure, interdevice infrastructure communication (eg PPP or HSRP) will happen, but only support and route IP as the protocol used by customer equipment.

Broadcast domain on pg 382

Note that because a broadcast is sent to all devices it will reduce some of the benefits of switches; collisions of unnecessary traffic become more common.

Wiring to desktop pg 388

Also test all patch cables before putting into use (eg after purchasing but before making available for SA use). Nothing worse than diagnosing a new install and finding out it's the patch cable that's broken!

Footnote pg 389

RJ48? While RJ48 is the same physical connector as RJ45, it's used for telecoms (especially T1 lines) use, not data, and has a different pinout.

18.1.3 pg 399

Availability of monitoring and alerting is business critical, even if it's not seen that way. Lose your network, you lose the ability to work. On sites with redundancy (eg HSRP between routers) you need monitoring and alerting to tell when you've failed over in order to fix the primary before you lose everything.

-- StephenHarris - 21 Aug 2006