HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations - نسخه متنی

Tammy Zitello

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید



Chapter 9. Scalability and Distribution


NNM provides a number of scalability features. This chapter discusses the features that allow the scalability and distribution of NNM. While scaling a product does not eliminate the necessity for hardware upgrades, it may reduce the amount of resources required for optimal performance. For example, if the synchronization of a map (loading objects into memory) takes a long time, this may indicate that the management station could use more memory. Before upgrading memory, try the options listed here that may reduce the amount of memory being consumed on the management station when maps are opened:

  • Configure remote consoles to distribute the display of maps. Maps that are opened from the remote console use the remote console memory to load the objects.

  • Modify the persistence level of the maps that are opened on the management station. This reduces the number of objects that are loaded into memory when a map is opened.

  • Implement a discovery filter to reduce the number of objects in the database. Because there are fewer objects in the database, the number of objects loaded into memory for polling and display is reduced.

  • Implement map filters to reduce the number of objects loaded into memory. The objects still reside in the database but are not displayed on maps containing filters. Assign different map filters to different maps.

  • Configure a collection station to discover a portion of the network. Maps displayed from a collection station only load objects that reside in the collection station's database.

  • Use the network presenter. Although this does not reduce memory on the management station because ovw must still be running, it does reduce the requirements on the display station.

  • Sealey Inc. needs a network monitoring solution that scales well. Because their customers do not currently have a monitoring solution, no one knows what the customer networks consist of (the number of nodes, routers, or the topology). Network operators have workstations (UNIX and Windows) that can be utilized to offload some of the resources from the management station.

    Due to the network sizes and security issues, Sealey Inc. may be required to implement NNM stations on some of the customer networks. Many of the customers have firewalls between Sealey Inc. and their private networks. These firewalls do not allow ICMP and SNMP traps to pass through them.

    Many of the operators have very specific skills that require them to monitor critical devices. They need custom maps that display only the critical devices. Custom maps allow the operator to monitor and troubleshoot the devices more efficiently.

    If necessary, Sealey Inc. can ignore certain devices' types, such as DHCP devices. They would like to provide IP address ranges that will not be discovered or managed by their monitoring solution.

    Many NNM features provide the capability to scale network management to the enterprise. This chapter provides technical details on the implementation of remote consoles, management and collection stations, and the different types of filters.


      / 276