Difference between revisions of "CCNP TSHOOT 642-832/Chapter 1"

From Teknologisk videncenter
Jump to: navigation, search
m (→‎Well Know Network Maintenance Models)
m (→‎FCAPS)
Line 72: Line 72:
 
|Log user activity
 
|Log user activity
 
|}
 
|}
−
 
+
=Identifying Common Maintenance Procedures=
 +
==Routine maintenance tasks==
 +
*Configuration Changes
 +
*Replacement of older or failed hardware
 +
*Scheduled backups
 +
*Updating Software
 +
*Monitoring network performance
 +
===Managing Network changes===
 +
*Who is responsible for authorizing network changes
 +
*Which tasks should only be performed during scheduled maintenance windows
 +
*What procedures should be followed prior making a change (Backup etc.)
 +
*What measurable criteria determine the success or failure of a network change
 +
*How will a network change be documented, and who is responsible for the documentation
 +
*How will a roll-back plan be created prior to the change.
 +
*Under what circumstances can formalized change management policies be overridden, and what authorization is required.
 +
===Maintaining Network Documentation===
 +
====Logical Topology Diagram====
 +
Shows the interconnection between network segments. The protocols used and how end users interface with the network. (No physical locations)
 +
====Physical Topology Diagram====
 +
Show how geographical areas - floors in a building - interconnect. The diagram reflects where various network components are physically located.
 +
====Listning of Interconnections====
 +
A listing of interconnections. Ports on which devices to where. Fx. in a spreadsheet. Circuit ID's for ISP connections might be included.
 +
====Inventory of Network Equipment====
 +
Manufacturer, model, version of OS, licensing organizational tag etc.
 +
====IP Address assignments====
 +
Document IP plan.
 +
====Configuration Information====
 +
When a configuration change is made the current configuration should be backup up. Have generations of backed up configurations. could be useful. Use a logical name system to the backups. (Date etc.) Also remember to backup software. (Versions etc.)
 +
====Original design Documents====
 +
Documents created during the initial design might provide insight in the decisions the designers made. Plans for future expansions etc.
 +
===Restoring after failure===
 +
*Duplicate hardware
 +
*OS and application software for the device. (Check licensing)
 +
*Restore backup from failed device.
 +
=The Network Maintenance Toolkit=
 +
==Basic Network Maintenance Tools==
 +
From very expensive to free tools. Vary in complexity.
 +
==CLI Tools===
 +
Cisco IOS CLI
 +
==GUI Tools== 
 +
*'''CCP:''' Cisco Configuration Professional
 +
*'''CCA:''' Cisco Configuration Assistant
 +
*'''CNA:''' Cisco Network Assistant
 +
*'''SDM:''' Cisco Security Device Manager
 +
==Backup Tools==
 +
Cisco IOS Backup
 +
=== Example 1: Backing up manually ===
 +
<source lang=cli>
 +
R1# <input>copy startup-config ftp://kevin:dj7jS@192.168.22.33</input>
 +
Address or name of remote host [ 192.168.22.33]?
 +
Destination file name [r1-confg]?
 +
Writing R1-confg !!!
 +
3458 bytes copied in 3.443 secs (1243 bytes/sec)
 +
</input>
 +
=== Example 2: Predefined ftp username/password===
 +
Define password
 +
<source lang=cli>
 +
R1# <input>configure terminal</input>
 +
R1(config)#<input>ip ftp username kevin</input>
 +
R1(config)#<input>ip ftp password dj7jS</input>
 +
</input>
 +
Backing up without specifying login credentials
 +
<source lang=cli>
 +
R1# <input>copy startup-config ftp://192.168.22.33</input>
 +
Address or name of remote host [ 192.168.22.33]?
 +
Destination file name [r1-confg]?
 +
Writing R1-confg !!!
 +
3458 bytes copied in 3.443 secs (1243 bytes/sec)
 +
</input>
 +
=== Example 3: Backing up automatically===
 +
Backup up every 1440 minuttes. 60*24=1440
 
<source lang=cli>
 
<source lang=cli>
 
!
 
!
−
ip ftp username hotbu
+
ip ftp username kevin
−
ip ftp password F8iJk
+
ip ftp password dj7jS
 
!
 
!
 
archive
 
archive
Line 82: Line 152:
 
  write-memory
 
  write-memory
 
  time-period 1440
 
  time-period 1440
 +
</source>
 +
Viewing
 +
<source lang=cli>
 +
R1#<input>show archive</input>
 +
The next archive file will be named ftp://192.168.2.33/R1-confg-4
 +
Archive #  Name
 +
  0
 +
  1      ftp://192.168.2.33/R1-confg-1
 +
  2      ftp://192.168.2.33/R1-confg-2
 +
  3      ftp://192.168.2.33/R1-confg-3 <- Most Recent
 +
  4
 +
  5
 +
  6
 +
  7
 +
  8
 +
  9
 +
  10
 +
  11
 +
  12
 +
  13
 +
  14
 
</source>
 
</source>
 
{{Source cli}}
 
{{Source cli}}
 
[[Category:CCNPv6]][[Category:CCNPv6 TSHOOT]]
 
[[Category:CCNPv6]][[Category:CCNPv6 TSHOOT]]

Revision as of 07:42, 6 June 2010

Introduction to Network Maintenance

understanding Maintenance Mode

Introducing network maintenance

  • Hardware and software installation and configuration.
  • Troubleshooting problem reports.
  • Monitoring and tuning network performance.
  • Planning for network expansion.
  • Documenting the network and any changes made to the network.
  • Ensuring compliance with legal regulations and corporate policies.
  • Securing the network against internal and external threats.

Proactive Versus Reactive Network Maintenance

  • Structured tasks: Performed as a predefined plan.
  • Interrupt driven tasks: Involve resolving issues as they are reported.

Well Known Network Maintenance Models

Maintenance models
Model Explanation
FCAPS Fault-, Configuration-, Accounting-, Performance- and Security management
defined by ISO
ITIL IT Infrastructure Library
Defines a collection of best-practice recommendations that work together to meet business goals.
TMN Telecommunications Management Network
ITU-T variation of FCAPS - See above - specially targeted towards Tele Communication Networks
PPDIOO Also called Cisco Lifecycle Services (See drawing below
PPDIOO Life Cyclus

FCAPS

FCAPS examples
Type of Management Examples of tasks
Fault Management Use network management software to collect information from routers and switches.
Send an E-mail alert when CPU utilization exceeds 80 percent.
respond to incoming trouble tickets from the help desk.
Configuration management Require logging of any changes to hardware or software configurations.
Implement a change management system to alert relevant personal.
Accounting management Invoice IP telephony users for their long distance and international calls
Performance management Monitor network performance for both LAN and WAN links
Deploy QoS to utilize limited WAN bandwidth.
Security management Deploy firewall, VPN and IPS technologies
Create a security policy dictating acceptable network use
Use AAA server to validate user credentials
Assign appropriate user privileges
Log user activity

Identifying Common Maintenance Procedures

Routine maintenance tasks

  • Configuration Changes
  • Replacement of older or failed hardware
  • Scheduled backups
  • Updating Software
  • Monitoring network performance

Managing Network changes

  • Who is responsible for authorizing network changes
  • Which tasks should only be performed during scheduled maintenance windows
  • What procedures should be followed prior making a change (Backup etc.)
  • What measurable criteria determine the success or failure of a network change
  • How will a network change be documented, and who is responsible for the documentation
  • How will a roll-back plan be created prior to the change.
  • Under what circumstances can formalized change management policies be overridden, and what authorization is required.

Maintaining Network Documentation

Logical Topology Diagram

Shows the interconnection between network segments. The protocols used and how end users interface with the network. (No physical locations)

Physical Topology Diagram

Show how geographical areas - floors in a building - interconnect. The diagram reflects where various network components are physically located.

Listning of Interconnections

A listing of interconnections. Ports on which devices to where. Fx. in a spreadsheet. Circuit ID's for ISP connections might be included.

Inventory of Network Equipment

Manufacturer, model, version of OS, licensing organizational tag etc.

IP Address assignments

Document IP plan.

Configuration Information

When a configuration change is made the current configuration should be backup up. Have generations of backed up configurations. could be useful. Use a logical name system to the backups. (Date etc.) Also remember to backup software. (Versions etc.)

Original design Documents

Documents created during the initial design might provide insight in the decisions the designers made. Plans for future expansions etc.

Restoring after failure

  • Duplicate hardware
  • OS and application software for the device. (Check licensing)
  • Restore backup from failed device.

The Network Maintenance Toolkit

Basic Network Maintenance Tools

From very expensive to free tools. Vary in complexity.

CLI Tools=

Cisco IOS CLI

GUI Tools

  • CCP: Cisco Configuration Professional
  • CCA: Cisco Configuration Assistant
  • CNA: Cisco Network Assistant
  • SDM: Cisco Security Device Manager

Backup Tools

Cisco IOS Backup

Example 1: Backing up manually

R1# <input>copy startup-config ftp://kevin:dj7jS@192.168.22.33</input>
Address or name of remote host [ 192.168.22.33]? 
Destination file name [r1-confg]?
Writing R1-confg !!!
3458 bytes copied in 3.443 secs (1243 bytes/sec)
</input>
=== Example 2: Predefined ftp username/password===
Define password
<source lang=cli>
R1# <input>configure terminal</input>
R1(config)#<input>ip ftp username kevin</input>
R1(config)#<input>ip ftp password dj7jS</input>
</input>
Backing up without specifying login credentials
<source lang=cli>
R1# <input>copy startup-config ftp://192.168.22.33</input>
Address or name of remote host [ 192.168.22.33]? 
Destination file name [r1-confg]?
Writing R1-confg !!!
3458 bytes copied in 3.443 secs (1243 bytes/sec)
</input>
=== Example 3: Backing up automatically===
Backup up every 1440 minuttes. 60*24=1440 
<source lang=cli>
!
ip ftp username kevin
ip ftp password dj7jS
!
archive
 path ftp://192.168.2.33/R1-config
 write-memory
 time-period 1440

Viewing 

R1#<input>show archive</input>
The next archive file will be named ftp://192.168.2.33/R1-confg-4
 Archive #  Name
   0
   1       ftp://192.168.2.33/R1-confg-1
   2       ftp://192.168.2.33/R1-confg-2
   3       ftp://192.168.2.33/R1-confg-3 <- Most Recent
   4
   5
   6
   7
   8
   9
   10
   11
   12
   13
   14
Retrieved from "http://mars.merhot.dk/w/index.php?title=CCNP_TSHOOT_642-832/Chapter_1&oldid=12235"