Embed
Email

netcourses.tech.purdue.educit443DatalecturesLe...

Document Sample

Shared by: ewghwehws
Categories
Tags
Stats
views:
0
posted:
2/1/2012
language:
pages:
19
CIT 443: Enterprise Network Management





FCAPS: Configuration Management

Definition of

Configuration Management



Configuration management is the

process of obtaining functional data

from each network device, storing and

documenting that data, and

subsequently utilizing that data to

manage the operations of all network

devices



Fall 2007 2

Why Configuration Management?



 Systems are as complex as they have

ever been

 Networked systems must be configured

properly in order to function properly

 Usually means the default configuration is

not sufficient

 Managing how these devices are

configured and documenting these

configurations is extremely important

Fall 2007 3

Configuration Management Activities



 Gather network configuration

information – How?

 Store the data in redundant locations

 Why?

 Use configuration information to identify

& make necessary configuration

changes

 Produce configuration reports

 non-compliance reports

Fall 2007 4

Network Design Aspects of CCM



 Initializing the network

 Design and Implementation

 Maintaining, adding and updating the

relationships between components

 Graceful shut-down of the network

 Others?





Fall 2007 5

Configuration Management Functions

1. Network Topology Control

2. Network Provisioning

 Progress of New Equipment Installations

 Progress of New Service Configurations

3. Inventory Management

4. Version Control

 Device Configuration

 Firmware Version

5. Configuration Control

 Local

 Remote

6.

Fall 2007

Network Documentation! 6

Expectations of

Configuration Management



Users:

 Informed of changes in configuration

 Scheduled downtime & periodic reports

 Rapid response/resolution of problems

Network Engineers:

 Predefined configuration attributes

 Standardized protocols and interoperability

Network Administrators:

 Change connectivity of network as required

Fall 2007  Users are unable to change configurations 7

Configuration

Management Information

Network Maps:

 Documents physical & logical network design

 Should be used as “background” for a fault management

system

 Other Information?

Software Inventories:

 Licensing Information

 Support Contract/Contact Information

 Other Information?

Hardware Inventories:

 Make/Model

 Serial Number

 Property Accounting Tag Number

 Support Contract/Contact Information

Fall 2007 8

 Other Information?

Configuration

Management Benefits

 Rapid access to vital configuration data

 Disaster Recovery

 Improved Fault Resolution

 Framework for updating

connectivity/communications between

devices

 Quickly determine how many devices of

a certain type of are on the network

 Bug Fixes

 Upgrades/Updates

 2007

Fall

Other Benefits? 9

Configuration Management:

Manual Device Discovery

 Time consuming and inaccurate

 Missing nodes

 Will you be current when you’re done?

 Touch every node and collect the data

 New devices?

 Geographically disparate systems?

 Large networks?

Fall 2007 10

Configuration Management:

Automatic Device Discovery

 Passively listen for stations

 Not as intrusive to users or BW intensive

 Incomplete and least accurate of

automated methods

 Likely more accurate than manual methods

 Passively listen to switched connections?

 Security Risk?





Fall 2007 11

Configuration Management:

Automatic Device Discovery

 Ping and query all addresses within

range

 Potentially Disruptive

 BW Intensive

 Find a single device then use a

management protocol to ask it who it

has talked to recently

 Nmap/Nessus/Netstat



Fall 2007 Arpwatch 12

Configuration Management via SNMP



SNMP “Public” Community:

 Gather information about the current network

environment

 Read-Only

 Password Required/Often Disabled

 Default is “public”





SNMP “Private” Community:

 Gather information about the current network

environment AND make changes

 Read-Write

 Password Required – Change from Default!

Fall 2007 13

Other Relevant Protocols



 Telnet/SSH

 TFTP/FTP

 CORBA

 TL1

 SS7

 Others?



Fall 2007 14

Configuration Management –

Network Elements

 PBX

 Hubs

 Routers

 Switches

 Servers

 Workstations

 Firewalls

 Wireless Access Points

 Printers

 Power Management Systems

 Network SCADA Systems

 Temperature Management Systems (HVAC)

 Physical Security Systems

 Home Appliances?

 Others?

Fall 2007 15

Key Players

 HP (OpenView)

 Cisco (CiscoWorks)

 IBM (Tivoli)

 SolarWinds

 AlterPoint (Device Authority Suite)

 Voyence (VoyenceControl!)

 SpectrumSoft (WNMS)

 Micro2000 (RemoteScope)

 Compuware (Vantage Solution Suite)

 Others?

Fall 2007 16

Industry Trends

 Automated Configuration Backup

 Automated Configuration Updates

 Redundant Configuration Management Systems

 Mirror Sites and Redundant NOC(s)

 Configuration Replication – “ghosting”

 Others?









Fall 2007 17

Topics for Further Investigation



1. Configuration Management Protocols for Telecomm Networks

2. Configuration Management System Architectures

3. Disaster Recovery Planning – Best Practices and Lessons Learned

4. Corporate Implementations of Configuration Management Systems

5. Change Management Policies, Practices and Enforcement

6. IT Infrastructure Library & Service Management









Fall 2007 18

Reading



 There are two Change &

Configuration Management (CCM)

Whitepapers posted to the course

website.

 Read them for next time









Fall 2007 19



Other docs by ewghwehws
By registering with docstoc.com you agree to our
privacy policy

You are almost ready to download!

You are almost ready to download!