1 / 24

Maintaining the Network

Maintaining the Network. 17. Monitoring the Network. Network systems need to be constantly monitored to: Determine when failures occur To predict possible or imminent failure Activity can be monitored, recorded, and expressed statistically to predict failure

ketan
Télécharger la présentation

Maintaining the Network

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Maintaining the Network 17

  2. Monitoring the Network • Network systems need to be constantly monitored to: • Determine when failures occur • To predict possible or imminent failure • Activity can be monitored, recorded, and expressed statistically to predict failure • Predictions are based on system history

  3. Baseline Should be established immediately after the network or server is installed Should be routinely collected and reviewed to predict events that could affect network or server performance

  4. Network Baseline Information Peak utilization—Should not exceed 80% Average utilization—Should not exceed 40% Frame size peak and frame size average—Size affected by protocol and equipment used, amount of segment traffic, and type of data transmitted Number of protocols—Large number can indicate an improperly configured network device

  5. Network Baseline Information (Cont.) Number of nodes—Number of nodes communicating on the network segment Most active 10 nodes—Indicator of possible network problem locations Collisions—Primary indicator of a problem Packets dropped—Good indication there is a cable or connection problem

  6. Traffic Shaping Techniques Routers or layer 3 switches can be installed to provide additional segment links Multiple segment paths can increase network reliability provided by link redundancy

  7. Network Bottlenecks • Can be caused by servers and devices • Insufficient resources • Solution: Add more RAM or configure more hard disk drives and map users to additional drives • Unbalanced client loads • Solution: Change default server logon for users • Incorrectly configured service(s)

  8. Server Baseline Memory utilization and swap file activity—Determine if more RAM needs to be installed Hard disk activity—Determines if additional hard drives need to be installed CPU utilization—Should not exceed 85%

  9. Performance Monitor Provides administrator with information needed for making objective decisions about the system Can be configured to send alerts to the administrator when resources are critical Can be used to predict system failure or to isolate cause of the poor performance

  10. Performance Monitor Display

  11. Windows Task Manager Provides a quick view of system performance Can show what software applications, processes, and services are running

  12. Resource Monitor

  13. Microsoft Network Monitor Can be used to establish a baseline Displays all active network connections Collects frames in similar manner to protocol analyzers Filters can be applied to specific protocol types or contents Identifies fewer protocols than network analyzer

  14. Microsoft Network Monitor Display

  15. Event Viewer • Records events that occur on computer, such as: • Starting and stopping of a service • User logon activities • Share access • File access • Hardware and software information • Excellent utility for troubleshooting system failures

  16. Event Viewer Display

  17. Maintaining System Integrity To protect data, fault tolerance and disaster recovery must be designed into the network Fault tolerance includes some RAID systems and electrical power systems Disaster recovery includes data backups; hot and cold spares; and hot, warm, and cold sites

  18. RAID 1 RAID 1 consists of two disk drives with matching data on each drive

  19. RAID 5 RAID 5 combines parity and striping At least three hard disk drives are needed for a RAID 5 configuration

  20. Backup Data Methods Full backup—Only data needs to be copied Archive bit is set on files when a full or incremental backup is performed Archive bit is not reset when a differential backup is performed or when copy and xcopy commands are used

  21. Incremental Backup Less time than full backup Full backup is performed first, followed by daily incremental backups To restore, full backup is restored first, followed by daily incremental backups Incremental backups must be restored in sequence

  22. Differential Backup Performed on days when full backup is not being performed Perform a full backup first, followed by daily differential backups To restore, full backup is restored first, then the last differential backup

  23. Storing Backup Data • Store data backups • Off-site • In a secure area with limited access • In a climate-controlled storage area • Avoid storing backups • In direct sunlight • Near electrical panels or in equipment rooms • Near magnetic fields generated by electrical equipment

  24. In class lab Roberts Labs 96,79,83, Next Class Labsim Homework 8.7.1-8.7.5

More Related