![]() ![]() Customer Views 10.1 THE FIVE ADDITIONAL VIEWS 10.2 THE OVCUSTOMER UTILITY 10.3 CONFIGURING THE HIERARCHICAL SUBMAP BUILDER 10.4 SUMMARY Chapter 11. Scalability and Distribution 9.1 REMOTE CONSOLES 9.2 CONFIGURING THE ON-DEMAND LEVEL FOR A MAP 9.3 CONFIGURING THE POLLING FREQUENCY 9.4 DEFINING FILTERS 9.5 DISTRIBUTED INTERNET MONITORING (DIM) 9.6 SUMMARY Chapter 10. Data Collection and Event Configuration 8.1 CREATING A DATA COLLECTION 8.2 CREATING THRESHOLD AND REARM EVENTS 8.3 CUSTOMIZING EXISTING DATA COLLECTIONS 8.4 CUSTOMIZING EXISTING EVENTS 8.5 TEST YOUR KNOWLEDGE OF DATA COLLECTION AND EVENTS 8.6 DETAILED SOLUTION TO NETWORK PRINTER EXERCISE 8.7 SUMMARY Chapter 9. Advanced Customization 7.1 Application Integration using Application Registration Files (ARFs) 7.2 Application Integration using Web Launcher Registration Files (WLRF) and Network Presenter Registration Files (NPRF) 7.3 Defining Custom Symbols and Fields 7.4 Summary Chapter 8. Customizing NNM from the GUI 6.1 CUSTOMIZING SUBMAPS 6.2 SUMMARY Chapter 7. Network Discovery 5.1 SEEDING INITIAL DISCOVERY 5.2 ADDITIONAL DISCOVERY METHODS 5.3 NETMON POLLING STATISTICS 5.4 CONFIGURING SNMP COMMUNITY NAMES 5.5 FIREWALL CONSIDERATIONS IN NETWORK DISCOVERY 5.6 SUMMARY Chapter 6. Out-of-the-box Network Node Manager 4.1 NNM DISCOVERY 4.2 SYMBOLS AND OBJECTS 4.3 ALARM CATEGORIES 4.4 QUERYING THE MIB 4.5 WEB ACCESS 4.6 SUMMARY Chapter 5. Create a Deployment Plan 3.1 MANAGEMENT REQUIREMENTS 3.2 DEFINE THE MANAGEMENT DOMAIN 3.3 ARE THERE FIREWALLS WITHIN THE MANAGEMENT DOMAIN? 3.4 OUT-OF-BAND NETWORK MANAGEMENT 3.5 BACKUP AND RECOVERY REQUIREMENTS 3.6 AUTHENTICATION, AUTHORIZATION, AND ACCESS CONTROL REQUIREMENTS 3.7 EVENT CORRELATION REQUIREMENTS 3.8 HIGH AVAILABILITY AND FAULT TOLERANCE REQUIREMENTS 3.9 CONFIGURATION AND CHANGE MANAGEMENT PROCESS REQUIREMENTS 3.10 HARDWARE CONFIGURATION REQUIREMENTS 3.11 SUMMARY Chapter 4. TO EVEN GET OFF THE GROUND 2.5 SUMMARY Chapter 3. TO EFFECTIVELY MANAGE THE ENTERPRISE GROWTH 2.3. Why Network and Systems Management Systems Fail 2.1. Introduction to Network Node Manager, Customer Views, and Service Information Portal 1.1 AN SNMP COKE MACHINE 1.2 WHAT NETWORK NODE MANAGER PROVIDES 1.3 WHAT CUSTOMER VIEWS PROVIDES 1.4 WHAT SERVICE INFORMATION PORTAL PROVIDES 1.5 OBTAINING EVALUATION COPIES OF NNM, CV, AND SIP 1.6 ADDITIONAL OPENVIEW PRODUCTS 1.7 SOME HELPFUL URLS Chapter 2. Sitemap HP OpenView System Administration Handbook: Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations Table of Contents Copyright Praise for HP OpenView System Administration Handbook Hewlett-Packard Professional Books How This Book Is Organized Acknowledgements Who This Book Is For Conventions Used in This Book Part 1: Network Node Manager, Customer Views, and Service Information Portal Chapter 1.The temporary folder, or extract the archive before running the restore command. In this case, either ensure that the current working directory has adequate storage capacity to support If the provided source is a tar file, the NNMi restore command extracts the tar file to a temporary folder in the current With the -force option, the nnmrestore.ovpl command stops all NNMi processes, starts the nmsdbmgr service (if restoring from an online backup of the NNMi database), restores the data, and then restarts all NNMi processes. In restoring an offline backup, NNMi overwrites the Postgres files in the file system, completely replacing the database files For the NNMi database, the nmsdbmgr service must be running. Made revert to their state at the time of the backup. Additionally, any objects that were changed after the backup was ![]() That have been created since the backup was made disappear. Objects that were deleted after the backup was made are restored, and objects ![]() In restoring an online backup, NNMi copies the file system data to the correct locations and overwrites the contents of theĭatabase tables that were included in the backup. Management server, you must uninstall NNMi from the original NNMi management server. After you restore NNMi on the second NNMi Second NNMi management server means that both servers have the same database UUID. When you are using the global network management function, placing the backup data from one NNMi management server onto a Of operating system and the same NNMi version and patch level.ĭo not restore backup data acquired from an NNMi with a cluster configuration to an NNMi with a single configuration. If you use the nnmrestore.ovpl script to place database records on a second NNMi management server, both NNMi management servers must have the same type The type and scope of the backup determines what NNMi can restore. The NNMi restore script ( nnmrestore.ovpl) places backup data on the NNMi management server. ![]()
0 Comments
Leave a Reply. |