USRE41030E1 - System and method of network independent remote configuration of internet server appliance - Google Patents
System and method of network independent remote configuration of internet server appliance Download PDFInfo
- Publication number
- USRE41030E1 USRE41030E1 US11/241,901 US24190105A USRE41030E US RE41030 E1 USRE41030 E1 US RE41030E1 US 24190105 A US24190105 A US 24190105A US RE41030 E USRE41030 E US RE41030E
- Authority
- US
- United States
- Prior art keywords
- network
- message
- configuration
- computer
- broadcast
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0866—Checking the configuration
- H04L41/0873—Checking configuration conflicts between network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99932—Access augmentation or optimizing
Definitions
- the present invention is generally related to the configuration and management of network connected computer systems and, in particular, to a server appliance that is automatically network adaptive to an otherwise unknown connected network and, further, is configurable securely over the network without requiring prior local configuration of the server.
- TCP/IP transmission control protocol/internet protocol
- NIC network interface card
- MAC media access control
- the IP layer of a TCP/IP stack is soft-assigned an IP address that is at least intended to be unique.
- the IP address is either statically assigned through an initial configuration procedure performed locally to the computer system or dynamically assigned through the operation of a conventional pull-protocol, such as the dynamic host configuration protocol (DHCP). Since using a static IP assignment is incompatible with using a DHCP, a computer system must be specifically pre-configured individually with either a static IP address or as a DHCP client before any meaningful interoperation with a connected network is possible.
- DHCP dynamic host configuration protocol
- IP address ranges have been established to define different classes of networks.
- Network masks are used to further partition networks with the purpose of establishing identified local network segments.
- the IP stack conventionally supports a network routing table that identifies gateways on the local network segment that can be used as the nomitive destination for data packets intended for remote network segments. Gateway computer systems use this mechanism to screen out and ignore data packets intended for network segments different from their own or that comply with a route pre-established in the gateway routing table. This selectivity is required to prevent all of the gateway connected network segments from being flooded.
- a direct consequence is that a computer system must be installed with a static or DHCP provided dynamic IP address that is compatible with the directly connected network segment in order for the computer system to work within that network environment. If the IP address is not compatible, other locally connected computer systems will simply be unable to communicate with the incompatible network computer system.
- a general purpose of the present invention is to provide an efficient method and system for enabling the initial configuration and subsequent reconfiguration of a network connected computer system, such as a server appliance, to be performed remotely through the network.
- the server appliance includes a host computer system including a network interface controller and an operating system, executable by the host computer system, that is configurable by a defined set of network values for transmitting and receiving data packets through the network interface controller without network configuration conflicts.
- a control program executable by the host computer system in conjunction with the operating system, determines, on initial start-up and specifically with respect to the communications network, an initial set of network values to configure the operating system.
- the control program is subsequently responsive to a first broadcast data packet containing network configuration parameters that are used to determine and apply a second set of network values to configure the operating system, which are then applied as the operating configuration of the operating system with respect to the network.
- An advantage of the present invention is that, independent of the configuration of any other clients and servers connected to a network, a network server appliance can be initially connected to the network and immediately become configurable entirely through the network. No local terminal device, whether provided as a built-in display and keypad or connectable through a serial port, is required to enter any initial network configuration values.
- Another advantage of the present invention is that server appliances and other network computer systems constructed to embody the present invention have significantly lowered direct and indirect costs.
- the initial self-configuration capability provided by the present invention removes the hardware cost of any integrated local terminal and port connectivity for a mobile terminal as well as the cost of providing on-site configuration support, whether through a technician visit or other technical support mechanisms.
- Still another advantage of the present invention is that reinitialization of the network settings may be performed anytime a conflict with any other client or server on the network is detected during the power-on initialization of the present invention. This allows systems implementing the present invention to be added and changed between existing networks without conflicting with the network settings of any other clients or servers connected to the network.
- server appliances constructed according to the present invention are digitally serialized and, further, may be digitally signed, to ensure uniqueness of systems otherwise identically constructed.
- the digital signing of the serialization ensures that unauthorized construction of otherwise identical system is detectable.
- Still another advantage of the present invention is that remote communications with a configuration client application are encrypted to limit exposure of the configuration information to examination and potential spoofing even though transmitted as part of broadcast data packets.
- An authentication mechanism may also be utilized to ensure that communications of network configuration parameters only occur between the configuration client application and network appliance.
- a yet further advantage of the present invention is that, pending the acceptability of a network settings configuration by the configuration client application, static ARP routes may be installed by the server appliance and configuration client computer system to enable non-broadcast communications, thereby avoiding broadcast loading of the network, as well as security issue issues with the repeated broadcast of configuration information.
- FIG. 1 is a general illustration of a network server appliance operating in a network operating environment
- FIG. 2 is a block diagram of a network operating system and server management application configured in accordance with a preferred embodiment of the present invention
- FIG. 3 provides a process diagram of the preferred start-up sequence of a server appliance implemented in accordance with the present invention
- FIG. 4 provides a process diagram of the operation of a client configuration control application in accordance with a preferred embodiment of the present invention
- FIG. 5A provides a process diagram of the initial operation of the present invention in response to a broadcast inquiry for identification of server appliances awaiting configuration in accordance with a preferred embodiment of the present invention
- FIG. 5B provides a process diagram of the initial configuration of a network server through remote network communications with a client configuration control application in accordance with a preferred embodiment of the present invention.
- FIG. 6 provides a process diagram of the preferred construction and serialization of server appliances in accordance with the present invention.
- a server appliance is described as implementing the system and methods of the present invention.
- This server appliance is preferably a type of computer system generally optimized for use as a Web server, application server, file server, firewall, or other similar specific function computer system. These optimizations are generally directed to the size (or volume), power requirements, CPU performance, and I/O performance of the server appliance.
- the system and methods of the present invention are equally applicable and effective when used with other types of computer systems, including general purpose personal, workstation, and server computer systems and dedicated function computers, such as routers.
- a server appliance 12 may be connected to both a local area network (LAN) 14 and wide area network (WAN) 16 through separate NIC interfaces.
- the server appliance 12 operates as a network gateway between the LAN network 14 and the WAN network 16 , including any other networks that may be connected to the WAN network 16 .
- These other networks may include the Internet 18 , which is accessible through a router 20 .
- the server appliance 12 operates to selectively isolate network traffic that occurs on the LAN and WAN networks 14 , 16 .
- other computer systems 22 , 24 connected to the LAN network 14 are not exposed to the potentially high bandwidth traffic that may occur on the WAN network 16 .
- private traffic on the LAN network 14 is not exposed on the WAN network 16 to other computers or servers 28 , other networks 18 , or distant computer systems 26 .
- the present invention provides for the initial installation configuration and subsequent reconfiguration of the server appliances 12 , 28 , or a client computer system 24 , to an existing LAN network 14 having an attached and operating network client computer system 22 .
- the client computer system 22 executes a configuration control application, which implements a network configuration management process.
- the configuration control application preferably includes a local repository of configuration information established for the LAN network 14 and the WAN network 16 .
- the scope of network configuration control by the configuration control application is limited to those networks that are connected to the LAN, LAN network 14 that can exchange network broadcast data packets with the LAN network 14 .
- the locally connected client computer system 24 and the server appliance 12 are both immediately within the potential scope of configuration control of the configuration control application.
- the server appliance 28 will be within the scope of configuration control once the configuration of the server appliance 12 is established to enable the routing of broadcast data packets between the networks 14 , 16 .
- a configuration control boundary is preferably established by the router 20 by blocking all broadcast data packets to or from the Internet 18 . Although the router 20 blocks the routing of broadcasts between network segments, the router 20 may nonetheless respond to and be configured in response to broadcasts that can be sufficiently authenticated by the router 20 .
- the server appliances 12 , 28 preferably execute a network operating system, such as the LinuxTM operating system, which supports the execution of an application level program that implements the configuration protocols of the present invention.
- a network operating system such as the LinuxTM operating system
- the preferred network operating system environment includes an operating system kernel 32 that supports conventional interfaces to the TGP TCP and UDP layers 34 , 36 of a TCP/IP stack.
- the UDP layer is specifically used for the transmission and reception of network broadcast messages.
- An IP layer 38 operates in conjunction with an IP table 40 that stores the IP address assigned to the IP layer 38 , as well as the IP routing information used by the IP layer 38 . IP addresses are resolved by a network layer 42 against an address resolution protocol (ARP) table 44 to determine actual network paths between IP address identified computer systems.
- ARP address resolution protocol
- One or more NIC drivers 46 may be installed in the TCP/IP stack to support the hardware dependencies of physical layer NICs 48 , 50 .
- Each of the NICs 48 , 50 are is provided with a MAC address 52 , 54 typically stored in a read-only memory located on the NICs 48 , 50 .
- a configuration management application 56 is preferably executed on each of the server appliances 12 , 28 , within the application execution environment supported by the operating system kernel 32 .
- the configuration management application supports a socket-level connection through the operating system kernel 32 with the TCP/IP stack. This allows fully qualified IP address TCP connections to be established through the TCP 34 and IP 38 layers to other computer systems present on a locally connected network, network 14 , 16 . IP broadcast connections are routed through the operating system kernel 32 and the UDP layer 36 .
- the configuration management application 56 has the ability, consistent with the preferred embodiments of the present invention, to establish broadcast-based communications with other computer systems through the locally connected network 14 , 16 .
- a modified DHCP server 58 is also preferably provided and potentially executed on each of the server appliances 12 , 28 .
- the configuration management application 56 is preferably capable of both enabling and disabling execution of the DHCP server 58 .
- the configuration management application is also able to direct the operation of the DHCP server to issue a DHCP protocol discovery request and to receive the results of that request.
- a conventional DHCP server receives and responds to DHCP discovery requests from a network 14 , 16 , which are originated by remote DHCP clients.
- the DHCP server 58 is modified to allow the server 58 to itself issue a discover request to the networks 14 , 16 in order to identify the operating presence of any remote DHCP server connected to and serving the networks 14 , 16 .
- the presence or absence of a responding remote DHCP server on the networks 14 , 16 is reported back to the configuration management application 56 .
- the configuration management application 56 is preferably capable of using the conventional capabilities of the operating system kernel 32 to provide and set IP alias addresses and static ARP addresses.
- an IP alias can be specified by the configuration management application through the appropriate operating system kernel 32 interface to have the IP address set 60 in the IP table 40 as an equivalent IP identifier for the TCP/IP stock stack.
- the IP layer 38 will therefore operate to recognize the IP alias address as a proper source and destination address for this TCP/IP stock stack.
- static ARP table 44 entries can be explicitly specified by the configuration management application 56 . These entries are then set 60 in the ARP table 44 along with those entries that are automatically discovered from the attached networks 14 , 16 through the conventional operation of the ARP protocols. Consequently, systems, systems such as the configuration management client can be explicitly identified by an ARP entry where such an entry would not otherwise be automatically entered.
- a status flag 62 is preferably provided as an indicator of the configuration status of the network server 12 , 28 .
- This status flag 62 is preferably persistent through the use of some non-volatile memory, such as a NVRAM or a disk file. Since the server appliances 12 , 28 utilize an Intel®-type industry standard architecture motherboard, which includes a battery-backed CMOS memory, server appliances without local disks could use the CMOS memory to store the status flag 62 . In the preferred embodiments of the present invention, however, the operating system is loaded and operated from a local disk.
- a registry data structure, stored in a disk file is preferably used to store the status flag 62 . This registry is also preferably used to store other persistent information defining the configuration parameters of the server appliance 12 .
- the boot-up process implemented by a server appliance 12 generally in accordance with the present invention is shown in FIG. 3 .
- Sections of the preferred process implementation are also provided in pseudocode form in Tables 1 through 4.
- POST power-on self-test
- the configuration management application 56 is preferably started automatically as a background or daemon process.
- a current IP address and netmask are assumed by the server appliance 12 . These values are the default values set during the factory construction of the sever appliance 12 , where the server appliance 12 has not been previously configured. Alternately, the IP and netmask are assumed from their last configured values, which may be values corresponding to the currently connected network or another entirely different network against which the server appliance was previously configured.
- the validity of the assumed IP and netmask values are not determined from the state of the status flag 62 .
- the status flag 62 may be reset to indicate that the server appliance 12 is in an uninitialized (SERVER_UNINTIALIZED) state.
- the IP address and netmask values may also be reset to their default values.
- the present invention provides for an initial IP address conflict check 74 , as indicated by the call to the checkIPConflict() routine in Table 1, independent of the state of the status flag 62 .
- this call initiates an ARP interrogation of the locally connected network to obtain a list of all known IP addresses that are actively connected to the network. A comparison is then made to determine whether the IP address assumed by the server appliance 12 will be in conflict with the IP address assigned to any other computer system connected to the local network.
- the IP conflict check implemented by the present invention makes no assumption about the nature of the local network, specifically in regard to how IP addresses are assigned. There is no reliance on the prior existence and proper configuration of a DHCP server on the local network. Further, there is no requirement for preconfiguring the server appliance 12 to specifically use either a network compatible static IP address or to operate as a DHCP client to acquire a compatible IP address. As will be evident, the present invention operates from the assumed IP address and netmask even if those values are incompatible with the local network.
- an error message is generated 78 .
- this message is provided to alert the system administrator of the occurrence of an unexpected IP address conflict.
- the present invention provides for automatically resolving any detected IP address conflict.
- the list of IP addresses in use is scanned 80 (Table 3) to identify an IP address that is not in use.
- an unused IP address is selected and set 82 as the IP address of the server appliance 12 .
- the state of the server flag 62 indicates that the server appliance 12 has been previously configured
- the assumption is made that another device or computer system has been erroneously configured and is the source of the conflict.
- An error message is preferably generated 78 .
- a scan 80 is then performed and a free IP address is selected. While this IP address might be set as a new IP address for the server appliance 12 , preferably the IP address is set 82 as an IP alias for the server appliance 12 , respecting the presumed choice of the IP address earlier configured into the server appliance.
- either a probe of the locally connected network or a previously configured registry value will determine whether a DHCP server is started on the server appliance 12 .
- a DHCP configuration registry value is checked 86 on an initialized server appliance 12 to determine whether to start 88 the DHCP server 58 .
- the server appliance 12 then enters the normal run state 90 of the operating system 32 .
- the configuration management system 56 remains operative in a wait state receptive to further configuration management commands to configure or reconfigure the server appliance 12 .
- the DHCP server is pre-emptively started 92 under the continuing control of the configuration management application 58 .
- a DHCP discovery process is initiated and responses from other DHCP servers are collected. Based on the collected responses, if any, the configuration management application 56 determines 96 to stop the DHCP server 58 or directly continue to the run state 90 .
- a configuration control application 100 is preferably executed by a network client computer system. 22 .
- This application 100 once initialized 102 , issues a broadcast message 104 to the locally connected network 14 .
- Any server appliance 12 that receives this broadcast message preferably responds with a broadcast message including a unique identifier of the responding server appliance 12 .
- a list of the responding server appliances 12 is collected 106 by the configuration control application 100 and, in a preferred embodiment of the present invention, is presented as a pick-list of server appliances to be configured. From the selection of a server appliance 12 to configure, a process of providing configuration parameters 108 from the configuration control application 100 to the configuration management application 56 to con figure 110 the server appliance 12 is then performed. This process of configuration 108 , 110 is preferably performed through a series of broadcast messages that are secure 112 relative to other computer systems and server appliances that can receive the broadcast messages.
- the configuration data exchanged by these broadcast messages in encrypted based on a password established between the configuration management and control applicants applications 56 , 100 .
- the first transaction between a configuration control application 100 and the configuration management application preferably forces the establishment of a new administration password that is then effectively unique to the particular instance of the server appliance 12 . Encryption of the configuration data is then based directly or indirectly on this password.
- the broadcast configuration messages provide a server appliance 12 with sufficient information to determine how to adapt to the network environment of the connected local network.
- the server appliance 12 is not necessarily configured sufficiently to enable direct communications with any other computer system attached to the local network.
- the IP address and netmask values assumed by the server appliance 12 may be entirely incompatible with those of the connected local network.
- the IP address and netmask values assumed by the server appliance 12 , those assigned to the client computer system 22 executing the configuration control application 100 , or those assigned to some other computer system or device connected to the local network may be in actual conflict with one another.
- the present invention nonetheless, enables communications between the configuration control client computer system 22 and the server appliance 12 sufficient to enable the server appliance 12 to determine and adapt to the network environment requirements of the locally connected network.
- An initial configuration transaction using get_server_info_command (clientNet) provides the configuration management application 56 with the network environment settings of the configuration control client 22 .
- a data structure such as listed in Table 5, is provided as a basis for a server appliance to evaluate and adapt to the local network environment.
- the configuration management application 56 preferably responds with an acknowledgment broadcast message, such as ackNetInfo(serverLAN), confirming to the client control application 100 the IP address and netmask of the server appliance 12 and that no conflicts or network incompatibilities are detected.
- the configuration control application 100 then preferably establishes a non-broadcast-based TCP/IP connection with the server appliance 12 and proceeds with any remaining configuration of the server appliance 12 .
- the configuration management application 56 preferably first checks to determine the source of the conflict by executing the check_IP_conflict(serverLAN.ipAddress) routine. If a server IP address conflict is determined to exist, a resolve_server_IP_conflict(serverLAN) routine, generally as listed in Table 6, is executed.
- resolveServerIPConflict int resolveServerIPConflict(NET_INFO serverLAN) ⁇ if (authenticateClient( ) ! AUTHENTICATED) ⁇ /* determine whether the get_server_info_command( ) includes a correct administration password.
- the configuration management application 56 determines and sets a non-conflicted IP alias address for the server appliance 12 .
- the selection of this IP address is conditional on the acceptance of the IP address by the configuration control application 100 through the presentation of the IP address as a selectable option of the configuration parameters 108 .
- clientNet.ipAlias findAvailableIP(clientNet); /* find an available IP in the client network and set the clientNet.ipAlias to the available IP. This is to inform the client that there is a conflict, in case the client is not capable of detecting its IP conflict condition.
- clientNet.ipAlias findAvailableIP(clientNet); /* find an available IP in the client network and set the clientNet.ipAlias to the available IP. This is to inform the client that there is a conflict, in case the client is not capable of detecting its IP conflict condition.
- */ setStaticARP(clientNet); /* Overwrite the ARP table with a static entry to associate the client Physical Address with the client IP address. This way a connection to the client can always be guaranteed. Note: the ARP static entry for the client IP will always be removed after the connection is closed. */ ⁇
- the configuration management application 56 is able to force the association of an otherwise unused IP address with the configuration control client 22 by the setting of a corresponding static ARP entry. In effect, this establishes a reverse IP alias for the configuration control client 22 for the server appliance 12 .
- a broadcast message is sent from the server appliance 12 to the configuration control client to acknowledge the conflict-resolved configuration of the server appliance 12 .
- the configuration control application 100 again preferably establishes a non-broadcast-based TCP/IP connection with the server appliance 12 and proceeds with any remaining configuration of the server appliance 12 .
- the configuration management application determines that there is a network incompatibility between the server appliance 12 and the configuration control client 22 , specifically that the appliance 12 and client 22 are configured for different networks
- the configuration management application additionally executes a resolveIPalias(clientNet) routine.
- This routine performs an IP address scan for an unused IP address within the client compatible network identified from the clientNet data structure.
- a setIPAlias(clientLAN.ipAlias, clientNet) routine is then executed with the result that an IP alias address is established for the server appliance 12 in and compatible with the client network environment.
- the server appliance 12 is both responsible for and capable of self-adaptation into the client network environment.
- a non-broadcast TCP/IP connection can then be established between the server appliance 12 and the configuration control client 22 .
- a message may be sent to the configuration management application 56 to finalize the server configuration.
- this re-initialization message may result 114 in the restarting of some service processes, a reload or reboot of the operating system, or no action at all.
- the configuration control application 100 determines 116 whether there are any remaining unconfigured server appliances. The process of providing configuration parameters 108 may automatically continue with any unconfigured server appliance 12 . Alternately, the operator of the configuration control application 100 may elect to reconfigure any of the server appliances 12 .
- the process 120 of responding by the configuration management application 56 to broadcast inquiries involves propagating 122 the data contained in the broadcast through the TCP/IP stack 30 to the configuration management application 56 .
- the process 120 is preferably a thread of the configuration management application 56 that remains active on the server appliance 12 and monitoring for IP connections on a defined well-known port.
- the contents of a broadcast data packet received on this port are preferably evaluated by the configuration management application 56 , potentially including to determine the release level or type of the configuration control application 100 .
- Other validation or authentication checks may also be made at this point, such as determining whether the inquiry is received through a NIC adapter connected to a public WAN or a private LAN.
- the configuration management application determines that a response is appropriate 124 , a broadcast data packet is prepared 126 with the UMID of the server appliance 12 , or at least corresponding to the NIC adapter through which the original broadcast inquiry was received.
- the process operation 130 of the configuration management application 56 is further detailed in FIG. 5 B.
- Client broadcast messages containing a particular UMID, and therefore intended for a specific server appliance 12 are detected and routed 132 for decryption and authentication 134 .
- the resulting data is then analyzed 136 to, for example, extract a clientNet data structure. Based on the analysis 136 , an IP address scan 140 and tentative setting of an IP address or alias 142 may be performed as needed 138 to handle conflicts and network incompatibilities.
- the resulting server network environment information (serverNet) is then collected and encrypted 144 before being sent 146 as a broadcast reply to the configuration control application 100 .
- the effectively proposed server network environment settings are provided to the configuration control application 100 for prior approval.
- the tentative setting of network parameters by the configuration management application 56 allows the configuration control application 100 the opportunity to provide a clientNet data structure reflecting a different network environment to the configuration management application. This allows the configuration control application 100 to cause the configuration management application 56 to adapt the network environment of, for example, a server appliance 28 to a network 16 different from that of the configuration control client 22 .
- a broadcast acceptance message is sent to the UMID identified configuration management application 56 .
- This message type is recognized 132 and checked 148 to determine if the proposed configuration is acceptable or not. If not accepted, the IP address scan 140 and set 142 is repeated and the new network environment parameters of the server 12 , 28 are again sent 146 . Where accepted 148 , however, a static ARP entry is set 150 and a server acknowledgment message is prepared 144 and sent 146 .
- Other, typically subsequent and non-broadcast messages are also received from the configuration control application 100 . These messages are routed 132 and decrypted and authenticated 134 as before. Based on the identified type of these messages, the data content analysis 136 preferably retrieves different data structures from the message content. The resulting data is used to identify and provide a basis basis, if not the actual value value, for establishing 152 other configuration settings of the server appliance 12 , 28 including, but not limited to, network environment settings that are not handled by the DHCP protocol. These additional parameters preferably correspond to the hostname, security domain, and access permissions. As these additional parameters are successfully set, corresponding server acknowledgment messages are prepared 144 and sent 146 .
- the preferred process 160 of initially configuring server appliances 12 , 28 for operation is generally shown in FIG. 6 .
- the base assembly 162 of a server appliance 12 preferably including an image copy of a disk drive containing the operating system and configuration management application
- the hardware configuration is recorded in a database 164 organized by system identifiers.
- Each server appliance 12 is then serialized 166 .
- This serialization includes establishing an initial unique hostname and setting a pseudo-random IP address for the server appliance 12 .
- This hostname is preferably constructed by concatenating a defined prefix string, such as “SA,” with at least a portion of the MAC address from the specific LAN NIC adapter included in the construction of the server appliance 12 .
- the IP address is preferably constructed as the concatenation of the first two octets of a Class-A network and the least significant sixteen bits of the MAC address.
- the serialized hostname and IP address values are used as permanent identifiers of a particular server appliance 12 .
- These values, and potentially hardware specific values such as the MAC address of any included NIC or NICs and the microprocessor hardware identifier code, may be used as the basis of a digital signature that is then coded into the configuration of the operating system.
- These values, including the digital signature if used, are also preferably recorded in the database 164 against the server identifier for the particular server appliance 12 .
- the server appliance 12 is then ready for shipment, installation, and operation.
- corresponding fixes and updates may be downloaded from, in effect, the manufacturing or maintenance facility for the server appliances 12 .
- Any request for the update may be required to be validated 172 against the data stored in the database 164 .
- Any server appliances 12 built without going through the serialization process 160 will therefore not be eligible for updates.
- any update obtained through the verification process 172 preferably will be specific to the serialization information stored in the database 164 for the downloading server appliance 12 .
- the update can therefore be made to be unusable by any other server appliance 12 . If the update is also digitally signed, there is little chance that the update can be manipulated for use by other than a single server appliance 12 .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
TABLE 1 |
IP Check, Scan and Set |
If (checkIPConflict(serverLAN.ipAddress) == TRUE) { |
/* Use ARP protocol to find out whether the boot up LAN IP Address | |
assignment conflicts with another device in the network */ | |
If (SERVER_UNINTIALIZED == TRUE) { |
serverLAN.ipAddress == findAvailableIP(serverLAN); |
/* find an available IP Address in the server network space. | |
Note: there is no client network known yet. */ |
setIP(serverLAN.ipAddress); |
/* change the LAN IP Address to the available IP */ |
} else { |
serverLAN.err = ERR_LAN_IP_ADDRESS_CONFLICT; |
// Set error flag |
errAlarm( ); | // Report the fatal errors. |
// This fatal error could be reported via several means: |
// broadcast in the existing network | |
// email, paging, set alarm tone |
serverLAN.ipAlias = findAvailableIP(serverLAN); |
// find an available IP Address in the server network |
setIPAlias(serverLAN.ipAlias, serverNet); |
/* Set IP Alias for LAN interface with an avaialbe IP in the server | |
network */ |
} |
} |
TABLE 2 |
checkIPconflict |
STRUCT_PHYS_ADDR *checkIPconflict(STRUCT_IP ipAddress) { |
/* Use gratuitous ARP protocol to obtain the list of PHYS_ADDR of |
all network device with ipAddress. |
- Return a pointer to the buffer that contains the physical addresses |
of the devices with ipAddress (which indicate a conflict condition). |
- Return NULL if there is no conflict. |
Note: the ARP sender does not answer the ARP request and is |
excluded. */ |
} |
TABLE 3 |
findAvailIP |
STRUCT_IP findAvailIP(NET_INFO netInfo) { |
/* Sequence through all possible IP address of the network specified in |
netInfo to locate an available IP address by using the checkIPconflict( ) |
routine. |
Return the first IP that has no conflict. |
Return all ones (binary) if there is no IP available in the network. |
*/ |
} |
TABLE 4 |
DHCP Detect |
/* Probe the network for an existing DHCP Server if this is an |
unintialized server * |
If (SERVER_UNITIALIZED == TRUE) { |
If (DHCP_Server_Exist( ) == TRUE) { |
Do_not_load_DHCP Server( ); |
} else { |
Load_DHCP Server( ); | /* To Allow DHCP Clients Adapt its IP | |
settings so that it is compatible with | ||
the default Server setup. */ |
} |
} else { | /* If the server is intialized, then the registry will |
determine whether to load the DHCP server. */ |
if (registry(DHCP_SERVER_ENABLED) { |
Load_DHCP Server( ); |
} |
} |
TABLE 5 |
Data Structure |
struct NET_INFO { | |
STRUCT_IP ipAddress; | // IP Address |
STRUCT_NETMASK netmask; | // Netmask |
STRUCT_IP IP_Alias; | // IP alias, if any 0 means none. |
STRUCT_PHYS_ADDR physicalAddress; |
/* Physical Address of the interface, 0 means not found, all ones |
means not applied. */ |
STRUCT_ERR err; | // status of the interface |
} clientNet, serverLAN, serverWAN; | |
From the given client IP address and netmask, the
TABLE 6 |
resolveServerIPConflict |
int resolveServerIPConflict(NET_INFO serverLAN) { |
if (authenticateClient( ) != AUTHENTICATED) { /* determine whether the |
get_server_info_command( ) includes a correct administration | |
password. */ |
return ERR_NOT_AUTHENTICATED; |
} | |
for (int i=0; i < MAX_RETRIES; i++) { |
err = NO_ERR; | // NO_ERR == no error |
serverLAN.ipAlias = findAvailableIP(clientNet); |
/* find an available IP in the client network and set the | |
serverLAN.ipAlias to the available IP */ |
setIPAlias(serverLAN.ipAlias, clientNet); |
/* set the server LAN IP alias so that it is compatible with the | |
client Network */ |
broadcast(MSG_IP_RESOLUTION_OFFER, allInfo); |
/* broadcast all necessary info to client which includes the | |
serverLAN and clientNet data structure */ |
startTimeOut(MAX_TIME_OUT); | // start the timeout timer |
waitMsg(revMessage); | /* wait for a message back from | |
the client */ |
if ((revMessage( ) != MSG_IP_RESOLUTION_OFFER_ACK) || |
((timeout( ) == TRUE) { | // Error condition | |
removeIPAlias)serverLAN.ipAlias); |
if (timeout( ) == TRUE) err = ERR_TIME_OUT; |
else err = NACK; |
} else { |
break; | // client ACK on the OFFER |
} |
} | |
if (err != NO_ERR) { |
errHandler( ); | |
return; |
} | |
setStaticARP(clientNet); |
/* Overwrite the ARP table with a static entry to associate the client | |
Physical Address with the client IP address. This way a connection to | |
the client can always be guaranteed. Note: the ARP static entry for | |
the client IP will always be removed after the connection is closed. | |
*/ |
} |
TABLE 7 |
resolveClientIPConflict |
int resolveClientIPConflict(NET_INFO clientNet) { |
clientNet.ipAlias = findAvailableIP(clientNet); |
/* find an available IP in the client network and set the | |
clientNet.ipAlias to the available IP. This is to inform the client that | |
there is a conflict, in case the client is not capable of detecting its IP | |
conflict condition. */ |
setStaticARP(clientNet); |
/* Overwrite the ARP table with a static entry to associate the client | |
Physical Address with the client IP address. This way a connection to | |
the client can always be guaranteed. Note: the ARP static entry for | |
the client IP will always be removed after the connection is closed. */ |
} |
Claims (36)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/241,901 USRE41030E1 (en) | 2000-03-01 | 2005-09-30 | System and method of network independent remote configuration of internet server appliance |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/516,386 US6629145B1 (en) | 2000-03-01 | 2000-03-01 | System and method of network independent remote configuration of internet server appliance |
US11/241,901 USRE41030E1 (en) | 2000-03-01 | 2005-09-30 | System and method of network independent remote configuration of internet server appliance |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/516,386 Reissue US6629145B1 (en) | 2000-03-01 | 2000-03-01 | System and method of network independent remote configuration of internet server appliance |
Publications (1)
Publication Number | Publication Date |
---|---|
USRE41030E1 true USRE41030E1 (en) | 2009-12-01 |
Family
ID=28455016
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/516,386 Ceased US6629145B1 (en) | 2000-03-01 | 2000-03-01 | System and method of network independent remote configuration of internet server appliance |
US11/241,901 Expired - Lifetime USRE41030E1 (en) | 2000-03-01 | 2005-09-30 | System and method of network independent remote configuration of internet server appliance |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/516,386 Ceased US6629145B1 (en) | 2000-03-01 | 2000-03-01 | System and method of network independent remote configuration of internet server appliance |
Country Status (1)
Country | Link |
---|---|
US (2) | US6629145B1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090170496A1 (en) * | 2007-12-27 | 2009-07-02 | Motorola, Inc. | Device and method of managing data communications of a device in a network via a split tunnel mode connection |
US20100266131A1 (en) * | 2009-04-20 | 2010-10-21 | Bart Cilfone | Natural action heuristics for management of network devices |
US20130198349A1 (en) * | 2012-01-31 | 2013-08-01 | Edward Allen Wright | Remote server configuration |
EP3163311A1 (en) | 2011-10-18 | 2017-05-03 | Iltron, Inc. | Traffic management and remote configuration in a gateway-based network |
Families Citing this family (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7392281B1 (en) * | 2000-02-25 | 2008-06-24 | Navic Systems, Inc. | System and method for providing guaranteed delivery of messages to embedded devices over a data network |
US7330824B1 (en) | 2000-02-25 | 2008-02-12 | Navic Systems, Inc. | Method and system for content profiling and activation |
US6714992B1 (en) * | 2000-02-25 | 2004-03-30 | Navic Systems, Inc. | Method and system for embedded network device installation |
EP1188164B1 (en) * | 2000-04-05 | 2011-10-05 | Sony United Kingdom Limited | Identifying and processing of audio and/or video material |
US7194072B2 (en) * | 2000-04-19 | 2007-03-20 | Gamble Oliver W | Method and system for remotely accessing and controlling remote devices |
US6842769B1 (en) | 2000-05-05 | 2005-01-11 | Interland, Inc. | Automatically configured network server |
DE10053809A1 (en) * | 2000-10-30 | 2002-05-08 | Philips Corp Intellectual Pty | Ad hoc network with several terminals for determining terminals as controllers of sub-networks |
US7152099B1 (en) * | 2000-10-31 | 2006-12-19 | Hewlett-Packard Development Company, Lp. | Friend configuration and method for network devices |
US7047273B2 (en) | 2000-11-28 | 2006-05-16 | Navic Systems, Inc. | Load balancing in set top cable box environment |
US7313610B2 (en) * | 2001-02-13 | 2007-12-25 | Siemens Ag | Method and array for determining internet protocol addresses of a terminal array |
US7487253B1 (en) * | 2001-04-03 | 2009-02-03 | F5 Networks, Inc. | Method for configuring a network element having an unknown protocol address |
GB2374756B (en) * | 2001-04-20 | 2004-07-28 | Discreet Logic Inc | Image processing |
GB2374749B (en) * | 2001-04-20 | 2005-04-06 | Discreet Logic Inc | Image data processing |
US20030018758A1 (en) * | 2001-07-13 | 2003-01-23 | Changguan Fan | Generically provisioning an appliance |
US20030088701A1 (en) * | 2001-11-05 | 2003-05-08 | Mross Robert Warren | Establishing network addresses for network devices |
JP2003271429A (en) * | 2002-03-15 | 2003-09-26 | Hitachi Ltd | Storage device resource managing method, storage resource managing program, recording medium recording the program, and storage resource managing device |
US8140642B1 (en) * | 2002-05-17 | 2012-03-20 | Mcafee, Inc. | Network connection-independent updating system and method |
US7281056B1 (en) * | 2002-06-04 | 2007-10-09 | Hewlett-Packard Development Company, L.P. | Assigning a device to a network |
US20040179537A1 (en) * | 2003-03-11 | 2004-09-16 | Motorola, Inc. | Method and apparatus providing a mobile server function in a wireless communications device |
US20040243841A1 (en) * | 2003-06-02 | 2004-12-02 | Stumpf Bradley W. | Network configuration using scannable token |
US7568025B2 (en) * | 2003-06-27 | 2009-07-28 | Bank Of America Corporation | System and method to monitor performance of different domains associated with a computer system or network |
DE10329858A1 (en) * | 2003-07-02 | 2005-01-27 | Siemens Ag | Method for configuring a device in a data network |
US8631163B1 (en) | 2003-12-11 | 2014-01-14 | At&T Intellectual Property Ii, L.P. | Automatic connectivity determiner and configurator |
US7383429B2 (en) * | 2003-12-18 | 2008-06-03 | Hewlett-Packard Development Company, L.P. | Configuring settings of a computer system to be compatible with an operating system |
US7809809B2 (en) * | 2004-01-13 | 2010-10-05 | Nokia Corporation | Client provisioning using application characteristics template with flag parameters |
US7420934B2 (en) * | 2004-02-20 | 2008-09-02 | Dell Products L.P. | System and method for maintaining network connectivity during remote configuration of an information handling system |
US7668944B2 (en) * | 2004-02-20 | 2010-02-23 | Evgeny Leib | System and unified setting interface for configuring network manageable devices |
US9160811B2 (en) * | 2004-08-10 | 2015-10-13 | Nokia Technologies Oy | Client provisioning with enhanced linking |
US7483963B2 (en) * | 2004-08-20 | 2009-01-27 | Research In Motion Limited | Method and system for configuring a client on host devices by utilizing an interface between a configuration application and host device drivers on a configuring device |
US20060070120A1 (en) * | 2004-09-02 | 2006-03-30 | Brother Kogyo Kabushiki Kaisha | File transmitting device and multi function device |
WO2006102904A2 (en) * | 2005-03-31 | 2006-10-05 | Bang & Olufsen A/S | Table based distributed control for a network of consumer electronics |
US8443094B2 (en) * | 2005-05-12 | 2013-05-14 | Oracle America, Inc. | Computer system comprising a communication device |
US8667106B2 (en) * | 2005-05-20 | 2014-03-04 | At&T Intellectual Property Ii, L.P. | Apparatus for blocking malware originating inside and outside an operating system |
US7929452B2 (en) * | 2005-06-30 | 2011-04-19 | Intel Corporation | Internet protocol (IP) address sharing and platform dynamic host configuration protocol (DHCP) mediator |
US8688800B2 (en) * | 2005-10-05 | 2014-04-01 | Hewlett-Packard Development Company, L.P. | Remote configuration of persistent memory system ATT tables |
US7633888B1 (en) | 2005-11-15 | 2009-12-15 | S2 Security Corporation | System and method to configure a network node |
US7734738B2 (en) * | 2007-01-17 | 2010-06-08 | Microsoft Corporation | Automatic configuration of client and server networking |
US8041785B2 (en) * | 2007-01-17 | 2011-10-18 | Microsoft Corporation | Programmatically choosing a router configuration provider |
US20080244063A1 (en) * | 2007-03-26 | 2008-10-02 | Vinayak Risbud | Automatically detecting managed servers in a network |
EP2150026A1 (en) * | 2008-07-31 | 2010-02-03 | Nokia Siemens Networks OY | Configuration of a communication device |
US8631086B2 (en) | 2008-09-30 | 2014-01-14 | International Business Machines Corporation | Preventing messaging queue deadlocks in a DMA environment |
KR20100040658A (en) * | 2008-10-10 | 2010-04-20 | 삼성전자주식회사 | Method and apparatus for preventing ip address conflict in remote access service of upnp network |
US8671172B2 (en) * | 2009-07-09 | 2014-03-11 | International Business Machines Corporation | Network device configuration |
EP2716003B1 (en) | 2011-06-03 | 2016-09-28 | Oracle International Corporation | System and method for authenticating components in a network |
US9401963B2 (en) * | 2012-06-04 | 2016-07-26 | Oracle International Corporation | System and method for supporting reliable connection (RC) based subnet administrator (SA) access in an engineered system for middleware and application execution |
US9532224B2 (en) * | 2012-11-05 | 2016-12-27 | Electronics And Telecommunications Research Institute | Method of device-to-device discovery and apparatus thereof |
CN104394206A (en) * | 2014-11-19 | 2015-03-04 | 黑龙江大学 | System and method for controlling ARM9-based radio station network |
US10313259B2 (en) | 2016-12-09 | 2019-06-04 | Vmware, Inc. | Suppressing broadcasts in cloud environments |
CN106878088A (en) * | 2017-03-10 | 2017-06-20 | 郑州云海信息技术有限公司 | A kind of method of the configuration server data transfer based on linux |
US20230328054A1 (en) * | 2021-06-14 | 2023-10-12 | Kelly Dao Xuan Nguyen | Autonomous control and secure communications system and methods for sensors |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5812819A (en) * | 1995-06-05 | 1998-09-22 | Shiva Corporation | Remote access apparatus and method which allow dynamic internet protocol (IP) address management |
US5854901A (en) * | 1996-07-23 | 1998-12-29 | Cisco Systems, Inc. | Method and apparatus for serverless internet protocol address discovery using source address of broadcast or unicast packet |
US5884038A (en) * | 1997-05-02 | 1999-03-16 | Whowhere? Inc. | Method for providing an Internet protocol address with a domain name server |
US6101182A (en) * | 1996-04-18 | 2000-08-08 | Bell Atlantic Network Services, Inc. | Universal access multimedia data network |
US6101499A (en) * | 1998-04-08 | 2000-08-08 | Microsoft Corporation | Method and computer program product for automatically generating an internet protocol (IP) address |
US20010005858A1 (en) * | 1996-08-29 | 2001-06-28 | Shuji Ohno | Automatic address distributing system |
US20020133573A1 (en) * | 1998-11-12 | 2002-09-19 | Toru Matsuda | Method and apparatus for automatic network configuration |
US6678732B1 (en) * | 1998-08-10 | 2004-01-13 | Fujitsu Limited | Dynamic host configuration protocol server for allocating IP addresses to a plurality of clients |
US6892229B1 (en) * | 1998-09-30 | 2005-05-10 | 3Com Corporation | System and method for assigning dynamic host configuration protocol parameters in devices using resident network interfaces |
US7281036B1 (en) * | 1999-04-19 | 2007-10-09 | Cisco Technology, Inc. | Method and apparatus for automatic network address assignment |
-
2000
- 2000-03-01 US US09/516,386 patent/US6629145B1/en not_active Ceased
-
2005
- 2005-09-30 US US11/241,901 patent/USRE41030E1/en not_active Expired - Lifetime
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5812819A (en) * | 1995-06-05 | 1998-09-22 | Shiva Corporation | Remote access apparatus and method which allow dynamic internet protocol (IP) address management |
US6101182A (en) * | 1996-04-18 | 2000-08-08 | Bell Atlantic Network Services, Inc. | Universal access multimedia data network |
US5854901A (en) * | 1996-07-23 | 1998-12-29 | Cisco Systems, Inc. | Method and apparatus for serverless internet protocol address discovery using source address of broadcast or unicast packet |
US20010005858A1 (en) * | 1996-08-29 | 2001-06-28 | Shuji Ohno | Automatic address distributing system |
US5884038A (en) * | 1997-05-02 | 1999-03-16 | Whowhere? Inc. | Method for providing an Internet protocol address with a domain name server |
US6101499A (en) * | 1998-04-08 | 2000-08-08 | Microsoft Corporation | Method and computer program product for automatically generating an internet protocol (IP) address |
US6678732B1 (en) * | 1998-08-10 | 2004-01-13 | Fujitsu Limited | Dynamic host configuration protocol server for allocating IP addresses to a plurality of clients |
US6892229B1 (en) * | 1998-09-30 | 2005-05-10 | 3Com Corporation | System and method for assigning dynamic host configuration protocol parameters in devices using resident network interfaces |
US20020133573A1 (en) * | 1998-11-12 | 2002-09-19 | Toru Matsuda | Method and apparatus for automatic network configuration |
US7039688B2 (en) * | 1998-11-12 | 2006-05-02 | Ricoh Co., Ltd. | Method and apparatus for automatic network configuration |
US20060155833A1 (en) * | 1998-11-12 | 2006-07-13 | Toru Matsuda | Method and apparatus for automatic network configuration |
US7281036B1 (en) * | 1999-04-19 | 2007-10-09 | Cisco Technology, Inc. | Method and apparatus for automatic network address assignment |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090170496A1 (en) * | 2007-12-27 | 2009-07-02 | Motorola, Inc. | Device and method of managing data communications of a device in a network via a split tunnel mode connection |
US8139515B2 (en) * | 2007-12-27 | 2012-03-20 | Motorola Mobility, Inc. | Device and method of managing data communications of a device in a network via a split tunnel mode connection |
US20100266131A1 (en) * | 2009-04-20 | 2010-10-21 | Bart Cilfone | Natural action heuristics for management of network devices |
US8819781B2 (en) * | 2009-04-20 | 2014-08-26 | Cleversafe, Inc. | Management of network devices within a dispersed data storage network |
EP3163311A1 (en) | 2011-10-18 | 2017-05-03 | Iltron, Inc. | Traffic management and remote configuration in a gateway-based network |
US10200476B2 (en) | 2011-10-18 | 2019-02-05 | Itron, Inc. | Traffic management and remote configuration in a gateway-based network |
US20130198349A1 (en) * | 2012-01-31 | 2013-08-01 | Edward Allen Wright | Remote server configuration |
US9973385B2 (en) * | 2012-01-31 | 2018-05-15 | Hewlett Packard Enterprise Development Lp | Remote server configuration |
Also Published As
Publication number | Publication date |
---|---|
US6629145B1 (en) | 2003-09-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
USRE41030E1 (en) | System and method of network independent remote configuration of internet server appliance | |
US7152099B1 (en) | Friend configuration and method for network devices | |
US8914787B2 (en) | Registering software management component types in a managed network | |
EP1766860B1 (en) | Method and system for dynamic device address management | |
US8285981B2 (en) | Remote network device provisioning | |
US7912958B2 (en) | Method and apparatus for automatic IP allocation bootstrapping of embedded network management cards used in networked uninterruptible power supplies and other supported devices | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | Routing AppleTalk | |
Cisco | Routing AppleTalk | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | AppleTalk Remote Access Commands | |
Cisco | Routing AppleTalk | |
Cisco | Routing AppleTalk | |
Cisco | Routing AppleTalk | |
Cisco | Routing AppleTalk |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AVAYA INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CYBERIQ SYSTEMS, INC.;REEL/FRAME:019960/0383 Effective date: 20011017 Owner name: AVAYA TECHNOLOGY CORP., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AVAYA, INC.;REEL/FRAME:019960/0390 Effective date: 20020124 |
|
AS | Assignment |
Owner name: AVAYA INC, NEW JERSEY Free format text: REASSIGNMENT;ASSIGNORS:AVAYA TECHNOLOGY LLC;AVAYA LICENSING LLC;REEL/FRAME:021156/0287 Effective date: 20080625 Owner name: AVAYA INC,NEW JERSEY Free format text: REASSIGNMENT;ASSIGNORS:AVAYA TECHNOLOGY LLC;AVAYA LICENSING LLC;REEL/FRAME:021156/0287 Effective date: 20080625 |
|
AS | Assignment |
Owner name: AVAYA TECHNOLOGY LLC, NEW JERSEY Free format text: CONVERSION FROM CORP TO LLC;ASSIGNOR:AVAYA TECHNOLOGY CORP.;REEL/FRAME:022677/0550 Effective date: 20050930 Owner name: AVAYA TECHNOLOGY LLC,NEW JERSEY Free format text: CONVERSION FROM CORP TO LLC;ASSIGNOR:AVAYA TECHNOLOGY CORP.;REEL/FRAME:022677/0550 Effective date: 20050930 |
|
AS | Assignment |
Owner name: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE, PENNSYLVANIA Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC., A DELAWARE CORPORATION;REEL/FRAME:025863/0535 Effective date: 20110211 Owner name: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLAT Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC., A DELAWARE CORPORATION;REEL/FRAME:025863/0535 Effective date: 20110211 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE, PENNSYLVANIA Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:030083/0639 Effective date: 20130307 Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE, Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:030083/0639 Effective date: 20130307 |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
AS | Assignment |
Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS INC.;OCTEL COMMUNICATIONS CORPORATION;AND OTHERS;REEL/FRAME:041576/0001 Effective date: 20170124 |
|
AS | Assignment |
Owner name: AVAYA INTEGRATED CABINET SOLUTIONS INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION), CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST, NA;REEL/FRAME:044892/0001 Effective date: 20171128 Owner name: OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: VPNET TECHNOLOGIES, INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INTEGRATED CABINET SOLUTIONS INC., CALIFORNI Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.;REEL/FRAME:045012/0666 Effective date: 20171128 |
|
AS | Assignment |
Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:045034/0001 Effective date: 20171215 Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW Y Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:045034/0001 Effective date: 20171215 |
|
AS | Assignment |
Owner name: CITIBANK, N.A., AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:045124/0026 Effective date: 20171215 |
|
AS | Assignment |
Owner name: AVAYA INTEGRATED CABINET SOLUTIONS LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001 Effective date: 20230403 Owner name: AVAYA MANAGEMENT L.P., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001 Effective date: 20230403 Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001 Effective date: 20230403 Owner name: AVAYA HOLDINGS CORP., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001 Effective date: 20230403 |
|
AS | Assignment |
Owner name: AVAYA MANAGEMENT L.P., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: CAAS TECHNOLOGIES, LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: HYPERQUALITY II, LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: HYPERQUALITY, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.), NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: VPNET TECHNOLOGIES, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: OCTEL COMMUNICATIONS LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: AVAYA INTEGRATED CABINET SOLUTIONS LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: INTELLISIST, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 |