# Patent

## Title
Remote power control system

## Abstract

An SNMP network comprises a power manager with an SNMP agent in TCP/IP communication over a network with an SNMP network manager. The power manager is connected to control several intelligent power modules each able to independently control the power on/off status of several network appliances. Power-on and load sensors within each intelligent power module are able to report the power status of each network appliance to the SNMP network manager with MIB variables in response to GET commands. Each intelligent power module is equipped with an output that is connected to cause an interrupt signal to the network appliance being controlled. The SNMP network manager is able to test which network appliance is actually responding before any cycling of the power to the corresponding appliance is tried.

## Background
CROSS-REFERENCE TO RELATED APPLICATION(S)
This application is a continuation of U.S. patent application Ser. No. 11/370,489, filed Mar. 7, 2006, now U.S. Pat. No. 8,560,652, titled REMOTE POWER CONTROL SYSTEM, which is a continuation of U.S. patent application Ser. No. 09/732,557, filed Dec. 8, 2000, now U.S. Pat. No. 7,099,934, titled NETWORK-CONNECTING POWER MANAGER FOR REMOTE APPLIANCES, the entireties of which are all incorporated herein by reference.


BACKGROUND
1. Technical
The technical field relates generally to automatic power control and more particularly to remote control methods and devices to maintain computer network system availability.
2. Description of the Prior Art
Enterprise networks exist to support large world-wide organizations and depend on a combination of technologies, e.g., data communications, inter-networking equipment (frame relay controllers, asynchronous transfer mode (ATM) switches, routers, integrated services digital network (ISDN) controllers, application servers), and network management application software. Such enterprise networks can be used to support a large company's branch offices throughout the world, and, as such, these networks have become mission critical to the functioning of such organizations. Masses of information are routinely expected to be exchanged, and such information exchanges are necessary to carry on the daily business of modern organizations. For example, some international banks have thousands of branch offices placed throughout Europe, Asia and the United States that each critically depend on their ability to communicate banking transactions quickly and efficiently with one another and headquarters.
A typical enterprise network uses building blocks of router and frame relay network appliances mounted in equipment racks. Such equipment racks are distributed to remote point of presence (POP) locations in the particular network. Each equipment rack can include frame relay controllers, routers, ISDN controllers, servers and modems, etc., each of which are connected to one or more power sources. The value of POP equipment can range from $200,000 to $500,000, and the number of individual devices can exceed a thousand.
Many enterprises rely on an uninterruptable power supply (UPS) to keep their network appliances operational. Many network appliances are typically connected to a single UPS, and this sets up a problem. When an individual router locks up, the router's power cannot be individually cycled on and off externally at the UPS because it is connected to a multiple power outlet. The recovery action choices available to the network control center operator thus do not include being able to reinitialize the individual equipment through a power interruption reset. The network operator could command the UPS to power cycle, but that would reset all the other attached devices that were ostensibly operating normally and carrying other network traffic. Another option is to dispatch someone to the remote location to reset the locked-up device. Neither choice is an attractive solution.
In large organizations that have come to depend heavily on enterprise networks, great pressures develop to control costs and thus to improve profits. Organizational down-sizing has been used throughout the corporate world to reduce non-network costs, and that usually translates to fewer technical people available in the right places to support large and complex in-house global networks. Such reduced repair staffs now rely on a combination of centralized network management tools and third-party maintenance organizations to service their remote POP sites. The costs associated with dispatching third-party maintenance technicians is very high, and the dispatch and travel delay times can humble the business operations over a wide area for what seems an eternity.
Global communication network operators, located at a few centralized network management centers, are relying more and more on automated network management applications to analyze, process, display and support their networks. An increasing number of network management software applications are being marketed that use open-system standardized protocols.
Particular network application tool software is available to report lists of the network appliances, by location, and can issue trouble lists and keep track of software versions and releases. New simple network management protocol (SNMP) applications are conventionally used to issue alarms to central management consoles when remote network appliances fail.
One such SNMP network management application is marketed by Hewlett-Packard. HP OPENVIEW is a family of network and system management tools and services for local and wide area multivendor networks. OPENVIEW is a management platform that provides application developers and users with the ability to manage multivendor networks and expand their distributed computing environments. OPENVIEW allows network operation centers to build an intelligent hierarchical network management application, and uses open standards such as SNMP, user datagram protocol (UDP), and the now ubiquitous transmission control protocol/internet protocol (TCP/IP).
Because OPENVIEW is built on open system standards, global communication network operators can easily integrate the various inter-networking equipment nodes into a managed environment operated by strategically located network consoles.
In order to provide a reliable computing environment, a robust and active process for problem resolution must be in place. OPENVIEW allows the definition of thresholds and monitoring intervals, and the interception of network, system, database, and application-messages and alerts. Once a threshold value is exceeded, intelligent agents can run a pre-defined automatic action and/or generate and send a message to alert an operator on a central management console. Messages can also be forwarded to a pager or trouble-ticketing application. To help focus on the most critical problems, a message browser window is used to display six severity levels for incoming problems and events, e.g., ranging from stable to critical. An integrated history database is provided for auditing and analyzing system and network activities, for identifying trends and for anticipating problems before they occur. Activity displays and reports can be customized by the users.
Prior art SNMP network management uses embedded microprocessors in almost every network appliance to support two-way inter-computer communications with TCP/IP, of which SNMP is a member of the TCP/IP protocol suite. SNMP is conventionally used to send messages between management client nodes and agent nodes. Management information blocks (MIBs) are used for statistic counters, port status, and other information about routers and other network devices. GET and SET commands are issued from management consoles and operate on particular MIB variables for the equipment nodes. Such commands allow network management functions to be carried out between client equipment nodes and management agent nodes.
SNMP is an application protocol for network management services in the internet protocol suite. SNMP has been adopted by numerous network equipment vendors as their main or secondary management interface. SNMP defines a client/server relationship, wherein the client program, a “network manager”, makes virtual connections to a server program, an “SNMP agent”, on a remote network device. The data base controlled by the SNMP agent is the SNMP management information base, and is a standard set of statistical and control values SNMP and private MIBs allow the extension of standard values with values specific to a particular agent.
Directives issued by the network manager client to an SNMP agent comprise SNMP variable identifiers, e.g., MIB object identifiers or MIB variables, and instructions to either GET the value for the identifier, or SET the identifier to a new value. Thus private MIB variables allow SNMP agents to be customized for specific devices, e.g., network bridges, gateways, and routers. The definitions of MIB variables being supported by particular agents are located in descriptor files, typically written in abstract syntax notation (ASN.1) format. The definitions are available to network management client programs.
SNMP enjoys widespread popularity, and SNMP agents are available for network devices including computers, bridges, modems, and printers. Such universal support promotes interoperability. The SNMP management protocol is flexible and extensible, SNMP agents can incorporate device specific data. Mechanisms such-as ASN.1 files allow the upgrading of network management client programs to interface with special agent capabilities. Thus SNMP can take on numerous jobs specific to device classes such as printers, routers, and bridges. A standard mechanism of network control and monitoring is thus possible.
Unfortunately, SNMP is a complicated protocol to implement, due to complex encoding rules, and it is not a particularly efficient protocol. Bandwidth is often wasted with needless information, such as the SNMP version that is to be transmitted in every SNMP message, and multiple length and data descriptors scattered throughout each message. SNMP variables are identified as byte strings, where each byte corresponds to a particular node in the MIB database. Such identification leads to needlessly large data handles that can consume substantial parts of each SNMP message.
Most vendors implement network managers thinking a user's primary interest is in the data associated with particular network devices. But such data is easily acquired by other means, e.g., “netstat” and “rsh” UNIX programs. The important information about the network includes the differences between devices, besides their current states. SNMP affords a good mechanism for rapidly processing such differences on large networks, since SNMP avoids the processing burden of remote login and execution.
Network management applications can thus monitor the health of every part of a global communications network and can be set to communicate alarms to a central management console. Current network management applications do an adequate job of informing central management consoles about the health of various nodes in the network and the alarms they issue when a node is failing are useful.
Conventional SNMP network management technologies do not provide sufficient information related to the nodes' electrical power status. A new technology is needed that can be simply and inexpensively added to client equipment nodes for SNMP reporting of the electrical power status of the node. For example, in a router based network with SNMP support, prior art individual routers can use SNMP to issue an alarm to the management console. But the console operator would know only that the router is failing. A GET command can be issued to the router node to determine if the counter and buffer threshold limits were exceeded and caused a router to lock-up. However, the console operator does not have any information about the electrical power status to the router, e.g., has the router power switch been moved to the OFF position or has the switch been accidentally turned OFF? The electrical power source could have failed, the power cable connection become loose, or a technician may have accidentally removed the router from a rack.
SUMMARY OF THE PRESENT INVENTION
Certain embodiments of the present invention provide a system and method for providing power supply status and control in network nodes at geographically distant locations.
Certain embodiments of the present invention provide a system and method for describing power supply status and control in SNMP MIB variables between network nodes and a central network management console.
Certain embodiments of the present invention provide a verification of which particular network appliance will be subjected to a power-up or power-down command before the operator must commit to such commands.
Briefly, an SNMP network embodiment of the present invention can comprise a power manager with an SNMP agent in TCP/IP communication over a network with an SNMP network manager. The power manager can be connected to control several intelligent power modules each able to independently control the power on/off status of several network appliances in an equipment rack at a common remote node, e.g., a point-of-presence site. Power-on and load sensors within each intelligent power module can are able to report the power status of each network appliance to the SNMP network manager with MIB variables in response to GET commands. Each intelligent power module can be equipped with an output that is connected to cause an interrupt signal to the network appliance being controlled. The SNMP network manager can is able to test which network appliance is actually responding before any cycling of the power to the corresponding appliance is tried.
An advantage of certain embodiments of the present invention is that a system and method can be provided that can help an operator avoid the mistake of turning on or off wrong network appliance in a busy equipment rack at a remote site.
Another advantage of certain embodiments of the present invention is that a system and method can be provided for describing power supply status and control in SNMP MIB variables between network nodes and a central network management console.
A further advantage of certain embodiments of the present invention is that a system and method can be provided that allows a network console operator to investigate the functionality of the electrical power status when a router or other network device has been detected as failing.
A still further advantage of certain embodiments of the present invention is that a system and method can be provided for reducing the need for enterprise network operators to dispatch third party maintenance vendors to remove equipment rooms and POP locations simply to power-cycle failed network appliances. The costs to dispatch such third party maintenance vendor can run from $300-$600 per call. The cost of implementing the present invention can be recaptured in less than one year, e.g., by reducing the number of third party maintenance dispatches to remove locations.
Another advantage of certain embodiments of the present invention is that a system and method can be provided for reducing the time it takes to restore a failed network appliance and improving service level measures.
Another advantage of certain embodiments of the present invention is that a system and method can be provided for reducing organization losses from network downtime. Being able to immediately power-cycle a failed server and thus return the server to operation can directly reduce the downtime loss to the organization.
There are other objects and advantages of various embodiments of the present invention. They will no doubt become obvious to those of ordinary skill in the art after having read the following detailed description of the preferred embodiments which are illustrated in the various drawings figures.



IN THE DRAWINGS
FIG. 1 is a block diagram of a simple network management protocol (SNMP) network embodiment of the present invention;
FIG. 2 is a flowchart of a method of appliance power switch status detection, according to the present invention;
FIG. 3 is a schematic of a representative intelligent power module such as are included in the network of FIG. 1;
FIG. 4 is a schematic diagram of the load sensor included in the intelligent power module of FIG. 3; and
FIG. 5 is a schematic diagram of the power-on sensor included in the intelligent power module of FIG. 3.



DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
FIG. 1 illustrates a simple network management protocol (SNMP) network embodiment of the present invention, referred to herein by the general reference numeral 10. The SNMP network 10 includes a host 12 with a TCP/IP connection 14 to a plurality of point-of-presence (POP) nodes represented by a pair of network equipment racks 16 and 18. SNMP network management is provided by a SNMP manager 20 in communication with a respective pair of SNMP agents 22 and 24 at the remote nodes. The SNMP manager 20 may comprise a commercial product such as IBM NETVIEW/6000, HP OPENVIEW, POLYCENTER, SunNet MANAGER, Cabletron SPECTRUM, etc.
An uninterruptable power supply (UPS) 26 provides operating power to a TCP/IP-addressable enterprise power manager 28. It also powers a plurality of intelligent power modules (IPM's) 30, 32, 34, 36 that are able to switch the operating power on/off to a corresponding network appliances 38, 40, 42, 44.
An SNMP agent 46 is private to the power manager 28. It does not depend on the equipment rack 16 or any of its network appliances 38, 40, 42, 44. The power manager 28 is connected to independently control each of the intelligent power modules 30, 32, 34, 36. Such control includes being able to sense the power-on and load status of each of the network appliances 38, 40, 42, 44 and to switch power on and off to each of the network appliances 38, 40, 42, 44. Such status is sensed and reported by an SNMP GET command 48 and the power switching is accomplished with an SNMP SET command that issue from the host 12.
The power manager 28 and IPM's 30, 32, 34, 36, are also able to generate an interrupt signal to each corresponding network appliances 38, 40, 42, 44. Although FIG. 1 shows only the four network appliances 38, 40, 42, 44, typical installations will have so many that it is easy for the wiring of the power supply to get confused. In practice this has happened often enough that serious consequences have been paid when the network appliance that was supposed to be controlled by a particular IPM was not. Given the dependence that customers, users, and suppliers now place on the uninterrupted operation of their networks, accidental interruptions cannot be tolerated at all.
If the SNMP manager 20 intends, for example, to power cycle the third network appliance 42, an interrupt signal is sent to IPM 34 via SNMP agent 46. If IPM 34 really is supplying the power to network appliance 42, an interrupt signal will be processed and a message will be sent on the TCP/IP network 14. Such message will be received by the SNMP manager 20 that will unambiguously identify the third network appliance 42 as having been “tickled”. If such message does not appear, or it appears and identifies a different network appliance, then the system administrator will be alerted to a probable wiring error.
Many commercial network devices provide a contact or logic-level input port that can be usurped for the “tickle” signal. Cisco Systems routers, for example, provide an input that can be supported in software to issue the necessary message and identifier to the system administrator. A device interrupt has been described here because it demands immediate system attention, but a polled input port could also be used.
A network appliance 38, 40, 42, 44, that needs to have its power cycled on/off may need such action to clear a software lockup that has occurred. A power-on reset is needed to get the appliance to reboot. In such instances, a “tickle” signal from an IPM would be ignored because the recipient is essentially dead. Some systems may be temporarily awakened from their death sleep by a non-maskable interrupt and interrupt service routine. There may be enough resources to issue the message and identification that the system administrator needs to see. It will therefore be best for routine checks to be made before there is any trouble to register which IPM 30, 32, 34, 36, matches which network appliance 38, 40, 42, 44.
If the devices being supplied operating power by the IPM's 30, 32, 34, 36, are NT-servers, then an RS-232 serial interface is present that can be used for the “tickle” signal. In particular, the request-to-send (RTS) control line can be provided with a pulled-up dry-contact or open-collector from the IPM's 30, 32, 34, 36. A application program interface (API) is then added to the NT-server to issue the report message and identity when the RTS is toggled.
FIG. 2 shows a method of appliance power switch status detection, referred to herein by the general reference numeral 100. The method 100 comprises a step 102 applying a series of alternating current (AC) voltage pulses to an appliance with an on/off switch that are synchronized to a source of AC power. A step 104 senses the presence of any series of AC current pulses that result if the appliance switch is closed. A step 106 analyzes any AC current pulses detected in step 104 to determine if they resulted from the application of the AC voltage in step 102. A step 108 outputs an on/off status indication for the appliance switch. Method 100 does not result in the turning-on and the operation of the appliance during steps 102 or 104, and is therefore unobtrusive.
FIG. 3 illustrates an intelligent power module 200, similar to intelligent power modules 30, 32, 34, 36, which may be located external or internal to devices 38, 40, 42, 44, or internal or external to the UPS 26. The intelligent power module 200 includes a power supply and clock generator 212, a load sensor 214, a power-on sensor 216, a solid-state relay 218 and a microprocessor 220. A serial input/output (I/O) connection 221 provides for communication with a controller, e.g., power manager 28.
A “tickle” relay 222 is controlled by the microprocessor 220 and can issue a dry-contact test signal. Such signal is intended to stimulate a message and identity report to a system administrator. Preferably, the operating power is controlled by an IPM and such test signal or “tickle” are wired to the same network appliance.
An appliance, such as the network appliances 38, 40, 42, 44, has a power on/off switch 223 that may be internal or external to the appliance, and is represented in FIG. 3 by a network device load 224 connected to a network 225. The switch 223 may also actually comprise both internal and external switches in series. The incoming alternating current (AC) line power is applied to the intelligent power module 200 at a hot (H) terminal 226, a neutral (N) terminal 227 and a ground (G) terminal 228. The appliance has its incoming AC line power applied to a hot (H) terminal 230, a neutral (N) terminal 232 and a ground (G) terminal 234, which are respectively connected to a hot (H) terminal 236, a neutral (N) terminal 238 and aground (G) terminal 240. A relay 242 allows automatic remote control by the microprocessor of power to the appliance due to its position in the incoming AC line.
A network monitor 243 and a system administrator are able to receive message and identity reports issued by the network device load 224 in response to a “tickle” signal.
The load sensor 214 is such that if a current is flowing because switch 223 is closed, the microprocessor will receive a logic low status indication.
FIG. 4 represents an embodiment of the load sensor 214 included in FIG. 3. The load sensor 214 comprises a sense resistor 244 connected to a voltage comparator 245. When the voltage dropped across the sense resistor 244 exceeds a reference voltage provided by a power supply 246, the output of the voltage comparator 245 goes high. A resistor 247 couples this to an opto-isolator 248 and produces a five volt digital output (I_SENS) that indicates load/no-load to the microprocessor 220. A resistor 250 provides a pull-up to a current sense input to the microprocessor 220.
FIG. 5 represents an embodiment of the power-on sensor 216 included in FIG. 3. The power-on sensor 216 includes an opto-isolator 252. The output of the opto-isolator 252 goes low when a sufficient voltage is dropped across a resistor 254. A five volt power supply connection and a pull-up 256 provide a five volt logic output (V_SENS) that indicates power/no-power to the microprocessor 220.
In operation, the device 200 senses if switch 223 is closed or open by converting AC current pulses from the power supply 212 that flow through the series circuit comprising the solid-state relay 218, the H-terminals 230 and 236, the switch 223, the network device load 224, the N-terminals 232 and 238, the load sensor 214, and return to the power supply 212. If the switch 223 is open, no such current can flow.
The power supply and clock generator 212 provides a five volt pulse clock (CLK) to the microprocessor 220 at each zero-crossing of the incoming AC power line voltage across the H-terminal 226 and the N-terminal 227. A slightly delayed version of the clock is output by the microprocessor 220 to control the solid-state relay 218. A seventy volt AC output (70 VAC) of the power supply and clock generator 212 provides a reduced voltage AC sine wave that is approximately seventy volts RMS. The solid-state relay 218 therefore gates through the seventy volt AC waveform twice each cycle such that alternating pulses of +70 volts and −70 volts are sent through switch 223 and load sensor 214. If a current flows because the switch 223 is closed, a characteristic pulse synchronized to the CLK signal will appear as an output from the opto-isolator 248. A resistor 250 provides a pull-up to a current sense input to the microprocessor 220. If the switch 223 is open, the characteristic pulses will not appear. An “on-sense” opto-isolator 252 provides isolation for a voltage sense input to the microprocessor 220.
The microprocessor 220 analyzes and stores its determination of whether the power is applied to the device 38-44 and whether the switch 223 is closed. Such data is thereafter useful to control the relay 242. The microprocessor 220 is programmed to control the relay 242 and to report the presence of current and voltage to the appliance through serial communication conducted over the serial I/O connection 221.
The power manager 28 is able to read from the intelligent power modules 30, 32, 34, 36, whether there is a proper operating voltage being supplied to the network appliances 38, 40, 42, 44, and whether such loads are turned on. The power manager 28 and its SNMP agent 46 are able to report such status in response to the GET command 48. The GET command modifies a MIB variable that is reported by the SNMP agent 46 to the SNMP manager 20.
The power manager 28 is able to require the intelligent power modules 30, 32, 34, 36, to turn the power being supplied to the network appliances 38, 40, 42, 44, on or off in response to the SET command 50. Such SET commands modify the MIB variable defined for power on/off, and allow independent power-cycling of each and any of the network appliances 38, 40, 42, 44. Such power cycling promotes a power-up reset of the appliance, e.g., when the SNMP agent 22 has reported a failure of the POP node 16 to the SNMP manager 20.
SNMP defines a client/server relationship. The client program, network manager 20, makes virtual connections to the server program, the SNMP agent 22 and 24 on a remote network device. The database controlled by the SNMP agent is the management information base (MIB). The MIB is a standard set of statistical and control values that provides information about the attributes of devices attached to the network. SNMP allows for the extension of these standard values with values that are specific to a particular SNMP agent through the use of private MIBs. The use of private MIB variables allows SNMP agents to be modified for a variety of devices, e.g., bridges, hubs, routers and CSU/DSUs, etc. SNMP operates by exchanging network information through protocol data unit (PDU) messages. PDUs carry variables that have both titles and values. There are five types of PDUs that SNMP uses to monitor a network, two for reading terminal data, two for setting terminal data, and one, the trap, monitoring network events. Every SNMP message consists of a variable, and every variable consists of a variable title, the integer, string data type of the variable, whether the variable is read-only or read-write, and the value of the variable.
The SNMP manager 20 collects information via MIBs about routers, hubs, bridges, concentrators, servers, switches and other network appliances. When a problem at a remote node is detected, the corresponding SNMP agent issues an alarm that identifies the problem by type and node address. The SNMP manager typically sends a Telnet script to a TCP/IP-addressable enterprise power manager. The Telnet script instructs the enterprise power manager to cycle the power cycle, to recover an otherwise locked-up network device. SNMP management is not required for the enterprise power manger and the associated intelligent power modules. The intelligent power modules include normally closed relays so power is always on except when the relay is deliberately opened to trigger a power on reset and reboot. The network management application monitors the UPS and the network appliances.
The load sensor and power-on sensor can be combined such that a console operator can determine if electrical power is available to an equipment rack and to an individual network appliance. A relay reset located between the power source and the client equipment node supports an SNMP-type SET command that can be defined to open and close a relay to power-cycle the network appliance. Such power-cycling can clear a lockup condition and allow the device to return to normal operation via its own internal power-up reset mechanism.
A console operator can be notified by conventional means that a router is failing. A determination then needs to be made that the electrical power is available to the equipment rack and to an individual network appliance. The next action would be to try to power-cycle an individual network appliance to return it to operational status.
A power-on sensor 216, a load sensor 214 and a relay reset 218 can be combined in the electrical power supply connected to the equipment rack. Once a console operator has determined both that the router is failing and that the electrical power is available to the equipment rack and to the individual network appliance, the next logical step can be to power-cycle the individual network appliance, e.g., to return it to operational status.
Where the in-place equipment that supplies electrical power for an equipment rack cannot be modified to incorporate the functions of an intelligent power module, the intelligent power module 200 can be connected in-line between the electrical power source and the equipment power receptacle. The intelligent power module provides the necessary power-on sensor, load sensor, and relay reset circuit functions. The network management console operator can determine by conventional means that a device such as a router is failing.
With the present invention it can be further determined that electrical power is available to an equipment rack and to an individual network appliance, and even that the device's power switch is on. The present invention further permits an action to power-cycle the individual network appliance, to return it to operational status by forcing a reboot.
A pass-through communication switch is preferably included with power manager 28 that is installed in the same equipment rack with other network appliances because many network appliances have RS-232 network management system ports. Such management ports are intended to permit users to upload new software and to update and inspect configuration tables. A call-pass-through multi-port communications switch allows the initial communications session with modem RS-232 or TCP/IP to be switched directly to a device's management port. For example, when a communications session is established to reboot a locked up router, after the router is back in operation, the same communications session can be transferred from the power manager 28 to the router's management port. Preferably, such transfer of the particular communications session can be switched directly from a user interface screen in communication with the SNMP agent 46. The network operator can thereafter continue the repair operation by inspecting or updating the router's configuration table, and to verify its operability.
User interfaces are preferably provided to be configured by a system administrator at the SNMP manager 20. A screen interface allows an operator to control individual intelligent power modules 30, 32, 34, 36, directly from an associated keyboard. A command interface preferably allows script files to be constructed and sent directly for execution. Response codes are returned after each command is executed. Group names are preferably supported which allows a single command to control multiple devices.
The power manager 28 preferably supports a variety of communication interfaces, such as, RS-232 and ETHERNET. Out-of-band communications are connectable through an RS-232 interface using a DB9-type connector on a back panel. Such a port is used to establish communications sessions. An external dial-in-modem can also be used to establish communications. In-band communications are preferably provided with a LAN communications interface that supports ETHERNET connections, e.g., 10BaseT or 10Base2, with both IPX and TCP/IP protocols being supported.
A seven layer network communications model that is universally used to communicate between most types of computer networks is defined by the International Organization of Standards (ISO). Every layer relies on all its lower layers to complete its communication tasks. There are seven layers identified as the application, presentation, session, transport, network, data link, and physical layers. For example, e-mail is a task of the application layer. The application layer uses all of the layers below it to deliver particular e-mail messages to their destinations. The presentation layer formats the look of the e-mail, and the physical layer actually transports the binary data across the network. For more information, see, Naugle, Matthew G., Local Area Networking, (McGraw-Hill: New York), 1991.
The information that the SNMP manager 20 can gather from the SNMP agents 22 and 24 around a network is the definition of the MIB and it has a hierarchical tree structure. At the top of the tree is the general network information. Each branch of the tree gets more detailed about a specific network area. The leaves of the tree include the most detail. A device may be a parent in the tree, and its children can be discrete serial and parallel devices. Each node in the MIB tree can be represented by a variable. The top of a local area network MIB tree is usually referred to as “internet”.
Managed objects are accessed via the MIB and are defined using a subset of ASN.1. Each object type is named by an object identifier, which is an administratively assigned name. The object type and an object instance uniquely identify a specific object. Descriptor text strings are used to refer to the object type.
Network information is exchanged with protocol data unit (PDU) messages, which are objects that contain variables and have both titles and values. SNMP uses five types of PDUs to monitor a network. Two deal with reading terminal data, two deal with setting terminal data, and one, the trap, is used for monitoring network events such as terminal start-ups or shut-downs. When a user wants to see if a terminal is attached to the network, for example, SNMP is used to send out a read PDU to that terminal. If the terminal is attached, the user receives back a PDU with a value “yes, the terminal is attached”. If the terminal was shut off, the user would receive a packet informing them of the shutdown with a trap PDU.
In alternative embodiments of the present invention, it may be advantageous to include the power manager and intelligent power module functions internally as intrinsic components of an uninterruptable power supply (UPS). In applications where it is too late to incorporate such functionally, external plug-in assemblies are preferred such that off-the-shelf UPS systems can be used.
Although the present invention has been described in terms of the present embodiment, it is to be understood that the disclosure is not to be interpreted as limiting. Various alterations and modifications will no doubt become apparent to those skilled in the art after having read the above disclosure. Accordingly, it is intended that the appended claims be interpreted as covering all alterations and modifications as fall within the true spirit and scope of the invention.

## Claims

1. A method of using a power manager application to control operating power supplied to a plurality of power outputs within an electrical power distribution system, the method comprising:
providing, by at least a processor, a login interface having administrative capabilities;
providing a power output identifying interface;
providing an administrative grouping interface including a power outputs selection section that identifies a first sub-plurality of power outputs of said power outputs to be included in a first administrative group, and at least a second sub-plurality of power outputs of said power outputs to be included in at least a second administrative group;
providing a configuration entry interface corresponding to the first administrative group;
providing an administrative group manipulation interface to manipulate the first administrative group;
determining another configuration corresponding to the second administrative group and providing an interface to manipulate the second administrative group;
providing a digital current value interface to display a digital current value provided by a digital current value reporting system for the electrical power distribution system, wherein the electrical power distribution system has a power input and is connectable to provide power to one or more electrical loads in an electrical equipment rack, the digital current value reporting system being (i) in digital current value determining communication with at least one among the power input and said plurality of power outputs, and (ii) connectable in digital current value transfer communication with the power manager application; and
providing an operating power control interface, including an administrative group operating power control section to control a supply of operating power to the power outputs in the administrative groups.

2. The method of claim 1, further comprising providing a configuration change interface to change the configurations corresponding to the administrative groups.

3. The method of claim 1, wherein the step of providing a login interface is performed through an interface comprising a keyboard.

4. The method of claim 1, wherein the step of providing an administrative group manipulation interface comprises providing an add/delete a username interface.

5. The method of claim 1, wherein the step of providing an administrative group manipulation interface comprises providing a password change interface.

6. The method of claim 1, wherein the step of providing an administrative groups manipulation interface comprises providing a modem initialization data rate interface.

7. The method of claim 1, wherein the step of providing an administrative groups manipulation interface comprises providing a configuration modification interface.

8. The method of claim 7, wherein further comprising saving a configuration modification to non-volatile RAM.

9. The method of claim 1, wherein the step of providing an administrative groups manipulation interface comprises providing a user interface to allow an operator to control operating power supplied to the administrative groups.

10. The method of claim 1, wherein the step of providing an administrative groups manipulation interface comprises providing a user interface to allow an operator to control operating power supplied to the administrative groups.