08.02.2015 Views

Syngress - Eleventh Hour Network+ Exam N10-004 Study Guide (11 ...

Syngress - Eleventh Hour Network+ Exam N10-004 Study Guide (11 ...

Syngress - Eleventh Hour Network+ Exam N10-004 Study Guide (11 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuration Management 145<br />

should include as many specifics as possible. Information included in a database<br />

or series of documents may include the following:<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

The device asset number<br />

The name of the device<br />

The Internet Protocol (IP) address<br />

The Media Access Control address<br />

The make, model, and model number<br />

The serial number and product ID<br />

The location of the device<br />

The person who has been issued the device<br />

The purchase date<br />

The warranty information and details<br />

The operating system and service pack information<br />

Amount of physical memory installed<br />

The number of processors and their type and speed<br />

The number of hard disks and their size, type, and speed<br />

Software information<br />

There are a number of methods and tools available to help you acquire most<br />

of the information to be included in your database, but other information can<br />

be acquired using various configuration utilities. These tools include but are not<br />

limited to ipconfig, ifconfig, winipcfg, and ping.<br />

Change Control Documentation<br />

One of the benefits of compiling information about devices on your network is<br />

that it can allow you to see those devices which will be affected by a network<br />

change. Change control documentation provides a record of changes that have<br />

been made to a system, which can be used in troubleshooting problems and<br />

upgrading systems.<br />

DID YOU KNOW<br />

When you are creating a change control document, at a minimum you should document<br />

the following:<br />

1. Describing the change to be made<br />

2. Explaining why this change is required<br />

3. Outlining how the change is to be implemented and detailing the steps to be<br />

performed<br />

4. Documenting a rollback strategy<br />

The procedures you document are a valuable resource when you are recovering from a<br />

disaster and/or need to install another device or software in the same manner.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!