network management

  1. Reference Models
    What belongs together and its an abstract thought process.
  2. Fault
    • Fault management is concerned with monitoring the network to ensure that everything is running smoothly and reacting when this is not the case.
    • A large amout of time
  3. Management of alarms
    is the most important aspect of network monitoring.

    • know if switch goes down not all pc
    • Send alarms to a pager or send text message
  4. Filtering
    • Event –By device or by severity level or both
    • duplicate alarms- maintain history
  5. Proactive Fault Management
    recognizes patterns of alarms caused by minor faults that point to impending bigger problems
  6. Trouble Tickets
    helps track problems
  7. Configuration
    Perform operations that will deliver and modify configuration settings to equipment in the network
  8. Configuration Management Functions
    Configuring managed resources, whether they are network equipment or services running over the network
  9. Auditing
    Retrieving information from a device already known to exist
  10. Discovery
    Using software to see what is in the network
  11. Synchronization
    • The network itself
    • Management system’s view of the network
    • Views should be the same
  12. Backup and Restore
    your user data is the configuration data of your network
  13. Image Management
    • New feature releases or patches
    • (bug fixes)
    • You need to be able to keep track of which software images are installed
  14. Accounting
    Collect usage data is based on volume, duration, and/or quality
  15. Fraud detection
    with tracking down and preventing theft of communication services
  16. Performance
    Throughput, measured by a number of units of communication performed per unit of time.
  17. Quality Measurement
    • At the application layer for a web service, the number or
    • percentage of web requests that could not be serviced. Will be low
  18. Security of management
    • Set up proper processes and procedures to ensure orderly operations
    • Intrusion detection and prevention
  19. Operations
    the day-to-day running of the network
  20. Administration
    • required to manage the network and that do not involve performing changes (configuring, tuning) to the
    • running network itself.
  21. Maintenance
    the network andcommunication services operate as they are supposed to. This involves diagnosing, troubleshooting, and repairing
  22. Provisioning
    proper setting of configuration parameters on the network so that the network functions as expected
  23. Telecoms Operations Map (TOM)
    • has the concept of a management lifecycle at its center
    • lifecycle stages
    • –Fulfillment—Assurance—Billing
    • (FAB).
  24. Fulfillment
    a service order that was received from a customer is carried out properly
  25. Assurance
    all activities required to ensure that a service runs smoothly after it has been fulfilled.
  26. Billing
    sure that the services provided and resources consumed are accounted for properly and can be billed to the user.
  27. WAN issues
    • Congestion
    • TCP/IP protocol weakness
  28. Bandwidth upgrades increase costs but fail to
    permanently increase performance.
  29. Compress Everything Issues
    • Can enhance the wrong applications
    • Can actually reduce throughput
  30. Router Queuing Weaknesses
    • Cannot detect congestion until after it has occurred
    • Bydefinition, packets wait in line, which can result in retransmissions
  31. Acceleration
    • Appropriate compression
    • Best algorithm is different for different types of traffic
  32. TCP treats all traffic equally
    • Best effort
    • Packet retransmission can contribute to WAN congestion
    • UDP doesn’t manage an End-to-End connection
  33. Compression
    • 4:1 compression ratio for
    • some measurable amount of traffic
  34. Traffic Policing
    • Traffic policing propagates bursts.
    • Throw away slower traffic first
  35. Traffic Shaping
    retains excess packets in a queue and then schedules the excess for later transmission over increments of time
  36. Packeteer
    a packet/traffic shaper
  37. Critical Partition Setup
    • Partition size = 250kbps; burstable;
    • limit=none
  38. Test Environment
    • Off-line configuration
    • (sometimes called a sandbox)
  39. Window size
    Theoretical value for TCP window size is the bandwidth delay product
  40. Traffic Generators
    • Nearly all traffic generators follow a client/server model
    • client generates data
    • D-ITG (Distributed Internet Traffic Generator)
  41. Iperf
    Can be used to determine UDP characteristics
  42. D-ITG
    Distributed Internet Traffic Generator
    • A More Sophisticated Traffic Generator
    • Available for Windows and Linux
    • Can generate traffic having different shapes
    • and different packet size options
Card Set
network management
ch 5