chapter 1: pl i m i fplanning maintenance for complex · pdf filepl i m i fplanning...
TRANSCRIPT
Chapter 1:Pl i M i fPlanning Maintenance for Complex Networks
CCNP TSHOOT: Maintaining and Troubleshooting IP NetworksCCNP TSHOOT: Maintaining and Troubleshooting IP Networks
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco PublicTSHOOT v6 Chapter 1
1
Chapter 1 Objectives
Evaluate commonly-practiced models and methodologies for network maintenanceg Identify the processes and procedures that are a
fundamental part of any network maintenance methodologymethodology Identify, evaluate and select tools, applications and
resources to support network maintenance processespp p
Chapter 12© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Maintenance Models and Methodologies
A network engineer’s job description can include tasks related to: Device installation and maintenance Failure response Network performance Business procedures
S it Security
Chapter 13© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Benefits of Structured Maintenance over Interrupt driven MaintenanceInterrupt-driven Maintenance
Proactive vs. reactive Reduced network downtime More cost effective
B tt li t ith b i bj ti Better alignment with business objectives Improved network security
Chapter 14© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Maintenance Models and Organizations
IT Infrastructure Library (ITIL) ISO – FCAPSISO FCAPS
• Fault management• Configuration management
A i• Accounting management• Performance Management• Security Managementy g
ITU-T - Telecommunications Management Network (TMN)C f S OO Cisco Lifecycle Services Phases – PPDIOO (Prepare, Plan, Design, Implement, Operate, and Optimize)
Chapter 15© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
The Configuration Management element of th FCAPS d lthe FCAPS model
Chapter 16© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Network Maintenance Processes and P dProceduresA network maintenance plan includes procedures for the following tasks: Accommodating Adds, Moves, and Changes Installation and configuration of new devicesInstallation and configuration of new devices Replacement of failed devices Backup of device configurations and software Troubleshooting link and device failures Software upgrading or patching Network monitoringg Performance measurement and capacity planning Writing and updating documentation
Chapter 17© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Network Maintenance Processes and P dProceduresNetwork maintenance planning includes:p g Scheduling maintenance Formalizing change control procedures Establishing network documentation procedures Establishing effective communication
D fi i l / d / i Defining templates/procedures/conventions Planning for disaster recovery
Chapter 18© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Network Maintenance Tools, Applications, and ResourcesResources
Console TFTPConsoleSSHTelnet
FTPSCPHTTP(S)
CLI BackupsCLI mgmt
Syslog
HTTPHTTPST l t
NTP
SyslogGUI mgmt
Chapter 19© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
TelnetSSH Time Logging
NTP Example
(Selected output from the running config)
service timestamps debug datetime msec localtime show-timezoneservice timestamps log datetime localtime show-timezone!clock timezone PST -8clock summer-time PDT recurring 2 Sun Mar 2:00 1 Sun Nov 2:00!ntp server 10.1.220.3p
Chapter 110© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Cisco Configuration and Documentation Tools
Dynamic Configuration Tool• Aids in creating hardware configurations• Verifies compatibility of hardware and software selected• Produces a Bill of Materials (BoM) with part numbers Cisco Feature Navigatorg
• Quickly finds Cisco IOS Software release for required features SNMP Object Navigator
• Translates SNMP Object Identifiers (OID) into object names• Translates SNMP Object Identifiers (OID) into object names• Allows download of SNMP MIB files• Verify supported MIBs for a Cisco IOS Software versionCi P C l l t Cisco Power Calculator• Calculates power supply requirements a PoE hardware configuration• Requires CCO login
Chapter 111© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Logging Services
Logging severity levels on Cisco devices: (0) Emergencies( ) g (1) Alerts (2) Critical (3) Errors (3) Errors (4) Warnings (5) Notifications (6) Informational (7) Debugging
Enabling logging for a lower level (from importance point of view) will enable logging for all the above levels.
Chapter 112© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Logging to a Server
Messages are logged to!logging buffered 16348
a circular log buffer in RAMthat is limited to 16384 Bytes.
logging buffered 16348!logging console warnings!logging 10.1.152.1
Logging messages on the console arelimited to level 4 and lower. By defaultall messages from level 0 (emergencies)
logging 10.1.152.1!
all messages from level 0 (emergencies)to level 7 (debugging) are logged.
Messages are logged to a syslog server at IPAddress 10.1.152.1. By default all messagesExcept level 7 are sent.
Chapter 113© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Network Monitoring and Performance Measurement ToolsMeasurement Tools Capacity planning Diagnosing performance problems SLA compliance
Chapter 114© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Implementing Backup and Restore Services using FTP
Copy using FTP with specified username and passwordR1(config)# ip ftp username backupg p p p
R1(config)# ip ftp password san-fran
R1(config)# exit
R1# copy startup-config ftp://10.1.152.1/R1-test.cfg
Address or name of remote host [10 1 152 1]?Address or name of remote host [10.1.152.1]?
Destination filename [R1-test.cfg]?
Writing R1-test.cfg !
2323 bytes copied in 0.304 secs (7641 bytes/sec)
Copy using FTP with stored username and passwordR1# copy startup-config ftp://backup:san-fran@10 1 152 1/R1-test cfgR1# copy startup-config ftp://backup:[email protected]/R1-test.cfg
Address or name of remote host [10.1.152.1]?
Destination filename [R1-test.cfg]?
Writing R1-test.cfg !
Chapter 115© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
2323 bytes copied in 0.268 secs (8668 bytes/sec)
Implementing Backup and Restore Services using ArchiveArchive Setting up the configuration archiveR1(config)# archive( g)
R1(config-archive)# path flash:/config-archive/$h-config
R1(config-archive)# write-memory
R1(config-archive)# time-period 10080
show archive command output R1# show archive
There are currently 3 archive configurations saved.
The next archive file will be named flash:/config-archive/R1-config-4
Archive # Name
0
1 flash:/config-archive/R1-config-1
2 flash:/config-archive/R1-config-2
Chapter 116© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
5 flash:/config-archive/R1-config-3 <- Most Recent
Implementing Backup and Restore Services using configure replaceusing configure replaceR1# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)# hostname TEST
TEST(config)# ^Z
TEST# configure replace flash:config-archive/R1-config-3 list
This will apply all necessary additions and deletionsThis will apply all necessary additions and deletions
to replace the current running configuration with the
contents of the specified configuration file, which is
assumed to be a complete configuration, not a partial
fi ti E t Y if t t d ? [ ]configuration. Enter Y if you are sure you want to proceed. ? [no]: yes
!Pass 1
!List of Commands:
no hostname TEST
hostname RO1
end
Total number of passes: 1
Rollback Done
Chapter 117© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
o bac o e
Disaster Recovery Tools Successful disaster recovery is dependent on the existence of the following: Up to date configuration backups Up to date software backups Up to date hardware inventories Up to date hardware inventories Configuration and software provisioning tools
Chapter 118© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Chapter 1 Summary Advantages of a structured network maintenance model over interrupt-driven
include reduced network downtime and higher network security. Examples of structured network maintenance methodologies include ITIL Examples of structured network maintenance methodologies include ITIL,
FCAPS, TMN and Cisco Lifecycle Services (PPDIOO). Network maintenance plans include procedures for adds/moves/changes,
software upgrades and replacement of failed devicessoftware upgrades and replacement of failed devices. Network maintenance planning includes maintenance scheduling,
documentation development, templates/procedures/conventions definition and disaster recovery planning.y g
Network documentation includes network drawings, connections, equipment lists, IP address administration, device configurations and design documentation.
When a device fails, disaster recovery requires that replacement hardware, software, configuration files and transfer tools be available.
Chapter 119© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Chapter 1 Summary – Cont. The basic components of a network maintenance toolkit include CLI and
GUI device management tools as well as backup, log and time servers.Ci b b d t l d D i C fi ti T l Cisco web-based tools and resources: Dynamic Configuration Tool, Cisco Feature Navigator, SNMP Object Navigator and Cisco Power Calculator.M i ti ti f i t k f it Main motivations for measuring network performance are capacity planning, diagnosing performance problems and SLA compliance.
TFTP, FTP, SCP, HTTP, and HTTPS can be used to transfer files b t t k d b k d i FTP SCP HTTP d HTTPSbetween network and backup devices. FTP, SCP, HTTP, and HTTPS are more secure than TFTP as they require authentication. SCP and HTTPS are most secure because they also incorporate encryption.Th fi ti hi i f t b h l f l i ti The configuration archiving feature can be helpful in creating configuration archives, either locally on a remote server (introduced with IOS Release 12.3(7)T).
Chapter 120© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Chapter 1 Labs
There are no labs for this chapter.
Chapter 121© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public
Chapter 122© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public