Showing posts with label nws. Show all posts
Showing posts with label nws. Show all posts

Wednesday, 19 October 2011

how to install CISCO firewall

Below you find a short description how to install and configure a CISCO 2603 Router / Firewall. In the example, we have two LAN's using the private IP-addresses 192.168.102.0 and 192.168.101.0. Besides routing, the firewall translates all addresses from the internal LAN (192.168.102.0) to the external LAN (192.168.101.0) using NAT (Network Address Translation) and implements access lists between the two LAN's.
The following steps have to be done:
  • Connect Admin-Workstation with a serial cable to the firewall for the configuration
  • Install TFTP-Server and Terminalemulation Software on Admin-Workstation
  • Save current CISCO IOS from Router to the Admin-Workstation
  • Download CISCO Firewall IOS to the Router using TFTP
  • Save current Configurationfile from Router to the Admin-Workstation using TFTP
  • Create Configurationfile and download it to the Router using TFTP
Connect Admin-Workstation with a serial cable to the firewall for the configuration
Connect the NT4 Admin-Workstation on COM1 or COM2 using the blue RS-232 cable delivered with the CONSOLE-Port on the CISCO Router. This connection is used as the Router Console, to enter commands and to verify the boot process. To down- and upload the IOS image and configuration file a crossover LAN cable is needed. After booting the router, you will see the following messages in TeraTermPro (Terminal Emulation Software).
System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)
Copyright (c) 1999 by cisco Systems, Inc.
TAC:Home:SW:IOS:Specials for info
C2600 platform with 32768 Kbytes of main memory
Enter the basic parameters
Continue with configuration dialog? [yes/no]: yes
Would you like to enter basic management setup? [yes/no]: yes
Enter host name []: firebox
Enter enable secret [<Use current secret>]: eiger
Enter enable password []: moench
Enter virtual terminal password []: jungfrau
Configure SNMP Network Management? [no]: no
Enter interface name used to connect to the
management network from the above interface summary: FastEthernet0/0

Configuring interface FastEthernet0/0:
Use the 100 Base-TX (RJ-45) connector? [yes]: yes
Operate in full-duplex mode? [no]: no
Configure IP on this interface? [yes]: yes
IP address for this interface []: 192.168.102.200
Subnet mask for this interface [] : 255.255.255.0
Class C network is 192.168.102.0, 24 subnet bits; mask is /24

[0] Go to the IOS command prompt without saving this config.
[1] Return back to the setup without saving this config.
[2] Save this configuration to nvram and exit.

Enter your selection [2]: 2
Install TFTP-Server and Terminalemulation Software on Admin-Workstation
CISCO TFTP-Server
- Load CD-ROM
- Click on Tftpserv.exe, install it in C:\TFTP
- Start TFTP
- Menü: View/Options: TFTP server root directory: C:\TFTP\root
Save current CISCO IOS from Router to the Admin-Workstation
firebox# sh flash

System flash directory:
File Length Name/status 1 4519168 C2600-IP_FW_MZ-120-7
[4519232 bytes used, 3869376 available, 8388608 total]
8192K bytes of processor board System flash (Read/Write)

firebox# copy flash tftp
Source filename []? C2600-IP_FW_MZ-120-7
Address or name of remote host []? 192.168.102.147
Destination filename []? C2600-IP_FW_MZ-120-7
The current IOS image is now saved to the Admin Workstation.
Download CISCO Firewall IOS to the Router using TFTP
- Insert CD-ROM
- Go to E:\Images\12.0
- Look at Info File using Notepad: RIL.idf for the correct OS
- We used aaa1314.bin Cisco 2600 IOS IP/FW Feature Set 12.0(7)XK1
- Copy aaa1314.bin to TFTP directory: C:\TFTP\root
Load Image to Router:
firebox> enable
firebox2# copy tftp flash
Address or name of remote host []? 192.168.102.147
Source filename []? aaa1314.bin
Destination filename [aaa1314.bin]?
Accessing tftp://192.168.102.147/aaa1314.bin...
Erase flash: before copying? [confirm]
Erasing the flash filesystem will remove all files! [confirm]

Erasing device...erased
Erase of flash: complete
Loading aaa1314.bin from 192.168.102.147 (via FastEthernet0/0):
[OK - 4519168/9037824 bytes]

Verifying checksum... OK (0x37C6)
4519168 bytes copied in 56.244 secs (80699 bytes/sec)

firebox2# reload
Proceed with reload? [confirm]
Save current Configurationfile from Router to the Admin-Workstation using TFTP
firebox> enable
firebox# copy running-config tftp
Address or name of remote host []? 192.168.102.147
Destination filename [firebox2-confg]?
738 bytes copied in 2.4 secs (369 bytes/sec)
Edit Configurationfile and download it to the Router using TFTP
firebox> enable
firebox# copy tftp running-config
Address or name of remote host []? 192.168.102.147
Source filename []? firebox2-confg
Destination filename [running-config]?
Accessing tftp://192.168.102.17/firebox2-confg...
Loading firebox2-confg from 192.168.102.17 (via FastEthernet0/0): !
[OK - 2653/5120 bytes]
2653 bytes copied in 1.244 secs (2653 bytes/sec)
Configurationfile using NAT, Access-Lists and Routing enabled
!
version 12.0
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
!
hostname firebox
!
logging buffered 4096 debugging
no logging console
enable secret 5 xxxxxxxxxxxxxxxxx
enable password 7 xxxxxxxxxxxxxxxxx
!
ip subnet-zero
no ip domain-lookup
!
ip inspect max-incomplete high 1100
ip inspect one-minute high 1100
ip inspect udp idle-time 60
ip inspect dns-timeout 10
ip inspect name CBAC1 tcp timeout 3600
ip inspect name CBAC1 udp timeout 15
ip inspect name CBAC1 ftp timeout 3600
ip inspect name CBAC1 rcmd timeout 3600
ip inspect name CBAC1 smtp timeout 3600
ip inspect name CBAC1 sqlnet timeout 3600
ip inspect name CBAC1 tftp timeout 30
ip inspect name CBAC2 tcp timeout 3600
ip inspect name CBAC2 ftp timeout 3600
ip inspect name CBAC2 udp timeout 15
ip inspect name CBAC2 rcmd timeout 3600
ip inspect name CBAC2 smtp timeout 3600
ip inspect name CBAC2 sqlnet timeout 3600
ip inspect name CBAC2 tftp timeout 30
ip audit notify log
ip audit po max-events 100
!
interface FastEthernet0/0
 description HSZ
 ip address 192.168.102.200 255.255.255.0
 ip access-group 111 in
 ip access-group 112 out
 no ip directed-broadcast
 ip nat inside
 ip inspect CBAC1 in
 duplex auto
 speed auto
 no cdp enable
!
interface FastEthernet0/1
 description SICAP
 ip address 192.168.101.200 255.255.255.0
 ip access-group 121 in
 ip access-group 122 out
 no ip directed-broadcast
 ip nat outside
 ip inspect CBAC2 in
 duplex auto
 speed auto
 no cdp enable
!
ip default-gateway 192.168.102.1
ip nat inside source list 1 interface FastEthernet0/1 overload
ip classless
ip route 140.20.110.142 255.255.255.0 192.168.101.100
ip route 194.75.121.206 255.255.255.255 192.168.101.100
ip route 194.75.121.207 255.255.255.255 192.168.101.100
no ip http server
!
access-list 1 permit 192.168.102.0 0.0.0.255
access-list 111 permit ip 192.168.102.0 0.0.0.255 any
access-list 111 deny   ip any any
access-list 112 permit ip any any
access-list 121 permit icmp any any administratively-prohibited
access-list 121 permit icmp any any echo
access-list 121 permit icmp any any echo-reply
access-list 121 permit icmp any any packet-too-big
access-list 121 permit icmp any any time-exceeded
access-list 121 permit icmp any any unreachable
access-list 121 deny   ip any any log
access-list 122 permit ip any any
no cdp run
banner motd Akadia AG
Information Technology
Arvenweg 4
CH-3604 Thun
!
line con 0
 exec-timeout 0 0
 password 7 xxxxxxxxxxxxxxxxx
 login
 transport input none
line aux 0
line vty 0 4
 password 7 xxxxxxxxxxxxxxxxx
 login
!
no scheduler allocate
end

LAN Wiring & Pinouts

10base-T, 100base-TX/T4, 1000base-T, 10Gbase-T

Note: These pages were originally written when the world was young and 10m LANs were nose-bleedingly fast. They have been updated over the years but still contain some now long-in-the-tooth (otherwise know as legacy) stuff about crossed cables especially. You will need this information when working with specialised or older equipment but not otherwise. Crossed cables used to add a lot of color to wiring environments - sad really.
There is NOTHING more annoying than spending 30 minutes debugging a network problem to find it was the cable. Badly made or non-standard cabling is a foolish thing to spend time on - do it once and do it right. This guide may help you to forget cabling problems and spend time doing really useful things™ - like pondering the meaning of life.
Note: The IEEE 802 committee has a policy such that 12 months after the publication of a standard it is made freely availble for download. This enlightened and generous policy (relative to the ITU and TIA/EIA) has been operational for many years though it was originally 6 months after the standard was ratified - but who's counting. Documents may be found at the IEEE site.

Contents

Crossed and Straight cables - when to use them.
Standards Summary
Category 5 (UTP) colour coding table
10base Straight Cable (PC to HUB/SWITCH)
10baseT Crossed cable (PC to PC or HUB to HUB)
100baseT Straight Cable (PC to HUB/SWITCH)
100baseT Crossed cable (PC to PC or HUB to HUB)
1000base-T Gigabit Ethernet
10Gbase-T 10 Gigabit Ethernet
Power over Ethernet (PoE)
RJ45 Connector (Jack/Receptacle) Pin Numbering
RJ45 Connections - some hints
Shielded Twisted Pair (STP)
Notes:
  1. LAN cables are generically called UTP (Unshielded Twisted Pair) and are identified with a category rating. When installing new cable, unless there is a very good reason not to, you should be using category 5e or 6 UTP which is rated for 10mb, 100mb or Gigabit LAN operation. If you are moving to the exotic world of 10G LAN you will need category 6a wiring to go the full 100m (~330ft). Downhill, with a following wind, you can run 10G LANs over catgory 6 wiring over reduced distance. Info on Shielded Twisted Pair (STP) cabling.
  2. UTP comes in two forms SOLID or STRANDED. SOLID refers to the fact that each internal conductor is made up of a single (solid!) wire, STRANDED means that each conductor is made up of multiple smaller wires. Stranded cable (which is typically more expensive) has a smaller 'bend- radius' (you can squeeze the cable round tighter corners with lower loss) and due to its flexibility should be used where you plug and unplug the cable frequently. All other things being equal the performance of both types of cable is the same. In general, solid cable is used for backbone wiring and stranded for PC to wall receptacle (patch) cables. Beware: Each type of wire, solid or stranded, and each cable category (5e, 6, 6a) needs its own connector type.
  3. Straight and crossed cables are still shown in the various diagrams. Crossed are now practically irrelevant for anything but older equipment. Modern switches (and hubs - if they still exist) auto-sense the connections meaning that you can use straight cables almost everywhere - but when using older equipment you may still need a crossed cable.
  4. 100M LAN Notes: When working with 100M LANs you CAN use 100base-TX wiring with a 10base-T network (but not always the other way round). In general ALWAYS use 100baseTX/T4 wiring standards. If you are using category 5, 5e or 6 wiring EVERYWHERE in a 100M LAN you can use the 100base-TX standard (this only uses 2 pairs , 4 conductors). Most of the information below assumes you are using category 5, 5e or 6 cables. If you are using category 3 or 4 cables with 100M LANs ANYWHERE you MUST use the 100Base-T4 standard and this has ADDITIONAL RESTRICTIONS documented throughout (it uses all 4 pairs, 8 conductors). LAN connections/pinouts are defined by IEEE 802.3u.
  5. Gigabit and Gigabit+ LAN Notes: While 100M LANs allowed a 2-pair (4 conductor) wiring version (100base-TX) gigabit LANs require 4-pairs (all 8 conductors) which is functionally similar to 100base-T4 wiring. Even if gigabit LANs are still in the future - use 100base-T4/1000base-T (4-pair) wiring. If you still have 100base-TX (or even 10base-T) wiring in a gigabit LAN it will still function but auto-negotiation will limit speeds on those segments to 100Mbit/s.
  6. Maximum LAN cable runs or segments are 100 meters (~330ft) unless otherwise noted. Segments can joined using hubs (Class II repeaters) in which case up to 5 such segments (500m or ~1650 feet) are allowed for 10Base-T. When using 100Base-T/TX 2 hubs are allowed (200m or ~660 feet). When modern switches are used with 100M and Gigabit LANs these limits are raised and the switch vendors specification should be consulted.
  7. We provide a Cabling FAQ which provides additional information or background.
  8. We have added an article on mixing 10/100 MB LAN and Telephony on a single category 5(e) or 6 cable. It can be done, but you must be very, very cautious. If you are use Gigabit LANs this requires use of all 4 pairs( 8 conductors) thus eliminating the possibility of mixing LAN and telephony on the same wiring.
  9. We have updated most of the material for 1000base-T (Gigabit Ethernet 802.3ab) which uses all 4 pairs (8 conductors) and added notes where relevant about Power-over-Ethernet (PoE 802.3af and 802.3at).
  10. A copper standard for 10GB Ethernet (802.3an) was published by the IEEE in 2006 and is known as 10GBASE-T. It requires category 6A cables (ANSI/TIA-568-C.2/ISO 11801 Ammendment 2) for 100m (~330ft) operation but will run shorter distances over category 6 cables that meet TIA-155-A (ISO TR 24750) specifications.

Crossed and Straight cables - when to use them

The following diagram shows the Normal use of Crossed and Straight cables (see also the notes below).
Notes:
  1. We show Straight cables as BLUE and Crossed as RED. That is our convention. The cable color can be anything you choose or, more likely, the vendor decides.
  2. To avoid the need for Crossed cables many vendors provided UPLINK ports on Hubs or Switches - these were specially designed to allow the use of a STRAIGHT cable when connecting back-to-back Hubs or Switches. Read the manufacturers documentation carefully.
  3. Increasingly vendor hubs (can you still buy them) and switches will auto-detect the connection type and internally switch the connectors so that STRAIGHT cables can be used everywhere.
up icon

Standards Summary

The various standards can get a tad complicated and messy. We get occasional email requesting a summary of the standards - this is our attempt to provide a quick overview.
Standard Required Pairs 10M 100M 1000M 10G Cable Notes
10base-T 2 (1/2 and 3/6) yes yes no no cat 5, 5e, 6 100m support only if no cat 3/4 in run
100base-TX 2 (1/2 and 3/6) yes yes no no cat 5, 5e, 6 100m support only if no cat 3/4 in run
100base-T4 4 (1/2, 3/6, 4/5 and 7/8) yes yes yes yes cat 3, 4, 5, 5e, 6 max of 100m if cat 3 or 4 in network
1000base-T 4 (1/2, 3/6, 4/5 and 7/8) yes yes yes yes cat 5e, 6 Functionally identical to 100base-T4. Some cat cables may be acceptable.
10Gbase-T 4 (1/2, 3/6, 4/5 and 7/8) yes yes yes yes cat 6a cat 6 cables may be used but have distance limitations.
up icon

Category 5(e) (UTP) colour coding table

The following table shows the normal colour coding for category 5 cables (4 pair) based on the two standards supported by TIA/EIA (see also our primer on this topic)
We get occasional email about the difference between 568A and 568B wiring. Which one you use is a matter of local decision. These standards apply to the color code used within any SINGLE cable run - BOTH ENDS MUST USE THE SAME STANDARD. However, since they both use the same pinout at the connectors you can mix 568A and 568B cables in any installation.
cat colors
up icon

10baseT Straight Cable (PC to HUB/SWITCH)

Straight cables are used to connect PCs or other equipment to a HUB or Switch. If your connection is PC to PC or HUB to HUB you MAY need to use a Crossed cable with older equipment. Most modern Hubs and Switches provide auto-sensing which means a straight cable can always be used.
The following cable description is for the wiring of both ends (RJ45 Male connectors) with the 568B category 5(e) wiring colors you could, of course, use the 568A colour scheme.
Pin No. strand color Name
1 white and orange TX+
2 orange TX-
3 white and green RX+
4 NC *
5 NC *
6 green RX-
7 NC *
8 NC *
NOTE: Items marked * are not necessary for 10M LANs (10base-T) but since you will be moving shortly to 100MB or Gigabit LANs (won't you) you will save yourself a LOT OF TIME finding crappy cable (that you made) that does not work. Instead we suggest you wire to 100Base-T4 standards. After all you gotta stick the ends somewhere man.
We use BLUE for 10base-T straight cables. NOTE: All our wiring is now done to the 100base-T4 spec which you can use with 10base-T networks - but NOT necessarily the other way around.
up icon

10baseT Crossed cable (PC to PC or HUB to HUB)

Crossed cables are used to connect PCs to one other PC or to connect a HUB to a HUB. Crossed cables are sometimes called Crossover, Patch or Jumper cables. If your connection is PC to HUB you MUST use a Straight cable.
The following description shows the wiring at both ends (male RJ45 connectors) of the crossed cable.
One end
RJ45 Male
Other end
RJ45 Male
1 3
2 6
3 1
4 * 5 *
5 * 4 *
6 2
7 * 8 *
8 * 7 *
NOTES:
  1. Items marked * are not necessary for 10M LANs but since you will be moving shortly to 100MB or Gigabit LANs (won't you) you will save yourself a LOT OF TIME finding crappy cable (that you made) that does not work. Instead we suggest you wire to 100BaseT standards.
  2. We use RED for crossed cables (or more commonly now a red heat-shrink collar at each end).
  3. All our crossed wiring is done to the 100base-T4 spec which you can use with 10baseT networks - but NOT always the other way around.
up icon

100base-T Straight Cable (PC to HUB/SWITCH)

Straight cables are used to connect PCs or other equipment to a HUB or Switch. If your connection is PC to PC or HUB to HUB you MAY need to use a Crossed cable with older equipment. Most modern Hubs and Switches provide auto-sensing which means a straight cable can always be used.
The following cable description is for the wiring of BOTH ends (RJ45 Male connectors) with your category 5 wiring colors (TIA/EIA 568A or 568B though the example uses 568B colors).
Pin No. conductor color Name
1 white and orange TX_D1+
2 orange TX_D1-
3 white and green RX_D2+
4 blue BI_D3+ **
5 white and blue BI_D3- **
6 green RX_D2-
7 white and brown BI_D4+ **
8 brown BI_D4- **
We use BLUE for 100baseT straight cables.
NOTES:
  1. Wires marked ** are ABSOLUTELY NECESSARY for 100Base-T4 networks - used when any combination of category 3/4/5 cables are present, when using 1000base-T (GigE) and MAY be required for Power-over-Ethernet (PoE) - see below.
  2. Wires marked ** are not essential for 100Base-TX (using cat 5/5e6/6a ONLY cables) and CAN be used for other purposes, for example, telephony but, .. beware .. read this FAQ and our LAN plus Telephony article before you wire your entire neighbourhood for surround sound.
  3. The Power-over-Ethernet spec (802.3af) allows three schemes where power may be supplied. Two of these schemes use pairs 4,5 and 7,8 (marked ** in above table) for power (called Midspan PSE and Alternative B or Mode B), one scheme uses ONLY pairs 1,2 and 3,6 (Endpoint PSE, Alternative A or Mode A) for both signals and power. Depending on which scheme you use pairs 4,5 and 7,8 may be required. See Power over Ethernet (PoE).
  4. Gigabit Ethernet requires all 4 pairs (8 conductors).
  5. All our wiring is now done to the 100base-T4 spec which you can use with 1000base-T and even 10baseT networks - but NOT the other way around.

100base-T Crossed cable (PC to PC or HUB to HUB)

Crossed cables are used to connect PCs to one other PC or to connect a HUB to a HUB. Crossed cable are sometimes called Crossover, Patch or Jumper cables. If your connection is PC to HUB you MUST use a Straight cable. Most modern Hubs and Switches provide auto-sensing which means a straight cable can always be used.
The following description shows the wiring at both ends (male RJ45 connectors) of the crossed cable. Note: The diagrams below shows crossing of all 4 pairs and allows for the use of cat3/4 cables with 100m LANs (100base-T4). Pairs 4,5 and 7,8 do not NEED to be crossed in 100base-TX wiring. See notes below.
crossed connection
We use RED for crossed cables (or more commonly now a red heat-shrink collar at each end).
NOTES:
  1. All our crossed wiring is now done to the 100base-T4 spec (uses all 4 pairs, 8 conductors) which you can use with 1000base-T and even 10base-T networks - but NOT necessarily the other way around.
  2. Many commercial 100m LAN patch cables seem not to cross pairs 4,5 and 7,8. If there is no cat3/4 wiring in the network this perfectly acceptable.
  3. Gigabit Ethernet uses all 4 pairs so requires the full 4 pair (8 conductor) cross configuration (shown above).
  4. If you are using Power-over-Ethernet (802.3af) then Mode A or Alternative A uses pairs 1,2 and 3,6 for both signals and power. Mode B or alternative B uses 4,5 and 7,8 to carry power. In all cases the spec calls for polarity insensitive implementation (using a diode bridge) and therefore crossing or not crossing pairs 4,5 and 7,8 will have no effect. See Power over Ethernet (PoE).
up icon

1000base-T Gigabit Ethernet

1000base-T is the copper based version of the gigabit Ethernet standard defined by 802.3ab which, since it is over 12 months old, is available free of charge from the enlightened IEEE. Great work. In passing, if you want to see sophistry raised to an art form read the EIA's justification for charging for their specifications. (Note: The original EIA statement is, unfortunately, no longer available on-line. This is a great loss to the development of the English language in general, and comedy writing in particular.) The following notes apply to the 1000base-T spec:
  1. The standard defines auto-negotiation of speed between 10, 100 and 1000 Mbit/s so the speed will fall to the maximum supported by both ends - ensuring inter-working with existing installations.
  2. The cable specification base-line is ANSI/TIA/EIA-568-A-1995 (which you have to pay for). This means that if you know your cat5 cable was manufactured to this standard (there was a lower rated 1991 version of this specification) then it will support Gigabit Ethernet. Cat5 cable manufactured to the old specification may work or it may not - you need to run some tests. Cat 5e and cat 6 being higher spec cables will support Gigabit Ethernet.
  3. Maximum runs are the standard 100m (~330ft).
  4. Gigabit Ethernet uses all 4 pairs (8 conductors). The transmission scheme is radically different from 10 and 100 Mbit/s standards (PAM-5: a 5 level amplitude modulation scheme) and each conductor is used for send and receive.
  5. Crossed Gigabit Ethernet cables must cross all 4 pairs however it should be noted that since all 1000base-T equipment includes automatic crossover detection, crossed 1000base-T cables are extremely rare.
  6. Because of the higher speeds everything about a Gigabit cable must be correct. Specifically the connectors must be rated for Gigabit operation with minimal untwisting of the cable when adding the connector. See also cabling hints.
  7. When Cat6 cables are used these will also support 10 Gbit/s operation up to 55m. When Cat6a cables are used these will support 10 Gbit/s operation up to 100m.
up icon

10Gbase-T 10 Gigabit Ethernet

This is serious stuff only for server-server installations at this time - most PCs have a hard time even driving Gigabit networks. 10Gbase-T defines 10 gigabit Ethernet over copper cables (multiple other PHYs also exist within the 10G Ethernet ecosystem). Originally defined in 802.3an (2006) this has now been consolidated into the base 802.3-2008 spec (available at no cost from the IEEE). The followings notes apply to 10Gbase-T:
  1. The standard allows for auto-negotiation and thus 10Gbase-T will interwork with 10base-T, 100base-TX/T4 and 1000base-T networks but default, obviously, to the highest common speed supported on any given point-to-point connection.
  2. All 4 pairs - 8 connectors are required - it uses 1000base-T (or 100base-T4) wiring.
  3. 10Gbase-T requires category 6a wiring defined by ANSI/TIA-568-C.2 (ISO 11801 amendment 2) to support 100m (~330ft) runs. Category 6a wiring is bigger (standard allows up to 0.35 inch cable diameter vs ~0.20 for cat 5e and ~0.23 for cat 6) and currently (2011) around 30% more expensive than cat 6 which is around 50% more expensive than cat 5e.
  4. Category 6 wiring will support 10Gbase-T at up to 55m (~185ft) in electrically quiet environments and up to 37m (~81ft) in electrically noisy environments (such as in cable bundles, elevator shafts, proximity to flourescent lights). The measurement of electrical noise threshold levels (especially cross-talk) for cat 6a cables is defined by TIA-155-A (and ISO TR 24750) both of which you will have the dubious pleasure of paying for - handsomely.
  5. To maintain 10G speeds needs serious attention to all wiring practices. Minimum bending radii, careful attention to connectors and minimum untwisting of pairs are all crucial - this is not amateur stuff. STP may be a safer option (a view not always shared by the cable suppliers) or optical.
up icon

Power over Ethernet (PoE)

The original PoE specification was 802.3.af (2003) which has been superseded by 802.3at (2009). The primary differences are that the new 802.3at specification includes support for Gigabit LANs and raises the power levels available when using certain cable types. The following notes apply:
  1. The power available at each end-point with 802.3af is 13.0 Watts (W). The maximum input voltage is 44V DC at a current of 350ma which gives a figure of 15.4 W (44 x 350/100) but due to power losses in cables the 13.0 W value is guaranteed even at maximum (100m - ~330ft) runs on category 5, 5e and 6 wiring.
  2. The current 802.3at standard spilts systems into two categories for PoE levels based on the cable type. Type 1 covers cat 5 cables and these remain limited to the 802.3af limits of 13 W. Type 2 covers cat 5e (the actual minimum spec is ANSI/TIA/EIA-568-A-1995 which does cover some late cat 5 cables which only became available some time after 1995) and cat 6 cables and increases the maximum current to 600ma giving a maximum power figure of 44 x 600/100 = 26.4 W. Again due to losses over distance (lower than with Type 1 systems) this gives a figure of 25.5 W which is available even at maximum (100m - ~330ft) runs.
  3. Power Wiring: 802.3at defines two Alternatives (A and B) depending on your wiring system.
    • If you are using 10base-T or 100base-TX (both only need 2 pairs - 4 connectors) then Alternative A wiring sends power over the signal pairs 1,2 and 3,6 since these may be the only ones connected. Alternative B wiring uses the unused pairs 4,5 and 7,8 for power and will clearly only work for systems which have connected all 4 pairs (and are therefore using 100base-T4 wiring!).
    • If you are using 100base-T4 or 1000base-T (both need 4 pairs - 8 connectors) then Alternative A wiring sends power over the signal pairs 1,2 and 3,6. Alternative B wiring uses the signal pairs 4,5 and 7,8. Since 100base-T4 and 1000base-T need all 4 wires connected there is no functional difference between Alternative A and B in this case.
up icon

RJ45 Connector (Plug and Receptacle) Pin Numbering

RJ45 Male Connector (Plug) and Female Connector (Receptacle)
rj45
Notes:
  1. Today the male connector is more normally called a plug and the female connector a receptacle. Historically the term Jack was frequently used to describe what is now called a plug and Wall-Jack, or even just Jack, to describe the receptable. It's complicated.
  2. While most commonly referred as an RJ45, it is a modular connector with the catchy name of 8P8C (8 Positions, 8 Connections). RJ - in case you were wandering - means Registered Jack.
  3. The receptacle numbering is shown using a FRONT view (left to right, pin 1 - 8). Beware however, receptacles are wired from the REAR and hence the numbering will be inverted. Viewed from the REAR the numbering will be left to right, pin 8 - 1.
up icon

RJ45 Connections - some hints

We get mail saying 'Help. I've wired it correctly but it does not work'. Here are some simple notes that may help. Remember: it's more difficult that you think.
Use the best crimp tool you can afford or borrow. A cheap magnifying glass can sometimes help enormously.
  1. The RJ45 connector is the critical connection. Always use the highest quality connectors you can afford and rated for the cable category (using category 5e rated connectors with categeory 6/6a cable is a stupid economy). The most common cause of connection faults are bad connectors.
    There are different connectors for stranded and solid cable and manufacturers do not always do a good job at differentiating them. Spend the time to make sure you have the right connector type. Category 6/6a cables have higher rated (read - more expensive) connectors - always use them - don't penny-pinch. If you use the wrong type of connector the cable may work initially but it will almost certainly fail very quickly - then you'll spend hours debugging the problem. It will all end in tears as mothers throughout the world used to say, and probably still do.
  2. Make and test practice cables until you get it right every time - especially before you destroy a cable you just spent 2 hours fitting.
  3. When installing cable runs ensure the bend radius is within the cable specification and avoid kinks and excessive cable twisting. While the bend radius for Cat5/5e/6 is defined to be approximately 1 inch, in general this should be avoided and a more generous 3 - 6 inches should be allowed unless absolutely necessary.
  4. When cutting the exterior cover of the cable be very careful not to cut the insulation cover of the conductors since this can cause shorts. Bottom line: the cable won't work.
  5. Expose a maximum of 1 inch of individual conductors when preparing the cable for connection.
  6. Untwist the pairs and line up all the conductors according to the wiring standard you are using. Only untwist the exposed connector pairs that lie outside of the exterior cover. Do not allow the untwisting operation to propagate under the exterior cover.
  7. Measure the cable end by placing it beside the RJ45 and trim the conductor ends so they are are all the same length and no conductor wire is visible outside the plastic cover of the RJ45 connector. This procedure also ensures the absolute minimum of untwisted cable is used. Untwisting too much cable can easily cause reduced speed - especially when running Gigabit connections.
  8. Carefully slide the prepared cable into the RJ45 connector making sure the end of the conductors reaches the end of the RJ45 connector.
  9. Place the crimp tool carefully over the connector and make the connection with a single firm squeeze operation.
  10. Visually inspect the connection and test the cable before fitting if possible.
Note: If you are having problems, throwing the crimp tool accross the room or beating your head against the nearest wall rarely improves the situation. Inspect the connection with a magnifying glass to see what is going wrong and then go and sit down in a dark room for 30 minutes (aka take a break) before trying again. This sometimes works.
up icon

Shielded Twisted Pair

Shielded Twisted Pair (STP) comes in a variety of formats. It is typically used in three applications:
  1. Where there is significant EMI (Electro-Magnetic Induction) in the environment such as that caused by high-powered electric motors (for example, in elevator shafts), flourescent lighting, heavy industrial equipment, etc. In this case the ethernet signals in the cable require protection against external interference from either adjacent pairs or the environment.
  2. Where there is extremely sensitive electrical/electronic equipment in the surrounding environment or where security requirements demand elimination of eavesdropping possibilities from radiated LAN signals (TEMPEST). In this case the ethernet signals in the shielded cable are contained and prevented from polluting, or escaping into, the external environment.
  3. Where maximum performance - either speed or distance - is required. The problem here is normally Alien Crosstalk (ANEXT) such as can occur in very high speed (gigabit and 10gb) LANs. As Ethernet speeds continue to increase either fiber or Shielded Twisted Pair is becoming increasingly common. For instance, to reach 100m distances at 10Gb speeds on copper cables will require shielded cable (limited to 55m for UTP).
Shielded cable comes in three broad types with a confusing range of terminology:
  1. Where there is a single foil (FTP - Foil Twisted Pair) or braided (ScTP - Screened Twisted Pair) shield inside the jacket covering all four pairs. Suitable for applications 1 and 2 above.
  2. Where there is a foil shield covering each pair. This is frequently refered to as PiMF (Pairs in Metal Foil) and is designed primarily to eliminate Alien Cross-talk (ANEXT) from adjacent pairs. Suitable for application 3 above.
  3. Where there is a foil shield covering each pair and a (Foil or Braided) shield covering the whole cable. This is frequently refered to as SSTP (Double Shield Twisted Pair) or even PiMF - since many manufacturers also add a jacket shield to foil covered pair cables. Suitable for applications 1, 2 and 3 above.
In almost all cases there is a single ground wire (called a drain) which allows for connection to secondary grounding sources.
The diagram below illustrates the differences:
Shielded Twisted Pair
Notes:
  1. Shielded cable of any variety has a greater diameter than UTP and will therefore occupy more space in cable ducting and raceways.
  2. Connecting shielded cable is more complex and time consuming - but not execessively so - than conventional UTP. Manufacturers specifications vary enormously, expecially with respect to grounding, and should be followed closely.
  3. In shielded cable installations the jacks and receptacles are typically made of metal and the cable shield (foil or braid) is connected electrically to the connector and thence through the metal receptable to a suitable ground provided by the end equipment.
  4. Foil covered pairs are typically not connected to ground and thus provide only alien crosstalk immunity from adjacent pairs (ANEXT).
  5. Manufacturers specifications and measurements suggest that shielded cables do NOT create antenna effects - indeed experiments show that UTP creates a substantially greater antenna effect (~40db) over correctly grounded shielded cables.
  6. Even ungrounded shielded cables provide better performance (by ~20db) than conventional unshielded twisted pair (UTP).
  7. The drain wire provides a secondary or auxiliary ground method in cases where metallic path grounding is provided by the connectors and, as such, is optional. In cases where metal connectors are not being used (there is no grounding via the connectors) the drain wire may be used as the primary grounding method and needs to be routed independantly to a suitable ground. The drain wire (cable ground) needs to be exposed before the connector is added. This process could require a considerable length of exposed drain wire depending on the location of the ground source. A plastic insulating sheath should be placed over the drain wire to minimize electrical hazards.
  8. In all cases where both ends of a shielded cable are grounded this should be done using a common (building) ground to avoid ground potential loops which if they exceed 1V will have serious effects on cable performance. It is also important to note that 'grounding both ends' means final equipment terminations. Intermediate jacks or faceplates must maintain electrical continuity throughout the cable run but are not themselves grounded. This app note from AMP provides a detailed explanation.

Tuesday, 18 October 2011

Ethernet Cable - Color Coding Diagram

The information listed here is to assist Network Administrators in the color coding of Ethernet cables. Please be aware that modifying Ethernet cables improperly may cause loss of network connectivity. Use this information at your own risk, and insure all connectors and cables are modified in accordance with standards. The Internet Centre and its affiliates cannot be held liable for the use of this information in whole or in part.
T-568A Straight-Through Ethernet Cable
The TIA/EIA 568-A standard which was ratified in 1995, was replaced by the TIA/EIA 568-B standard in 2002 and has been updated since. Both standards define the T-568A and T-568B pin-outs for using Unshielded Twisted Pair cable and RJ-45 connectors for Ethernet connectivity. The standards and pin-out specification appear to be related and interchangeable, but are not the same and should not be used interchangeably.
T-568B Straight-Through Ethernet Cable
Both the T-568A and the T-568B standard Straight-Through cables are used most often as patch cords for your Ethernet connections. If you require a cable to connect two Ethernet devices directly together without a hub or when you connect two hubs together, you will need to use a Crossover cable instead.
RJ-45 Crossover Ethernet Cable
A good way of remembering how to wire a Crossover Ethernet cable is to wire one end using the T-568A standard and the other end using the T-568B standard. Another way of remembering the color coding is to simply switch the Green set of wires in place with the Orange set of wires. Specifically, switch the solid Green (G) with the solid Orange, and switch the green/white with the orange/white.
Ethernet Cable Instructions:
  1. Pull the cable off the reel to the desired length and cut. If you are pulling cables through holes, its easier to attach the RJ-45 plugs after the cable is pulled. The total length of wire segments between a PC and a hub or between two PC's cannot exceed 100 Meters (328 feet) for 100BASE-TX and 300 Meters for 10BASE-T.
  2. Start on one end and strip the cable jacket off (about 1") using a stripper or a knife. Be extra careful not to nick the wires, otherwise you will need to start over.
  3. Spread, untwist the pairs, and arrange the wires in the order of the desired cable end. Flatten the end between your thumb and forefinger. Trim the ends of the wires so they are even with one another, leaving only 1/2" in wire length. If it is longer than 1/2" it will be out-of-spec and susceptible to crosstalk. Flatten and insure there are no spaces between wires.
  4. Hold the RJ-45 plug with the clip facing down or away from you. Push the wires firmly into the plug. Inspect each wire is flat even at the front of the plug. Check the order of the wires. Double check again. Check that the jacket is fitted right against the stop of the plug. Carefully hold the wire and firmly crimp the RJ-45 with the crimper.
  5. Check the color orientation, check that the crimped connection is not about to come apart, and check to see if the wires are flat against the front of the plug. If even one of these are incorrect, you will have to start over. Test the Ethernet cable.
Ethernet Cable Tips:
  • A straight-thru cable has identical ends.
  • A crossover cable has different ends.
  • A straight-thru is used as a patch cord in Ethernet connections.
  • A crossover is used to connect two Ethernet devices without a hub or for connecting two hubs.
  • A crossover has one end with the Orange set of wires switched with the Green set.
  • Odd numbered pins are always striped, even numbered pins are always solid colored.
  • Looking at the RJ-45 with the clip facing away from you, Brown is always on the right, and pin 1 is on the left.
  • No more than 1/2" of the Ethernet cable should be untwisted otherwise it will be susceptible to crosstalk.
  • Do not deform, do not bend, do not stretch, do not staple, do not run parallel with power cables, and do not run Ethernet cables near noise inducing components.
Basic Theory:

By looking at a T-568A UTP Ethernet straight-thru cable and an Ethernet crossover cable with a T-568B end, we see that the TX (transmitter) pins are connected to the corresponding RX (receiver) pins, plus to plus and minus to minus. You can also see that both the blue and brown wire pairs on pins 4, 5, 7, and 8 are not used in either standard. What you may not realize is that, these same pins 4, 5, 7, and 8 are not used or required in 100BASE-TX as well. So why bother using these wires, well for one thing its simply easier to make a connection with all the wires grouped together. Otherwise you'll be spending time trying to fit those tiny little wires into each of the corresponding holes in the RJ-45 connector.

Tuesday, 4 October 2011

IP Addressing:


An IP (Internet Protocol) address is a unique identifier for a node or host connection on an IP network. An IP address is a 32 bit binary number usually represented as 4 decimal values, each representing 8 bits, in the range 0 to 255 (known as octets) separated by decimal points. This is known as "dotted decimal" notation.

Example: 140.179.220.200

It is sometimes useful to view the values in their binary form.

140 .179 .220 .200

10001100.10110011.11011100.11001000

Every IP address consists of two parts, one identifying the network and one identifying the node. The Class of the address and the subnet mask determine which part belongs to the network address and which part belongs to the node address.
Address Classes:
There are 5 different address classes. You can determine which class any IP address is in by examining the first 4 bits of the IP address.

Class A addresses begin with 0xxx, or 1 to 126 decimal.

Class B addresses begin with 10xx, or 128 to 191 decimal.

Class C addresses begin with 110x, or 192 to 223 decimal.

Class D addresses begin with 1110, or 224 to 239 decimal.

Class E addresses begin with 1111, or 240 to 254 decimal.

Addresses beginning with 01111111, or 127 decimal, are reserved for loopback and for internal testing on a local machine. [You can test this: you should always be able to ping 127.0.0.1, which points to yourself] Class D addresses are reserved for multicasting. Class E addresses are reserved for future use. They should not be used for host addresses.

Now we can see how the Class determines, by default, which part of the IP address belongs to the network (N) and which part belongs to the node (n).

Class A -- NNNNNNNN.nnnnnnnn.nnnnnnn.nnnnnnn

Class B -- NNNNNNNN.NNNNNNNN.nnnnnnnn.nnnnnnnn

Class C -- NNNNNNNN.NNNNNNNN.NNNNNNNN.nnnnnnnn

In the example, 140.179.220.200 is a Class B address so by default the Network part of the address (also known as the Network Address) is defined by the first two octets (140.179.x.x) and the node part is defined by the last 2 octets (x.x.220.200).

In order to specify the network address for a given IP address, the node section is set to all "0"s. In our example, 140.179.0.0 specifies the network address for 140.179.220.200. When the node section is set to all "1"s, it specifies a broadcast that is sent to all hosts on the network. 140.179.255.255 specifies the example broadcast address. Note that this is true regardless of the length of the node section.
Private Subnets:
There are three IP network addresses reserved for private networks. The addresses are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. They can be used by anyone setting up internal IP networks, such as a lab or home LAN behind a NAT or proxy server or a router. It is always safe to use these because routers on the Internet will never forward packets coming from these addresses

Subnetting an IP Network can be done for a variety of reasons, including organization, use of different physical media (such as Ethernet, FDDI, WAN, etc.), preservation of address space, and security. The most common reason is to control network traffic. In an Ethernet network, all nodes on a segment see all the packets transmitted by all the other nodes on that segment. Performance can be adversely affected under heavy traffic loads, due to collisions and the resulting retransmissions. A router is used to connect IP networks to minimize the amount of traffic each segment must receive.
Subnet Masking
Applying a subnet mask to an IP address allows you to identify the network and node parts of the address. The network bits are represented by the 1s in the mask, and the node bits are represented by the 0s. Performing a bitwise logical AND operation between the IP address and the subnet mask results in the Network Address or Number.

For example, using our test IP address and the default Class B subnet mask, we get:

10001100.10110011.11110000.11001000 140.179.240.200 Class B IP Address

11111111.11111111.00000000.00000000 255.255.000.000 Default Class B Subnet Mask

10001100.10110011.00000000.00000000 140.179.000.000 Network Address
Default subnet masks:
Class A - 255.0.0.0 - 11111111.00000000.00000000.00000000

Class B - 255.255.0.0 - 11111111.11111111.00000000.00000000

Class C - 255.255.255.0 - 11111111.11111111.11111111.00000000

CIDR -- Classless InterDomain Routing.

CIDR was invented several years ago to keep the internet from running out of IP addresses. The "classful" system of allocating IP addresses can be very wasteful; anyone who could reasonably show a need for more that 254 host addresses was given a Class B address block of 65533 host addresses. Even more wasteful were companies and organizations that were allocated Class A address blocks, which contain over 16 Million host addresses! Only a tiny percentage of the allocated Class A and Class B address space has ever been actually assigned to a host computer on the Internet.

People realized that addresses could be conserved if the class system was eliminated. By accurately allocating only the amount of address space that was actually needed, the address space crisis could be avoided for many years. This was first proposed in 1992 as a scheme called Supernetting.

The use of a CIDR notated address is the same as for a Classful address. Classful addresses can easily be written in CIDR notation (Class A = /8, Class B = /16, and Class C = /24)

It is currently almost impossible for an individual or company to be allocated their own IP address blocks. You will simply be told to get them from your ISP. The reason for this is the ever-growing size of the internet routing table. Just 5 years ago, there were less than 5000 network routes in the entire Internet. Today, there are over 90,000. Using CIDR, the biggest ISPs are allocated large chunks of address space (usually with a subnet mask of /19 or even smaller); the ISP's customers (often other, smaller ISPs) are then allocated networks from the big ISP's pool. That way, all the big ISP's customers (and their customers, and so on) are accessible via 1 network route on the Internet.

It is expected that CIDR will keep the Internet happily in IP addresses for the next few years at least. After that, IPv6, with 128 bit addresses, will be needed. Under IPv6, even sloppy address allocation would comfortably allow a billion unique IP addresses for every person on earth
Examining your network with commands:
Ping

PING is used to check for a response from another computer on the network. It can tell you a great deal of information about the status of the network and the computers you are communicating with.

Ping returns different responses depending on the computer in question. The responses are similar depending on the options used.

Ping uses IP to request a response from the host. It does not use TCP

.It takes its name from a submarine sonar search - you send a short sound burst and listen for an echo - a ping - coming back.

In an IP network, `ping' sends a short data burst - a single packet - and listens for a single packet in reply. Since this tests the most basic function of an IP network (delivery of single packet), it's easy to see how you can learn a lot from some `pings'.

To stop ping, type control-c. This terminates the program and prints out a nice summary of the number of packets transmitted, the number received, and the percentage of packets lost, plus the minimum, average, and maximum round-trip times of the packets.

Sample ping session

PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=2 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=2 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=2 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=2 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=255 time=2 ms
64 bytes from 127.0.0.1: icmp_seq=5 ttl=255 time=2 ms
64 bytes from 127.0.0.1: icmp_seq=6 ttl=255 time=2 ms
64 bytes from 127.0.0.1: icmp_seq=7 ttl=255 time=2 ms
64 bytes from 127.0.0.1: icmp_seq=8 ttl=255 time=2 ms
64 bytes from 127.0.0.1: icmp_seq=9 ttl=255 time=2 ms

localhost ping statistics

10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 2/2/2 ms
meikro$

The Time To Live (TTL) field can be interesting. The main purpose of this is so that a packet doesn't live forever on the network and will eventually die when it is deemed "lost." But for us, it provides additional information. We can use the TTL to determine approximately how many router hops the packet has gone through. In this case it's 255 minus N hops, where N is the TTL of the returning Echo Replies. If the TTL field varies in successive pings, it could indicate that the successive reply packets are going via different routes, which isn't a great thing.

The time field is an indication of the round-trip time to get a packet to the remote host. The reply is measured in milliseconds. In general, it's best if round-trip times are under 200 milliseconds. The time it takes a packet to reach its destination is called latency. If you see a large variance in the round-trip times (which is called "jitter"), you are going to see poor performance talking to the host
NSLOOKUP
NSLOOKUP is an application that facilitates looking up hostnames on the network. It can reveal the IP address of a host or, using the IP address, return the host name.

It is very important when troubleshooting problems on a network that you can verify the components of the networking process. Nslookup allows this by revealing details within the infrastructure.
NETSTAT
NETSTAT is used to look up the various active connections within a computer. It is helpful to understand what computers or networks you are connected to. This allows you to further investigate problems. One host may be responding well but another may be less responsive.
IPconfig
This is a Microsoft windows NT, 2000 command. It is very useful in determining what could be wrong with a network.

This command when used with the /all switch, reveal enormous amounts of troubleshooting information within the system.

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : cowder
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 12.90.108.123
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 12.90.108.125
DNS Servers . . . . . . . . . . . : 12.102.244.2
204.127.129.2
Traceroute
Traceroute on Unix and Linux (or tracert in the Microsoft world) attempts to trace the current network path to a destination. Here is an example of a traceroute run to www.berkeley.edu:

$ traceroute www.berkeley.edu

traceroute to amber.Berkeley.EDU (128.32.25.12), 30 hops max, 40 byte packets
 

1 sf1-e3.wired.net (206.221.193.1) 3.135 ms 3.021 ms 3.616 ms

2 sf0-e2s2.wired.net (205.227.206.33) 1.829 ms 3.886 ms 2.772 ms

3 paloalto-cr10.bbnplanet.net (131.119.26.105) 5.327 ms 4.597 ms 5.729 ms

4 paloalto-br1.bbnplanet.net (131.119.0.193) 4.842 ms 4.615 ms 3.425 ms

5 sl-sj-2.sprintlink.net (4.0.1.66) 7.488 ms 38.804 ms 7.708 ms

6 144.232.8.81 (144.232.8.81) 6.560 ms 6.631 ms 6.565 ms

7 144.232.4.97 (144.232.4.97) 7.638 ms 7.948 ms 8.129 ms

8 144.228.146.50 (144.228.146.50) 9.504 ms 12.684 ms 16.648 ms

9 f5-0.inr-666-eva.berkeley.edu (198.128.16.21) 9.762 ms 10.611 ms 10.403 ms

10 f0-0.inr-107-eva.Berkeley.EDU (128.32.2.1) 11.478 ms 10.868 ms 9.367 ms

11 f8-0.inr-100-eva.Berkeley.EDU (128.32.235.100) 10.738 ms 11.693 ms 12.520 ms

Types of Servers:


Device Servers
A device server is defined as a specialized, network-based hardware device designed to perform a single or specialized set of server functions. It is characterized by a minimal operating architecture that requires no per seat network operating system license, and client access that is independent of any operating system or proprietary protocol. In addition the device server is a "closed box," delivering extreme ease of installation, minimal maintenance, and can be managed by the client remotely via a Web browser.

Print servers, terminal servers, remote access servers and network time servers are examples of device servers which are specialized for particular functions. Each of these types of servers has unique configuration attributes in hardware or software that help them to perform best in their particular arena.
Print Servers
Print servers allow printers to be shared by other users on the network. Supporting either parallel and/or serial interfaces, a print server accepts print jobs from any person on the network using supported protocols and manages those jobs on each appropriate printer.

Print servers generally do not contain a large amount of memory; printers simply store information in a queue. When the desired printer becomes available, they allow the host to transmit the data to the appropriate printer port on the server. The print server can then simply queue and print each job in the order in which print requests are received, regardless of protocol used or the size of the job.
Multiport Device Servers
Devices that are attached to a network through a multiport device server can be shared between terminals and hosts at both the local site and throughout the network. A single terminal may be connected to several hosts at the same time (in multiple concurrent sessions), and can switch between them. Multiport device servers are also used to network devices that have only serial outputs. A connection between serial ports on different servers is opened, allowing data to move between the two devices.

Given its natural translation ability, a multi-protocol multiport device server can perform conversions between the protocols it knows, like LAT and TCP/IP. While server bandwidth is not adequate for large file transfers, it can easily handle host-to-host inquiry/response applications, electronic mailbox checking, etc. And it is far more economical than the alternatives of acquiring expensive host software and special-purpose converters. Multiport device and print servers give their users greater flexibility in configuring and managing their networks.

Whether it is moving printers and other peripherals from one network to another, expanding the dimensions of interoperability or preparing for growth, multiport device servers can fulfill your needs, all without major rewiring.
Access Servers
While Ethernet is limited to a geographic area, remote users such as traveling sales people need access to network-based resources. Remote LAN access, or remote access, is a popular way to provide this connectivity. Access servers use telephone services to link a user or office with an office network. Dial-up remote access solutions such as ISDN or asynchronous dial introduce more flexibility. Dial-up remote access offers both the remote office and the remote user the economy and flexibility of "pay as you go" telephone services. ISDN is a special telephone service that offers three channels, two 64 Kbps "B" channels for user data and a "D" channel for setting up the connection. With ISDN, the B channels can be combined for double bandwidth or separated for different applications or users. With asynchronous remote access, regular telephone lines are combined with modems and remote access servers to allow users and networks to dial anywhere in the world and have data access. Remote access servers provide connection points for both dial-in and dial-out applications on the network to which they are attached. These hybrid devices route and filter protocols and offer other services such as modem pooling and terminal/printer services. For the remote PC user, one can connect from any available telephone jack (RJ45), including those in a hotel rooms or on most airplanes.
Network Time Servers
A network time server is a server specialized in the handling of timing information from sources such as satellites or radio broadcasts and is capable of providing this timing data to its attached network. Specialized protocols such as NTP or udp/time allow a time server to communicate to other network nodes ensuring that activities that must be coordinated according to their time of execution are synchronized correctly. GPS satellites are one source of information that can allow global installations to achieve constant timing.