CertDoctor

Unless I get a lot of comments or Red Bulls I’m probably not going to update the Network+ Notes at this time and instead focus on presenting my notes and insights on the CTT+ exam first. I could however probably be talked into releasing my old Network+ notes. Thanks for the feed back and below is a sample of my old notes.

Sample of Notes: (Outline Components come from the Original Outline from CompTIA)

I.1.3 Associate IPX, IP, and NetBEUI with their functions.
IPX- (Internetworking Packet Exchange) Is part of the SPX/IPX protocol suite designed by Novell. It is a routable and connectionless oriented protocol. This protocol operates at the Networking layer of the OSI model and is responsible for addressing for nodes using SPX/IPX suite. IPX addressing is always dynamic and can not be manually configured because the address is partly composed based on the NIC’s (Network Interface Card) MAC (Media Access Control) number, the network number, and the socket number. When conflicts arise due to MAC address duplication on the network the network card will need to have its MAC address reconfigured. Contact the manufacture.
IP- (Internet Protocol) is part of the TCP/IP suite. This to is a connectionless oriented protocol.

I.1.4 Define the following terms and explain how each relates to fault tolerance or high availability:
• Mirroring
Mirroring- is duplication of a drive namely from one to another. This allows for one drive to fail and for the other mirrored drive to take over. Keep in mind mirroring only uses one disk controller so if the controller burns out you have a problem. First supported by RAID(Redundant Ray of Independent Disks) 1. (RAID will be explained shortly.)
• Duplexing
Duplexing- Simply put it is mirroring with a second disk controller. So that not only do you have fault tolerance on your drives but also for your controllers. Supported first by RAID level 1.
• Striping
Striping- This process only improves performance by itself. Striping allows for a volume of data to be spread out across multiple drives in by breaking it. Until striping a volume across multiple drives meant that each drive had to be filled up in order. So only one set of Read/write heads was active at one time, but with striping all read/write heads are active which improves overall speed. This striping only helps with fault tolerance when used with parity. RAID level 2 first supported data striping with a drive dedicated to parity information. (A brief explanation of
• Volumes
Volumes- Is a defined section of disk space. This can include a portion of a disk, the entire disk, or multiple disks. These are then given logical names for your convience such as (C,D.E drives and etc.).
• Tape backup
Tape backup- Oldest and most common form of removable backup media. Pros- simple to use, inexpensive, and high capacity. The following is a list of common types of tapes used and there storage capacity.
QIC 100MB+
DOS Cartridges for DAT drives 1GB+
DLT 35GB+
AIT 25GB,50GB
Types of backups are as follows with an explanation.
*Full- Simply backups up all data on a drive(s) specified. Note: takes the longest period of time to backup or restore. If multiple tapes are going to be needed an autoloader(such as a DAT autoloader) that loads to tapes after each is filled could be useful. Verse, having someone come by the station every few hours and see if a new tape is needed.
*Differential- This is used in conjunction with a full backup. A differential backup simply backups all files that have modified since the last full backup. The archive bit is utilized by the NOS to indicate the appropriate files to be backed up. During a full backup all files have their archive bit cleared.
*Incremental- This is used in conjunction with a full backup. A incremental backup backups all files that have changed since the preceeding full backup or incremental backup. Thus it backups all files that have changed then it clears those files archive bit.
***Usually all three methods are used together but they can be.
For simplicity here is what your would do if you needed to restore a server. Left to right indicates which to to restore first.
/Full Restore while using (full & incremental backups)
Full + All Incrementals up to the date of crash = Full Restore
/Full Restore while using (full & differential backups)
Full + Most recent Differential = Full Restore
/Full Restore while using (full, differential, & incremental backups)
Full + All incrementals + differential if it was the most recent backup = Full Restore

——-
“Computers are useless. They can only give you answers.”
-Pablo Picasso

This exam has changed since I took it but I plan on incorporating the new objectives into my FREE training. Here’s the basics.

This certification is for IT Professionals who want to specialize in networking technologies. It basically certifies you as a network technician and a entry level network admin. You’ll learn cabling, protocols, server layouts, security implementations, and much more. Check out more about the cert.

http://www.comptia.org/certifications/listed/network.aspx

Here’s my goal. I want to become a technical trainer.. In other words make a living off training others to become certified professionals. Still working on the CTT+ and MCT and that sort of stuff. But I thought Hey why not get a head start. A few years ago I made a step by step guide for the Network+ exam its gone through some changes since. But I figured I can make a few updates and post in segments on my blog right here. So enjoy… Here’s a sample.

(Bear in Mind the bold text is commentary and the outline is taken from an old objectives guide from CompTIA)

I.1 Basic Knowledge 18%
I.1.1 Demonstrate understanding of basic network structure, including:

• The characteristics of star, bus, mesh, and ring topologies, their advantages and disadvantages,

Topologies-

*Star- Each node has a connection to the hub or to a MAU which sends data to different physical segments according the type of network.  Hub is often seen in Ethernet in which it acts as a multi-port repeater.  A MAU (Multi-station Acces Unit) is seen in token-ring networks and uses the star topology as though it was a physical ring, by sending information to each segment sequentially until the right station grabs the token. Pros- If a segment fails the network doesn’t only that node losses communication. Reconfiguring is easy. Cons- Hub dies so does the network.  Cost is a higher verse Bus.

*Bus- All nodes are connected to the same physical media (Usually COAX).  Thus by broadcasting on this media all other nodes on this physical segment receive the information without need for a hub.  Note: when using COAX terminators will need to be used.  Pros- Simple installation and uses less cable thus it cuts down on expense.  Cons-  The main cable itself can can be the point of failure thus Bus topology has a low fault tolerance.  To find a fault in the cable use a TDR (Time Domain Reflectometer).

*Mesh- A physical path exists between all components on the network.  Often seen in mainframes that require clustering and not only require fault tolerant servers but also physical media.  A cable goes bad you can still route the information several other ways.  Formal: For every N stations you will have X number of connections N(N-1)/2=X. Pros- High degree of fault tolerance.  Cons- Very expensive to employ.

*Ring- A physical path exists between nodes to form a ring.  Sometimes the ends of the rind don’t physically connect but use a wireless technology to communicate.  Pros- Simple to troubleshoot since data flows in a sequential (station to station) manor.  Cons- Practically no fault tolerance if the ring is damaged the network will most likely crash.

• The characteristics of segments and backbones
  *Segments- In relation to a intranet work with a backbone a segment is a branch off the main backbone that contains nodes.  When talking about physical characteristics of a network a segment is a media that can allow for two nodes to take to each other from one end to another without a hub, repeater, or router (hence Minimum Segment length Standards).

*Backbones- A high-speed media that connects many segments.  A backbone is also often connects two or more LANs over great distances thus creating a WAN.

I.1.2 Identify the following:

• the major network operating systems, including Microsoft Windows NT, Novell NetWare, and Unix,

*Microsoft Windows NT- (Servers WWW, FTP, DNS, etc.) NT looks like a MAC server when enabled for file/print sharing on a MAC network.  Can run text-mode OS/2 programs.  NT can communicate with NetWare(NW) Servers using GSNW, CSNW, FPNW and DSMN.  GSNW(Gate-Way Services for NW) allows for a NT client to talk through a NT Server to a NW Server.  CSNW(Client Services for NW) allows for a NT client to talk to a NW Server for file/ print services.  FPNW(File and Print Services for NW) allow for a NT Server to act as though it was a File or Print Server running NW.  FPNW is often used when migrating a network from NW to NT. DSMN(Domain Services Manager for NW) allows a NT server to not only interact with a NT SAM database (soon to be discussed) but also with NDS(NW Domain Services) database and the old NW bindery.  NT can run 16-bit DOS applications and 32-bit Win 95/98 programs.  When using NT the goes from workgroups to domains.  NT Workstations supports workgroups.  A NTDS(NT Domain Services) allows for a network not server based database for usernames and passwords which are stored in SAM(Security Accounts Manager).  In a NT server environment only the PDC(Primary Domain Controller) can edit the SAM.  Other NTDS servers only contain a backup copy these servers are called BDCs(Backup Domain Controllers).  Thus if the PDC is down a BDC can replace it.  Minimum requirements for NT are a 486 CPU, 128MB Hard Drive space ,and 16MB RAM.  Note: NT supports intel, Alpha, MIPS, and Motorola processors.(No SPARC SUPPORT)

*NetWare(NW)- Newest version NW5 supports up to 32 CPUs(Intel Spec. 1.1 & 1.4) and hot-plug & play PCI cards.  NW Server’s can communicate with the following platforms Win 95/98/NT, MAC, VMS, OS/400, and Unix.  The NW server gives the appearance of actually being of the corresponding Platform that it is communicating with.  NW uses NLMs(NW Loadable Modules) to enable different functions on the server just as NT uses .DLL(Dynamic Link Library) and .EXE files.  These NLMs come in primarily four categories Disk Drivers, LAN Drivers, Name Space Modules, and Utilities.  Disk Drivers on older versions of only used .DSK extensions but new versions also implement .CDM and .HAM extensions.  (Example: on NW5 two drivers commonly used for IDE interfaces include IDEATA.HAM & IDEHD.CDM on NW3.x IDE.DSK is used)  The second major category LAN Drivers use .LAN extensions and are utilized for NICs.  Name Space Modules allow for a NW server to store different platform’s files on a NW server, the modules have a .NAM ext.  A name space gives the file on the NW server a standard 8.3 DOS name set to the other platform’s files so that the NW server can manage it.  (Example if you wanted your NW file server to store MAC files so that MACs on a network could access them you would load MAC.NAM)  While the name space on the NW server would have to conform to a 8.3 DOS set name the file would appear to be the same to platforms that use it across a network.  Utility NLMs are the most used and are the misc. of NLMs.  They include extensions such as .NLM(Misc. stuff) and .PSM(used for Multi-Processsor Systems).  NW4.x and later started using NDS(NW Domain Services) which is X.500 based.  In short it allows for a database that is network-centric.  You can set up permissions for a user across multiple servers using one database.  This is unlike NW3.x NOSs(Network Operating Systems) which used a server-centric database called a bindery.  So if you had a user that need multi-server permissions you would have to setup a user name and password on each NW server’s individual bindery.  Notably older versions of NW were mainly IPX/SPX based in their protocol.  While NW5 employs TCP/IP native.  NW5 no longer includes a client for DOS, but is fully intergrated with Win 95/98, and replaces NT login with a NW login screen.  OS/2 clients are not included on the packaged CD either.  In order to get a client for a MAC OS to login to a NW server you would have to go to www.prosofteng.com/nw4mac/ . Minimum requirements Pent. CPU/ 600MB Hard Drive Space/ 64 MB RAM.

*Unix/Linux- TCP/IP Native.  All Linux compiled versions are suppose to come with source code.  RedHat Linux supports Intel, Alpha, and SPARC processors.  Unixware was originally designed by Novell but has been sold to was IPX/SPX and TCP/IP ready.  Slackware Linux Intel based supports up to 16 processors at one time.  What ever flavor you want it exists if not have it written.  Unix/ Linux NOSs are very fast and stable.  (The server backbone of the internet).  Any POSIX(Portable OS Interface) program should run, a IEEE standard.  Unix and Linux allow for command line interface and GUI support through X-Windows.

• the clients that best serve specific network operating systems and their resources,

In short if possible use the corresponding servers supplied client by that NOS’s manufacture.

• the directory services of the major network operating systems.

Basically already mentioned- Brief overview.

*Windows NT- Uses a network-centric Database.  Which allows for a user name and password to be set up across multiple servers using a single database.  The Database called a SAM can only be edited by the PDC.  If the PDC crashes a BDC can be enabled to take over its position.  After a PDC is updated soon after the BDCs are updated which also are used as reference points for a user logging in.  So the PDC need not be operational for a user to log in but only for a ADM to edit the accounts.  Workstations can support workgroups but only a NT server can support domains which requires it to be enabled as a NTDS server.  To edit users rights use User Manager (Workgroups) or User Manager for Domains(Domains).

*NetWare- 3.x uses the old server-centric Bindery.  While 4.x uses the new NDS network-centric database.  Note: NDS can be supported across some Unix versions and used with NT using DSMN.  To edit such databases it is usually best to have NW client installed on your machine.  Here is a list of .EXEs that allow for editing of NDS or Bindery using a Win 95/98/NT system.  OS/2 can access similar functions when running DOS or Windows.