DOCSLIB.ORG

Cisco Unified Communications Manager XML Developers Guide, Release 9.0(1) Copyright © 2006–2012 Cisco Systems, Inc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cisco Unified Communications Manager XML Developers Guide, Release 9.0(1) Copyright © 2006–2012 Cisco Systems, Inc Cisco Unified Communications Manager XML Developers Guide Release 9.0(1) Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Text Part Number: OL-27400-01 NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R) Cisco Unified Communications Manager XML Developers Guide, Release 9.0(1) Copyright © 2006–2012 Cisco Systems, Inc. All rights reserved. Preface ix Purpose ix Audience x Organization xi Related Documentation xii Cisco Developer Network xiii Conventions xiv Obtaining Documentation and Submitting a Service Request xv Cisco Product Security Overview xv 1 Overview 1 Cisco Unified Communications Manager Interfaces 1 Provisioning Interfaces 1 Device Monitoring and Call Control Interfaces 2 Serviceability Interfaces 3 Routing Rules Interface 4 Development Guidelines 4 What is New in Cisco Unified Communications Manager 9.0(1) API 5 Administrative XML API 5 Serviceability XML API 11 Extension Mobility API 12 Web Dialer API 12 Routing Rules API 12 1 Administrative XML 1 1 Administrative XML Programming 1 Overview 2 New and Changed Information 3 New and Changed Information in Unified CM Release 9.0 3 New and Changed Information in Previous Releases of Unified CM 8 New Information for Unified CM 5.0(1) 134 AXL Schema Documentation 138 AXL Versioning Support 139 Authentication 142 Data Encryption 142 Dynamic Throttling of Requests 143 AXL Data Throttling 144 Integration Considerations and Interoperability 150 Post-Installation Steps and Troubleshooting on the Linux Platform 151 Post-Installation Steps 151 Post-Installation Troubleshooting Checklist 152 AXL Trace Logs 153 Using the AXL API with AXIS 155 Using the AXL API in a .NET Environment 156 Required Changes to the Generated Code 156 Backward Compatibility Issues 157 Tag Serialization Issues 158 Names Containing Special Characters 159 Returned Namespace for AXIS and .NET Applications 159 Example AXL Requests 160 C or C++ Example 161 Java Example 165 Using executeSQLUpdate 167 Using executeSQLQuery 167 AXL Error Codes 168 1 Serviceability XML 1 1 Serviceability XML Programming 1 Overview 2 New and Changed Information 2 New Information for Unified CM 9.0(1) 2 New and Changed Information in Previous Releases of Unified CM 3 Data Model 16 SOAP Binding 16 Namespaces 22 Downloading Serviceability SOAP WSDL Files 22 Monitoring SOAP Activity 23 RisPort SOAP Service 24 RisPort Service: selectCmDevice Operation 25 RisPort Service: SelectCmDeviceExt Operation 33 RisPort Service: SelectCmDevice Operation (Includes IPv6 Devices) 36 RisPort Service: selectCtiItem Operation 69 RisPort Service: SelectCtiDevice Operation (Includes IPv6 Devices) 73 RisPort Service: getServerInfo Operation 84 RisPort Service: SelectCmDeviceSIP Operation 93 Interface to Get Server Names and Cluster Name 109 PerfmonPort SOAP Service 110 PerfmonPort Service: perfmonOpenSession Operation 111 PerfmonPort Service: perfmonAddCounter Operation 112 PerfmonPort Service: perfmonRemoveCounter Operation 115 PerfmonPort Service: perfmonCollectSessionData Operation 118 PerfmonPort Service: perfmonCloseSession Operation 120 PerfmonPort Service: perfmonListInstance Operation 122 PerfmonPort Service: perfmonQueryCounterDescription Operation 125 PerfmonPort Service: perfmonListCounter Operation 126 PerfmonPort Service: perfmonCollectCounterData Operation 177 ControlCenterServicesPort SOAP Service 186 ControlCenterServicesPort service: soapGetStaticServiceList Operation 186 ControlCenterServicesPort service: soapGetServiceStatus Operation 199 ControlCenterServicesPort service: soapDoServiceDeployment Operation 214 ControlCenterServicesPort service: soapDoControlServices Operation 220 ControlCenterServicesPort service: getProductInformationList Operation 225 ControlCenterServicesPort service: soapGetfileDirectoryList Operation 247 ControlCenterServicesPort service: soapGetStaticServiceListExtended Operation 247 ControlCenterServicesPort service: soapDoControlServiceEx Operation 250 ControlCenterServicesPort service: soapDoServiceDeploymentNoDbUpdate Operation 251 LogCollectionPort SOAP Service 252 LogCollectionPort service: listNodeServiceLogs Operation 252 LogCollectionPort Service: selectLogFiles Operation 259 CDRonDemand SOAP Service 269 Security Considerations for CDRonDemand Service 273 CDRonDemand Service: get_file_list Operation 274 CDRonDemand Service: get_file Operation 275 DimeGetFileService SOAP Service 278 DimeGetFileService SOAP Service: getOneFile Operation 278 VersionService 279 Authentication 280 Basic 280 Secure 280 Authorization 281 Developer Tools 281 View Deployed Web Services 282 View <Web Service> WSDL 283 SOAP Monitor 284 Password Expiration and Lockout 284 Application Customization for Cisco Unity Connection Servers 284 SOAP Service Tracing 285 Serviceability XML API Authentication Security 286 Rate Control Mechanism 286 SOAP Fault Error Codes 287 Fault Strings 288 Sample SOAP Fault or AXIS Fault 292 Serviceability XML Application Design Guidelines and Best Practices 294 Maintain HTTPs sessions and Connection Timeouts 294 Send Perfmon Close Session 294 Device Query Support for Large Clusters 295 Respond and React to SOAP Faults 297 Limit Request and Response Size in the Application Design 297 Number of Nodes in the Cluster 297 SOAP Monitor Usage 297 Locations Topology XML Schema 297 XML Schema Definition 298 1 Extension Mobility Service API 1 1 Cisco Extension Mobility Service API 1 Overview 1 New and Changed Information 2 New Information for Cisco Unified Communications Manager 9.0(1) 2 New and Changed Information in Previous Releases of Unified CM 2 How Cisco Extension Mobility Works 3 Device Profiles 4 Using the Cisco Extension Mobility API 4 Set Up and Configuration 5 Messages 5 Message Document Type Definitions 6 Message Examples 8 Login Operation 8 Logout Operation 9 LogoutAll Operation 10 UserQuery Operation 10 DeviceQuery Operation 11 Device Profile Query 11 Extension Mobility Service Response Codes 12 1 Web Dialer API 1 1 Cisco Web Dialer API Programming 1 Overview 1 New and Changed Information 2 New Information for Cisco Unified Communications Manager 9.0(1) 2 New and Changed Information in Previous Releases of Unified CM 2 Cisco Web Dialer Components 3 Cisco Web Dialer Servlet 4 Redirector Servlet 4 Cisco Web Dialer Security Support 5 Security Service Parameters 6 Maximum Concurrent Call Requests 7 Phone Support For Cisco Web Dialer 7 Call Flows 10 Desktop-based Client Application Call Flow 11 Browser-Based Application Call Flow 12 Interfaces 14 SOAP Over HTTPS Interface 14 HTML Over HTTPS Interfaces 24 Cisco Web Dialer WSDL 26 Sample Code Snippet 30 1 Routing Rules API 1 1 Cisco Unified Routing Rules Interface 1 Overview 2 New and Changed Information 2 New Information for Cisco Unified Communications Manager 9.0(1) 2 New and Changed Information in Previous Releases of Unified CM 3 Call Routing Request 3 Description 3 Format 4 Parameters 5 Example 5 XACML Request Schema 7 Call Routing Response 9 Description 9 Format 9 Parameter 10 CIXML Format 12 CIXML Parameter 14 Example 16 XACML Response Schema 16 CIXML Schema 18 Keep-Alive Message 20 Message Timer 21 Connections 21 Multiple Connections 21 Redundant Web Services 22 Persistent Connection and Keep-Alive 22 Redirection 22 Error Handling 23 Web Service Connection Failure 23 Unified CM Timeout Awaiting Response from Web Service 23 Error Response from Web Service 24 Web Service Parse Request Error 24 Unified CM Parse Response Error 24 Web Service Evaluation Request Error 25 Security 25 Authentication 25 Certificate and Key 26 Transport Layer Security Version 26 Cipher Specification
Load more

Recommended publications
  • Fedora 7 Release Notes
    Fedora 7 Release Notes Fedora Documentation Project Copyright © 2007 Red Hat, Inc. and Others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. All other trademarks are the property of their respective owners. Abstract 1. Welcome to Fedora ................................................................................................................ 3 2. Release Highlights .................................................................................................................. 4 2.1. Fedora Tour ................................................................................................................. 4 2.2.
    [Show full text]
  • APC Tracker APC UPS Software for Mac OS X / Xserve
    APC Tracker APC UPS Software for Mac OS X / Xserve Connecting to a USB APC Tracker is the intelligent software for connecting to equipped UPS uninterruptible power supplies (UPS) for the Mac platform. Along with the standard protection a UPS provides USB HID standard compliant UPS devices from against power-failures and fluctuations, an active UPS different vendors are compatible with APC device monitoring system is useful and necessary to enable Tracker. This includes the APC Back-UPS and a proper server shut down in the event of a long-term Smart-UPS series models that are equipped with power-outage. A monitoring system is also necessary to a USB connector. diagnose the problem and to receive an automatic notification in the event of a failure. equinux APC Tracker provides Connecting to an APC UPS optimal support for market leading APCTM UPS systems over the network for the Mac platform. APC Tracker is able to connect to the UPS in the Restarting your server after a cold following ways: • Downtime prevention: shutdown can consume a lot of time due to file system APC SNMP Card checks, data base consistency checks, etc. APC Tracker All APC models that have a smart slot can be gives you the time to properly shut down your server in equipped with an APC Network Management the event of a longer power failure and thus prevents Card. This card supplies an ethernet jack to problems restarting the system. connect it to the local network. In regular time periods and in failure situations, the card sends • Easy to use: APC Tracker runs faceless in the status messages to the connected servers.
    [Show full text]
  • NUT - Network UPS Tools NUT - Network UPS Tools
    2021/09/26 07:37 1/7 NUT - Network UPS Tools NUT - Network UPS Tools This guide explains how to install NUT on a client / server architecture with several clients accessing the UPS. NUT Server Installation 1. Installing the nut package, should add the nut user and group. If it doesn’t, you have to add those manually. sudo apt-get install nut 2. Make the USB-Device accessible by NUT lsusb output: Bus 001 Device 002: ID 051d:0003 American Power Conversion UPS 3. Create new udev rule sudo vim /etc/udev/rules.d/90-nut-ups.rules ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="051d", ATTR{idProduct}=="0003", MODE="0660", GROUP="nut" 4. Activate udevadm control --reload-rules udevadm trigger ups.conf [ups] driver = usbhid-ups port = auto pollonly desc = "ups" The label in the square brackets can be anything. It identifies the UPS to upsd and upsmon. Find your UPS model on the NUT hardware compatibility list and substitute the corresponding driver for usbhid- ups above. If your UPS isn’t listed, find similar ones. They probably use the same driver. If you have a USB-based UPS, you can leave the port as auto; it’s ignored. Note: if you are connecting a Synology NAS to your NUT setup, then the label in square brackets must be named ups. Bernard's Wiki - https://wiki.condrau.com/ 2021/09/26 07:37 2/7 NUT - Network UPS Tools Make sure that nut properly detects the UPS: # upsdrvctl start You should see something like the following: Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) Using subdriver: APC HID 0.92 Now, we need to configure upsd and upsmon.
    [Show full text]
  • Apc Ups User Guide
    Apc Ups User Guide Torrance remains tutti after Bartlet liquidates midnight or aggresses any teffs. Frustrate Martino always frills his crosshatch if Dimitrios is impassioned or titivated comprehensively. Unabridged and unsymmetrical Seymour roughen so far-forth that Wolfram pocket his lascar. After having problems as two common in some parameters configuration parameter insures that under those elements of user guide ups apc ups is on the ups systems as they will switch would make it is If your critical electronics from apc ups to. Elevated temperature reduces longevity. When replacing batteries, use the same number and type ofsealed lead acid batteries as were originally contained in your UPS. Also, the information that is inserted in your halt script varies from system to system. This is the first year they show these products at the SPS. HDMI Streamer Pvi Vecaster Pro. All the standard apcupsd options can be used on the Windows version. So easy, even a baby could do it! Depending on the setting of your BIOS, it may prevent your computer from restarting when the power returns. Endpoint detection and response uses AI to help protect against nearly every type of attack aimed at endpoints in real time and can even roll back infected. We appreciate your patience and understanding. Yesterday we had a major snowstorm. Actual runtime may vary depending on the operating environment of the UPS, the power factors of the protected equipment and the condition of the UPS batteries. Designed with predictive failure notification a line-interactive APC UPS conducts. Conference scheduling, setting up the profile and address book.
    [Show full text]
  • APC UPS Management Under Linux
    APC UPS management under Linux Apcupsd Linux UPS daemon version 3.8.5 Apcupsd 3.8.5 User's Manual Last update to this manual 4 January 2002 Release Notes • Known Bugs • New features in Apcupsd 3.8.5 • New features in Apcupsd 3.8.4 • New features in Apcupsd 3.8.3 • Features in Previous Versions • Apcupsd License Apupsd Reference Manual • General −− Man Page • UPS Models and Cables Supported • Operating Systems Supported • Main Configuration Types • Compiling and Installing • Starting • Stopping or Restarting • Configuration Directives • Configuration Examples • Master/Slave Configuration • Cables • Testing • Shutdown Sequence • Trouble Shooting • Apcupsd Network Information Server • Apcupsd EVENTS • Apcupsd STATUS • Apcupsd DATA • Apcupsd System Logging • The CGI Network Interface • apcaccess • apctest • Configuring your EEPROM • UPS Programming Bible • Apcupsd under Windows 98 and Windows NT • Using Apcupsd with a USB UPS • Configuration for Controlling Multiple UPSes • Batteries Apcupsd 3.8.5 User's Manual 1 APC UPS management under Linux Other Notes • Frequently Asked Questions • Security • Thanks Other Notes 2 APC UPS management under Linux New Features in Apcupsd 3.8.5 This version of apcupsd corrects a bug that could cause a master/slave process to die due to a TCP/IP disconnect error. This version also includes the ability with the apctest program to perform a Battery Runtime Calibration. For more information on using apctest, please see the apctest Chapter of this manual. apcupsd is mainly developed under Linux and will compile cleanly and work under most flavors of Unix as well as many other operating systems including Windows. What to do if you find bugs : send an email to apcupsd−[email protected] (Developers mailing list) or go to one of the following sites: http://www.apcupsd.org http://www.sibbald.com/apcupsd Please be sure to include the version of apcupsd you are running, your operating system, and a detailed description of your problem.
    [Show full text]
  • Cisco Emergency Responder 9.0 Open Documentation
    Open Source Used In Cisco Emergency Responder 9.0 This document contains the licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of the source code to which you are entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License) , please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-22580798 Contents 1.1 ace 5.5.1 1.1.1 Available under license 1.2 acl 2.2.39 :6.el5 1.2.1 Available under license 1.3 acpid 1.0.4 :9.el5_4.2 1.3.1 Available under license 1.4 activation.jar ver 1.1 1.1 1.4.1 Available under license 1.5 alsa-lib 1.0.17 :1.el5 1.5.1 Available under license 1.6 alsa-utils 1.0.17 :1.el5 1.6.1 Available under license 1.7 Apache Commons Collections 3.2.1 Open Source Used In Cisco Emergency Responder 9.0 1 1.7.1 Available under license 1.8 Apache Commons Digester 1.8.1 1.8.1 Available under license 1.9 Apache Derby 10.5.3.0 1.9.1 Available under license 1.10 apcupsd 3.14.0 :1 1.10.1 Available under license 1.11 apcupsd 3.14.8 :1 1.11.1 Available under license 1.12 at 3.1.8 :84.el5 1.12.1 Available under license 1.13 attr 2.4.32 :1.1 1.13.1 Available under license 1.14 audit 1.7.17 :3.el5 1.14.1 Available under license 1.15 audit_libaudit 1.7.17 :3.el5 1.15.1 Available under license 1.16 authconfig 5.3.21 :6.el5 1.16.1 Available under license 1.17 axis 1.4 1.17.1 Available
    [Show full text]
  • Apcupsd User's Manual Apcupsd User's Manual
    apcupsd User's Manual apcupsd User's Manual Revision History Revision 2.0 20 Sept 2003 esr First XML−DocBook version. Table of Contents Release Notes New Features in in 3.10.6 New Features in 3.10.5 New Features in 3.10.4 How To Use This Manual I. Basic User's Guide 1. Planning Your Installation Quick Start for Beginners Supported Operating Systems, UPSes and Cables Choosing a Configuration Type Checking Out Your USB Subsystem 2. Building and Installing apcupsd Installation from Binary Packages Red Hat Linux Microsoft Windows Installation from Source Verifying a Source Installation Configure Options Recommended Options for most Systems Compilers and Options Operating System Specifics Alpha Debian FreeBSD HPUX NetBSD OpenBSD Red Hat Systems Slackware SuSE Sun Solaris Unknown System Windows Systems with CYGWIN Installed 3. After Installation Checking Your Configuration File Arranging for Reboot on Power−Up Making Sure apcupsd Is Running 4. Testing apcupsd Process−Status Test Logging Test apcaccess Test apcupsd User's Manual 1 apcupsd User's Manual Communications Test Simulated Power Fail Test System Shutdown Test Full Power Down Test Shutdown Sequence apctest 5. Troubleshooting Your Installation Known Problems with USB UPSes Reconnection does not clean up the lockfile Power Off (killpower) of UPS Does Not Work apcupsd Cannot Reconnect After a Reboot 6. Monitoring and Tuning your UPS apcaccess apcaccess status apcaccess eprom hid−ups and USB Specific Information apcupsd Network Monitoring (CGI) Programs Setting up and Testing the CGI Programs multimon.cgi upsstats.cgi ./upsstats.cgi upsfstatus.cgi Working Example Client Test Program A Tip from Carl Erhorn for Sun Systems Credits Security Issues Configuring Your EEPROM apcupsd No Longer Configures EEPROM Using apctest to Configure Your EEPROM 7.
    [Show full text]
  • APCUPSD User Manual
    APCUPSD User Manual Adam Kropelin Kern Sibbald Apcupsd is a UPS control system that permits orderly shutdown of your computer in the event of a power failure. March 28, 2014 23:31:53 This manual documents apcupsd version 3.14.x Copyright © 2004-2014 Adam Kropelin Copyright © 1999-2005 Kern Sibbald Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the name Apcupsd, the copyright notice, and this notice are preserved. Apcupsd source code is released under the GNU General Public License version 2. Please see the file COPYING in the main source directory. For more information on the project, please visit the main web site at http://www.apcupsd.com Important Legal Disclaimer 6 How To Use This Manual 7 Basic User's Guide 7 Quick Start for Beginners 7 Supported Operating Systems 8 Platform Support 8 Supported UPSes and Cables 9 Choosing a Configuration Type 10 Configuration types 10 USB Configuration 12 Linux USB Configuration 12 Known Linux USB Issues 12 Verifying Device Detection and Driver 13 Device Nodes 14 Miscellaneous 16 BSD USB Configuration 16 Known BSD USB Issues 16 Platforms and Versions 16 Kernel Configuration 16 Verifying Device Detection and Driver 17 Device Nodes 18 Windows USB Configuration 18 Platforms and Versions 18 USB Driver Installation 18 Verifying Device Detection and Driver 18 Solaris USB Configuration 18 Platforms and Versions 18 Building Apcupsd with USB 18 Verifying Device Detection and Driver 19 Device Nodes 19 Mac OS X (Darwin) USB Configuration
    [Show full text]
  • Network UPS Tools User Manual I
    Network UPS Tools User Manual i Network UPS Tools User Manual Network UPS Tools User Manual ii REVISION HISTORY NUMBER DATE DESCRIPTION NAME 2.7.4 2016-03-09 Current release of Network UPS Tools (NUT). 2.6.0 2011-01-14 First release of AsciiDoc documentation for Network UPS Tools (NUT). Network UPS Tools User Manual iii Contents 1 Introduction 1 2 Network UPS Tools Overview 1 2.1 Description......................................................1 2.2 Installing.......................................................1 2.3 Upgrading.......................................................1 2.4 Configuring and using.................................................1 2.5 Documentation....................................................1 2.6 Network Information.................................................2 2.7 Manifest........................................................2 2.8 Drivers........................................................2 2.8.1 Extra Settings.................................................3 2.8.2 Hardware Compatibility List.........................................3 2.8.3 Generic Device Drivers............................................3 2.8.4 UPS Shutdowns...............................................4 2.8.5 Power distribution unit management.....................................4 2.9 Network Server....................................................4 2.10 Monitoring client...................................................4 2.10.1 Master....................................................4 2.10.2 Slave.....................................................4
    [Show full text]