FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR ATTACHING ONE OR MORE TEMPORARY INTERNET PROTOCOL ADDRESSES TO TARGET
NODES”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR ATTACHING ONE OR MORE TEMPORARY INTERNET PROTOCOL ADDRESSES TO TARGET NODES
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to installation of operating system using servers. More particularly, embodiments of the present disclosure relate to a method and system for attaching one or more temporary internet protocol (IP) addresses to one or more target nodes.
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] An operating system (OS) falls into a category of a system software. The OS is responsible for managing a plurality of resources of a computer. The OS acts as an interface between the software and a plurality of components of the computer or a computer hardware. The OS has the ability to manage multiple resources and multiple operation of the computer. The OS is fully integrated set of specialized programs designed to handle a plurality of operations of the computer such as inputting, processing, outputting, storing, and controlling. The OS controls and monitors an execution of one or more programs that are stored in the computer such as application programs. Further, the OS is a collection of software for managing one or more computer hardware resources and provide a set of services for the computer programs. While the OS plays an important role in user friendliness and functionality within the computers, however the installation process of the OS extends beyond individual systems to one or more servers and one or more network environment for supporting multiple workstations and terminals which are connected on the network such as local area network (LAN). For instance, the OS may facilitate two or more nodes to share one or more resources.

[0004] Conventionally, the OS is installed in the computer/server manually by an operator. The manual process of installation of the OS, choosing the OS, choosing a backup of a data, choosing an installation media, configuring the OS, and the restoring the data.
[0005] Moreover, the manual installation of the OS additionally involve logging into an Out-Of-Band (OOB) graphical interface (GUI), setting one or more boot configurations, attaching a standard image uniform resource locator (URL) to a virtual media, rebooting a server, and manually selecting one or more option while the server is rebooting. The newly installed OS (operating system) does not have a default IP address of its own, therefore it is required to access the server using a temporary IP address for accessing the server, it is required to attach an IP, and this process is done manually. The manual procedure of attaching an IP address involves logging into OS via OOB (Out-Of-Band) management Graphical user interface (GUI) and run commands to configure IP address. This invention helps automate temporary IP address attachment on multiple target nodes in a parallel manner. Temporary IP address according to the present solution is the IP address which does not persist over reboot, and its purpose is to access server to make further configurations.
[0006] Thus, there exists an imperative need in the art to provide a system and method for attaching one or more temporary internet protocol (IP) addresses to one or more target nodes, which the present disclosure aims to address.
SUMMARY
[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0008] According to an aspect of the present disclosure, a method for attaching one or more temporary internet protocol (IP) addresses to one or more target nodes is disclosed. The method includes receiving, by a transceiver unit, at a central controller, one or more Out-Of-Band (OOB) login credentials for the one or more target nodes. The method further includes receiving, by the transceiver unit, at the central controller, one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes. The method furthermore includes executing, by a processing unit, at

the central controller, a configure IP script to initiate temporary attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on one or more host servers.
[0009] In an exemplary aspect of the present disclosure, the temporary attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers, comprises: initiating, by the processing unit, at the central controller, an OS install script for installation of one or more OS in the one or more target nodes, from the one or more host servers; logging, by the processing unit, at the central controller, to the one or more target nodes; executing, by the processing unit, at the central controller, one or more ansible scripts; and parsing, by the processing unit, at the central controller, one or more ansible script logs to detect one of a successful attachment status and an unsuccessful attachment status of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers.
[00010] In an exemplary aspect of the present disclosure, installation of one or more OS
in the one or more target nodes, comprises configuring, by a configuration unit, at the central controller, one or more image Uniform Resource Locators (image URLs) associated with the one or more OS to be installed in the one or more target nodes, for one or more host servers.
[00011] In an exemplary aspect of the present disclosure, the successful attachment
status, and the unsuccessful attachment status of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers, is displayed at the user interface of the central controller.
[00012] In an exemplary aspect of the present disclosure, the one or more OOB login
credentials for the one or more target nodes are received, by a user input, at a user interface of the central controller.
[00013] In an exemplary aspect of the present disclosure, the one or more Secure Socket
Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes, are received by the user input at the user interface of the central controller.

[00014] In an exemplary aspect of the present disclosure, the temporary attachment of
the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers, does not persist on rebooting of the one or more host servers.
[00015] According to an aspect of the present disclosure, a system for attaching one or
more temporary internet protocol addresses to one or more target nodes is disclosed. The system comprises a transceiver unit, at a central controller, configured to: receive, one or more Out-Of-Band (OOB) login credentials for the one or more target nodes; receive, one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes. The system further comprises a processing unit, configured to execute, at the central controller, a configure IP script to initiate temporary attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on one or more host servers.
[00016] Another aspect of the present disclosure provides a User Equipment (UE) for
attaching one or more temporary internet protocol addresses to one or more target nodes. The UE includes a processor configured to receive one or more Out-Of-Band (OOB) login credentials for the one or more target nodes; receive one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes; and execute a configure IP script to initiate temporary attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on one or more host servers..
[00017] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for attaching one or more temporary internet protocol addresses to one or more target nodes the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit, at a central controller, to receive, one or more Out-Of-Band (OOB) login credentials for the one or more target nodes; the transceiver unit, at the central controller, to receive, one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes; a processing unit, at a central controller, to execute, at the central controller, a configure IP script to initiate temporary attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on one or more host servers.

OBJECTS OF THE INVENTION
[00018] Some of the objects of the present disclosure, which at least one embodiment
disclosed herein satisfies are listed herein below.
[00019] It is an object of the present disclosure to provide method for attaching one or
more temporary internet protocol (IP) addresses to one or more target nodes.
[00020] It is another object of the present disclosure to automatically attach SSH (secure
shell) management IP address to an operating system (OS).
[00021] It is yet another object of the present disclosure for attaching the SSH IP
addresses to multiple servers in parallel manner, which speeds up deployment process and scales up the network.
DESCRIPTION OF THE DRAWINGS
[00022] The accompanying drawings, which are incorporated herein, and constitute a
part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[00023] FIG. 1 illustrates an exemplary block diagram of a computing device upon
which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[00024] FIG. 2 illustrates an exemplary block diagram of a system for attaching one or
more temporary internet protocol addresses to one or more target nodes, in accordance with exemplary implementations of the present disclosure.
5 [00025] FIG. 3 illustrates a method flow diagram for attaching one or more temporary
internet protocol addresses to one or more target nodes, in accordance with exemplary implementations of the present disclosure.
[00026] FIG. 4 illustrates an exemplary block diagram of a system architecture for
10 attaching one or more temporary internet protocol addresses to one or more target nodes, in
accordance with exemplary implementations of the present disclosure.
[00027] FIG. 5 illustrates an exemplary block diagram of a user equipment (UE) for
attaching one or more temporary internet protocol addresses to one or more target nodes, in
15 accordance with exemplary implementations of the present disclosure.
[00028] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
20 DETAILED DESCRIPTION
[00029] In the following description, for the purposes of explanation, various specific
details are set forth in order to provide a thorough understanding of embodiments of the present
disclosure. It will be apparent, however, that embodiments of the present disclosure may be
25 practiced without these specific details. Several features described hereafter may each be used
independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
30 [00030] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various
7

changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[00031] Specific details are given in the following description to provide a thorough
5 understanding of the embodiments. However, it will be understood by one of ordinary skill in
the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
10 [00032] Also, it is noted that individual embodiments may be described as a process
which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed
15 but could have additional steps not included in a figure.
[00033] The word “exemplary” and/or “demonstrative” is used herein to mean serving
as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as
20 “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or
advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar
25 to the term “comprising” as an open transition word—without precluding any additional or
other elements.
[00034] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for processing
30 instructions. A processor may be a general-purpose processor, a special purpose processor, a
conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding
35 data processing, input/output processing, and/or any other functionality that enables the
8

working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[00035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a
5 smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless
communication device”, “a mobile communication device”, “a communication device” may
be any electrical, electronic and/or computing device or equipment, capable of implementing
the features of the present disclosure. The user equipment/device may include, but is not limited
to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital
10 assistant, tablet computer, wearable device or any other computing device which is capable of
implementing the features of the present disclosure. Also, the user device may contain at least
one input means configured to receive an input from at least one of a transceiver unit, a
processing unit, a storage unit, a detection unit and any other such unit(s) which are required
to implement the features of the present disclosure.
15
[00036] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a form
readable by a computer or similar machine. For example, a computer-readable medium
includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk
20 storage media, optical storage media, flash memory devices or other types of machine-
accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[00037] As used herein “interface” or “user interface refers to a shared boundary across
25 which two or more separate components of a system exchange information or data. The
interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
30 [00038] All modules, units, components used herein, unless explicitly excluded herein,
may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field
35 Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
9

[00039] As used herein the transceiver unit include at least one receiver and at least one
transmitter configured respectively for receiving and transmitting data, signals, information, or
a combination thereof between units/components within the system and/or connected with the
5 system.
[00040] As used herein, Out-Of-Band (OOB) login credentials refers to the
authentication information used to access and manage network elements through an
independent management channel separate from primary network traffic. These credentials
10 typically include a username and password and may also encompass additional security
measures such as multifactor authentication tokens or digital certificates.
[00041] As used herein, one or more target nodes refers to any network entities or
computing devices that are intended to be configured or managed within the system. The target
15 nodes can include, but are not limited to, servers, virtual machines, or other types of endpoints
within a telecommunications network or data centre environment. The target nodes are the entities that receive temporary IP address attachments and subsequent operating system installations and configurations as described in the present disclosure.
20 [00042] As used herein, OOB IP address refers to an Out-Of-Band Internet Protocol
address utilized for the management and maintenance of network elements. OOB IP addresses
are dedicated IP addresses that provide a separate and secure channel for network
administrators to perform administrative tasks such as configuration, monitoring, and
troubleshooting of target nodes independently from the primary network traffic.
25
[00043] As used herein, Secure Socket Shell (SSH) Internet Protocol (IP) address refers
to a cryptographic network protocol for operating network services securely over an unsecured
network. SSH is commonly used for remote command-line login and execution, and it provides
a secure channel over an unsecured network by using a client-server architecture.
30
[00044] As used herein, IP script refers to a predefined set of executable instructions
designed to configure and manage Internet Protocol (IP) addresses on networked devices. The
IP script automates the process of assigning, modifying, and validating IP addresses on target
nodes within a network, ensuring that each device is correctly configured for communication.
35 The IP script can include commands for logging into devices using secure protocols, such as
10

Secure Socket Shell (SSH), and for making temporary IP address attachments that facilitate further configuration tasks.
[00045] As used herein, OS install script refers to a sequence of automated instructions
5 executed to facilitate the installation of one or more operating systems (OS) on the one or more
target nodes. The OS install script is responsible for initiating the download of the necessary OS images from Uniform Resource Locators ( URLs) for performing the installation process.
[00046] As used herein, ansible scripts refers to a set of automation scripts written in
10 YAML (Yet Another Markup Language) that are utilized to automate the deployment,
configuration, and management of network services and infrastructure. Ansible scripts operate
within the framework of the Ansible automation platform, which is designed to streamline the
provisioning of software and hardware resources in a networked environment. These scripts
enable the execution of various tasks such as installing software packages, configuring network
15 settings, and orchestrating complex workflows across multiple nodes in a network.
[00047] As used herein, image Uniform Resource Locators (URLs) refers to the specific
addresses on the network that point to the location of operating system images used for
installation on target nodes. Each URL provides a direct link to an OS image stored on one or
20 more host servers, ensuring that the correct version and configuration of the operating system
is retrieved and installed.
[00048] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-mentioned and other
25 existing problems in this field of technology by providing method and system for attaching one
or more temporary internet protocol addresses to one or more target nodes.
[00049] FIG. 1 illustrates an exemplary block diagram of a computing device [100] (also
referred herein as computer system [100]) upon which the features of the present disclosure
30 may be implemented in accordance with exemplary implementation of the present disclosure.
In an implementation, the computing device [100] may also implement a method for attaching one or more temporary internet protocol (IP) addresses to one or more target nodes utilising the system. In another implementation, the computing device [100] itself implements the method for attaching one or more temporary internet protocol addresses to one or more target
11

nodes using one or more units configured within the computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[00050] The computing device [100] may include a bus [102] or other communication
5 mechanism for communicating information, and a processor [104] coupled with bus [102] for
processing information. The processor [104] may be, for example, a general purpose microprocessor. The computing device [100] may also include a main memory [106], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [102] for storing information and instructions to be executed by the processor [104]. The main
10 memory [106] also may be used for storing temporary variables or other intermediate
information during execution of the instructions to be executed by the processor [104]. Such instructions, when stored in non-transitory storage media accessible to the processor [104], render the computing device [100] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [100] further
15 includes a read only memory (ROM) [108] or other static storage device coupled to the bus
[102] for storing static information and instructions for the processor [104].
[00051] A storage device [110], such as a magnetic disk, optical disk, or solid-state drive
is provided and coupled to the bus [102] for storing information and instructions. The
20 computing device [100] may be coupled via the bus [102] to a display [112], such as a cathode
ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command selections to the processor
25 [104]. Another type of user input device may be a cursor controller [116], such as a mouse, a
trackball, or cursor direction keys, for communicating direction information and command
selections to the processor [104], and for controlling cursor movement on the display [112].
This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a
second axis (e.g., y), that allow the device to specify positions in a plane.
30
[00052] The computing device [100] may implement the techniques described herein
using customized hard-wired logic, one or more ASICs or FPGAs, firmware, and/or program
logic which in combination with the computing device [100] causes or programs the computing
device [100] to be a special-purpose machine. According to one implementation, the techniques
12

herein are performed by the computing device [100] in response to the processor [104]
executing one or more sequences of one or more instructions contained in the main memory
[106]. Such instructions may be read into the main memory [106] from another storage
medium, such as the storage device [110]. Execution of the sequences of instructions contained
5 in the main memory [106] causes the processor [104] to perform the process steps described
herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[00053] The computing device [100] also may include a communication interface [118]
10 coupled to the bus [102]. The communication interface [118] provides a two-way data
communication coupling to a network link [120] that is connected to a local network [122]. For
example, the communication interface [118] may be an integrated services digital network
(ISDN) card, cable modem, satellite modem, or a modem to provide a data communication
connection to a corresponding type of telephone line. As another example, the communication
15 interface [118] may be a local area network (LAN) card to provide a data communication
connection to a compatible LAN. Wireless links may also be implemented. In any such
implementation, the communication interface [118] sends and receives electrical,
electromagnetic, or optical signals that carry digital data streams representing various types of
information.
20
[00054] The computing device [100] can send messages and receive data, including
program code, through the network(s), the network link [120] and the communication interface
[118]. In the Internet example, a server [130] might transmit a requested code for an application
program through the Internet [128], the ISP [126], the local network [122], host [124] and the
25 communication interface [118]. The received code may be executed by the processor [104] as
it is received, and/or stored in the storage device [110], or other non-volatile storage for later
execution.
[00055] The computing device [100] encompasses a wide range of electronic devices
30 capable of processing data and performing computations. Examples of computing device [100]
include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computing device [100] may include peripheral devices, such as monitors, keyboards, and
13

printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.
[00056] Referring to FIG. 2, an exemplary block diagram of a system [200] for attaching
5 one or more temporary internet protocol addresses (IP) to one or more target nodes, is shown,
in accordance with the exemplary implementations of the present disclosure. The system [200] comprises at least one central controller [200a], at least one transceiver unit [202], at least one processing unit [204], and at least one configuration unit [206]. In an exemplary aspect, the central controller [200a] includes the transceiver unit [202], processing unit [204] and the
10 configuration unit [206]. Also, all of the components/ units of the system [200] are assumed to
be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 2 only a few units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said units, as required to implement the
15 features of the present disclosure. Further, in an implementation, the system [200] may be
present in a user device to implement the features of the present disclosure. The system [200] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system [200] may reside in a server or a network entity. In yet another implementation, the system [200] may
20 reside partly in the server/ network entity and partly in the user device.
[00057] The system [200] is configured for attaching one or more temporary internet
protocol (IP) addresses to one or more target nodes with the help of the interconnection between
the components/units of the system.
25
[00058] The system comprises a transceiver unit [202], at a central controller [200a],
configured to receive, one or more Out-Of-Band (OOB) login credentials for the one or more
target nodes. For example, an IT administrator needs to configure several servers within a data
centre. Each server is equipped with an OOB management interface, such as an Integrated
30 Lights-Out (iLO) or a Baseboard Management Controller (BMC), which allows for remote
management independent of the operating system. The OOB login credentials include essential
authentication details such as usernames, passwords, and possibly additional security tokens or
certificates required to access these interfaces. When initiating the configuration process, the
administrator inputs these OOB credentials into the central controller [200a]. The transceiver
14

unit [202] is responsible for securely receiving and storing these credentials. For example, the
administrator might provide a list of target nodes with corresponding OOB IP addresses and
their respective login credentials. The transceiver unit [202] at the central controller [200a]
receives this information through a user interface or a configuration file. Once the credentials
5 are received, the transceiver unit [202] ensures they are available for subsequent operations,
such as logging into the target nodes to perform temporary IP address attachments.
[00059] Further, the one or more Out-Of-Band (OOB) login credentials include a user
identifier and a password. The user identifier may be numeric, alphabetic, alpha-numeric or
10 any other known format. Also, the user identifier may have a fixed set of characters. Further,
the password may be numeric, alphabetic, alpha-numeric, symbolic or any other known format. Also, the password may be a single word or a phrase to access the OOB. The one or more Out-Of-Band (OOB) login credentials aims to differentiate between an authorized access and an unauthorized access. In an exemplary aspect of the present disclosure, the one or more target
15 nodes may be network nodes such as desktop computer, a laptop, a server, and a virtual
machine.
[00060] The transceiver unit [202] is further configured to receive, one or more Secure
Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP
20 addresses for the one or more target nodes. For example, an IT administrator is preparing to
configure several servers, each server requires both an SSH IP address for secure
communication and an OOB IP address for management access. The SSH IP address is used
for secure command-line interface (CLI) access, while the OOB IP address allows for remote
management and monitoring of the server hardware.
25
[00061] When the administrator initiates the configuration process, they input both the
SSH IP addresses and the corresponding OOB IP addresses for each target node into the central
controller [200a]. The transceiver unit [202] captures this information. Each target node can be
accessed both via its secure CLI and its management interface. For example, a list may be
30 provided where each entry contains an SSH IP address and its corresponding OOB IP address.
The one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective
one or more OOB IP addresses for the one or more target nodes, are received by the user input
at the user interface of the central controller [200a].
15

[00062] The system [200] further comprises a processing unit [204] communicatively
coupled to the transceiver unit [202]. The processing unit [204] is configured to execute, at the
central controller [200a], a configure IP script to initiate temporary attachment of the one or
more SSH IP addresses with the respective one or more OOB IP addresses for each of the one
5 or more target nodes, on one or more host servers. For example, once the transceiver unit [202]
receives the SSH IP address and OOB IP address for each target node, the processing unit [204] utilizes this information to start the configuration process. The configure IP script is designed to log into each target node using the OOB IP address and the provided login credentials. Once logged in, the script temporarily assigns the corresponding SSH IP address
10 to the target node. For example, if the first target node has an OOB IP address of 10.0.0.1 and
an SSH IP address of 192.168.1.10, the processing unit [204] executes the configure IP script to log into the node at 10.0.0.1, then assigns 192.168.1.10 as the temporary SSH IP address. This process is repeated for each target node in the system, such as logging into 10.0.0.2 to assign 192.168.1.11 and logging into 10.0.0.3 to assign 192.168.1.12.
15
[00063] The processing unit [204] initiates IP attachment operation by running the
script, based on the OOB login credentials and the respective SSH IP address. In an exemplary aspect, the temporary attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host
20 servers is temporary and does not persist on rebooting of the one or more target nodes (such as
servers). Further, for rebooting the one or more target nodes, the processing unit [204] sends a reboot command to the one or more target nodes. In an exemplary aspect, the one or more host servers may be a physical server or cloud-based server.
25 [00064] The present disclosure encompasses that for the temporary attachment of the
one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers, by the processing unit [204], at the central controller [200a], the processing unit [204] is further configured to initiate, an OS install script for installation of one or more OS in the one or more target nodes. The processing
30 unit [204] is also configured to login to the one or more target nodes, execute one or more
ansible scripts, and parse one or more ansible script logs to detect one of a successful attachment status and an unsuccessful attachment status of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers. For example, after the processing unit [204] attaches the SSH IP
16

address temporarily to the target node using its OOB IP address, it initiates an OS install script.
The script may involve downloading an OS image from a repository and beginning the
installation process on the target node. Suppose the first target node has an OOB IP address of
10.0.0.1 and an SSH IP address of 192.168.1.10; the processing unit [204] logs into the node
5 at 10.0.0.1 using the OOB interface and starts the OS install script to install the necessary
operating system. Following the OS installation, the processing unit [204] uses the temporarily attached SSH IP address to log in to the target node. This step ensures that the secure communication channel is established via SSH for further configurations. The processing unit [204] then executes one or more ansible scripts on the target node. These ansible scripts are
10 responsible for performing additional configuration tasks required to prepare the node for its
intended operation within the network. Once the ansible scripts are executed, the processing unit [204] parses the logs generated by these scripts to determine the status of the IP attachment process. It checks the logs to detect whether the temporary attachment of the SSH IP address to the respective OOB IP address was successful or unsuccessful for each target node. For
15 example, if the log indicates that the SSH IP address 192.168.1.10 was successfully attached
to the target node with OOB IP address 10.0.0.1, the processing unit [204] records this as a successful attachment. Conversely, if there was an error or failure in the process, it records an unsuccessful attachment status.
20 [00065] In an exemplary aspect, installation of one or more OS in the one or more target
nodes, comprises configuring, by a configuration unit [206], at the central controller [200a], one or more image Uniform Resource Locators (image URLs) associated with the one or more OS to be installed in the one or more target nodes, for one or more host servers. For example, after the processing unit [204] temporarily attaches the SSH IP address to the target node using
25 its OOB IP address, it initiates an OS install script. Suppose the first target node has an OOB
IP address of 10.0.0.1 and an SSH IP address of 192.168.1.10. The processing unit [204] logs into the node at 10.0.0.1 using the OOB interface and starts the OS installation. The configuration unit [206] at the central controller [200a] sets up the necessary image URLs, such as "http://repository.example.com.iso," for the required OS. The processing unit [204], using
30 these configured image URLs, directs the target nodes to download and install the OS from the
specified locations, ensuring each node receives the correct OS image. The central controller [200a] manages this automated process, leveraging the configuration unit [206] to streamline the setup. Once the OS installation is initiated, the processing unit [204] logs in to the target nodes using the temporarily attached SSH IP address, executes one or more ansible scripts for
17

further configuration, and parses the ansible script logs to detect the success or failure of the attachment and configuration processes.
[00066] Further, the successful attachment status and the unsuccessful attachment status
5 of the one or more SSH IP addresses with the respective one or more OOB IP addresses for
each of the one or more target nodes, on the one or more host servers, is displayed at a user interface of the central controller [200a].
[00067] For example, after the processing unit [204] attempts to attach the SSH IP
address to the target node using its OOB IP address, the system monitors the success or failure of this operation. The results, indicating whether the SSH IP address attachment was successful or unsuccessful for each target node, are then shown on the user interface of the central controller [200a]. This allows administrators to easily verify the status of each node's IP configuration directly from a central dashboard.
[00068] In an embodiment, the one or more OOB login credentials for the one or more
target nodes are received, by a user input, at a user interface of the central controller [200a]. In another embodiment, the one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes, are received by a user input at a user interface of the central controller [200a].
[00069] Referring to FIG. 3, an exemplary method flow diagram [300] for attaching one
or more temporary internet protocol addresses to one or more target nodes, in accordance with
exemplary implementations of the present disclosure is shown. In an implementation the
25 method [300] is performed by the system [200]. Further, in an implementation, the system
[200] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 3, the method [300] starts at step [302].
[00070] At step [304], the method [300] comprises receiving, by a transceiver unit [202],
30 at a central controller, one or more Out-Of-Band (OOB) login credentials for the one or more
target nodes.
[00071] For example, an IT administrator needs to configure several servers within a
data centre. Each server is equipped with an OOB management interface, such as an Integrated
35 Lights-Out (iLO) or a Baseboard Management Controller (BMC), which allows for remote
18

management independent of the operating system. The OOB login credentials include essential
authentication details such as usernames, passwords, and possibly additional security tokens or
certificates required to access these interfaces. When initiating the configuration process, the
administrator inputs these OOB credentials into the central controller [200a]. The transceiver
5 unit [202] is responsible for securely receiving and storing these credentials. For example, the
administrator might provide a list of target nodes with corresponding OOB IP addresses and
their respective login credentials. The transceiver unit [202] at the central controller [200a]
receives this information through a user interface or a configuration file. Once the credentials
are received, the transceiver unit [202] ensures they are available for subsequent operations,
10 such as logging into the target nodes to perform temporary IP attachments.
[00072] Further the one or more Out-Of-Band (OOB) login credentials include a user
identifier and a password. The user identifier may be numeric, alphabetic, alpha-numeric or any other known format. Also, the user identifier may have a fixed set of characters. Further,
15 the password may be numeric, alphabetic, alpha-numeric, symbolic or any other known format.
Also, the password may be a single word or a phrase to access the OOB. The one or more Out-Of-Band (OOB) login credentials aims to differentiate between an authorized access and an unauthorized access. In an exemplary aspect of the present disclosure, the one or more target nodes may be network nodes such as desktop computer, a laptop, a server, and a virtual
20 machine.
[00073] At step [306], the method [300] comprises receiving, by the transceiver unit
[202], at the central controller [200a], one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes.
25 The one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective
one or more OOB IP addresses for the one or more target nodes, are received by the user input at the user interface of the central controller [200a]. The transceiver unit [202] is further configured to receive, one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes. For example,
30 an IT administrator is preparing to configure several servers, each server requires both an SSH
IP address for secure communication and an OOB IP address for management access. The SSH IP address is used for secure command-line interface (CLI) access, while the OOB IP address allows for remote management and monitoring of the server hardware.
19

[00074] When the administrator initiates the configuration process, they input both the
SSH IP addresses and the corresponding OOB IP addresses for each target node into the central
controller [200a]. The transceiver unit [202] captures this information. Each target node can be
accessed both via its secure CLI and its management interface. For example, a list may be
5 provided where each entry contains an SSH IP address and its corresponding OOB IP address.
The one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes, are received by the user input at the user interface of the central controller [200a].
10 [00075] At step [308], the method [300] comprises executing, by a processing unit [204],
at the central controller, a configure IP script to initiate temporary attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on one or more host servers. For example, once the transceiver unit [202] receives the SSH IP address and OOB IP address details for each target node, the processing
15 unit [204] utilizes this information to start the configuration process. The configure IP script is
designed to log into each target node using the OOB IP address and the provided login credentials. Once logged in, the script temporarily assigns the corresponding SSH IP address to the target node. For example, if the first target node has an OOB IP address of 10.0.0.1 and an SSH IP address of 192.168.1.10, the processing unit [204] executes the configure IP script
20 to log into the node at 10.0.0.1, then assigns 192.168.1.10 as the temporary SSH IP address.
This process is repeated for each target node in the system, such as logging into 10.0.0.2 to assign 192.168.1.11 and logging into 10.0.0.3 to assign 192.168.1.12.
[00076] The processing unit [204] initiates IP attachment operation by running the
25 script, based on the OOB login credentials and the respective SSH IP address. In an exemplary
aspect, the temporary attachment of the one or more SSH IP addresses with the respective one
or more OOB IP addresses for each of the one or more target nodes, on the one or more host
servers is temporary and does not persist on rebooting of the one or more target nodes (such as
servers). Further, for rebooting the one or more target nodes (such as servers), the processing
30 unit [204] sends a reboot command to the one or more target nodes (such as servers). In an
exemplary aspect, the one or more host servers may be a physical server or cloud-based server.
[00077] At step [310], the method [300] terminates.
20

[00078] Referring to FIG. 4, an exemplary block diagram of a system architecture [400]
for attaching one or more temporary internet protocol addresses to one or more target nodes is
shown. The system architecture comprises automated cloud installer (ACI) user interface (UI)
[402], ACI [404], and target Nodes [406].
5
[00079] The ACI UI [402] is responsible for receiving user inputs, such as Out-Of-Band
(OOB) login credentials and Secure Socket Shell (SSH) IP addresses with their respective OOB
IP addresses. The input is then transmitted to the central controller [200a] within the ACI [404].
In an embodiment, the central controller [200a] is communicatively coupled to the ACI [404].
10 In another embodiment, the central controller [200a] is embedded or incorporated in the ACI
[404].
[00080] Within the ACI [404], the central controller [200a] comprises a transceiver unit
[202] and a processing unit [204]. The transceiver unit [202] receives the user inputs and then
15 the processing unit [204] executes a configure IP script. The script initiates the temporary
attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes [406].
[00081] For example, a user needs to attach temporary IP addresses to multiple freshly
20 installed OS on different servers. The user provides the necessary OOB login credentials and
the desired SSH IP addresses through the ACI UI [402]. This information is then processed by
the central controller [200a] within the ACI [404]. The processing unit [204] logs into the target
nodes [406] (such as the server) and executes the necessary ansible scripts to configure the
temporary IP addresses. The logs of these operations are parsed to determine if the IP address
25 attachment was successful, and the results are displayed to the user.
[00082] The temporary attachment does not persist over reboot, meaning the SSH IP
addresses are used only for initial access to make further configurations on the target nodes
[406]. The system enables parallel attachment of temporary IP addresses to multiple servers,
30 thus speeding up the deployment process and aiding in scaling the network efficiently.
[00083] Referring to FIG. 5, an exemplary block diagram of a User Equipment (UE)
[500] for attaching one or more temporary internet protocol addresses to one or more target
nodes is shown. The UE [500] includes a processor configured to receive one or more Out-Of-
35 Band (OOB) login credentials for the one or more target nodes; receive one or more Secure
21

Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP
addresses for the one or more target nodes; and execute a configure IP script to initiate
temporary attachment of the one or more SSH IP addresses with the respective one or more
OOB IP addresses for each of the one or more target nodes, on one or more host servers.
5
[00084] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for attaching one or more temporary internet protocol
addresses to one or more target nodes the instructions include executable code which, when
executed by one or more units of a system [200], causes: causes a transceiver unit [202], at a
10 central controller [200a], configured to receive, one or more Out-Of-Band (OOB) login
credentials for the one or more target nodes; receive, one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes; a processing unit [204], at the central controller [200a] configured to execute, at the central controller [200a], a configure IP script to initiate temporary attachment
15 of the one or more SSH IP addresses with the respective one or more OOB IP addresses for
each of the one or more target nodes, on one or more host servers.
[00085] As is evident from the above, the present disclosure provides a technically
advanced solution for attaching one or more temporary internet protocol addresses to one or
20 more target nodes. The present solution encompasses many advantages over the prior art such
as the present solution automatically attach SSH (secure shell) management IP address to OS and is capable of attaching SSH IP address to multiple servers in parallel manner which speeds up deployment process and hence in turn helps in scaling the network.
25 [00086] Further, in accordance with the present disclosure, it is to be acknowledged that
the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the
30 disclosure should not be construed as limiting the scope of the present disclosure.
Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
22

[00087] It should be noted that the terms "first", "second", "primary", "secondary",
"target" and the like, herein do not denote any order, ranking, quantity, or importance, but rather are used to distinguish one element from another.
[00088] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We claim:
1. A method for attaching one or more temporary Internet Protocol (IP) addresses to one
or more target nodes, the method comprising:
- receiving, by a transceiver unit [202], at a central controller [200a], one or more Out-Of-Band (OOB) login credentials for the one or more target nodes;
- receiving, by the transceiver unit [202], at the central controller [200a], one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes; and
- executing, by a processing unit [204], at the central controller [200a], a configure IP script to initiate temporary attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on one or more host servers.
2. The method as claimed in claim 1, wherein, the temporary attachment of the one or
more SSH IP addresses with the respective one or more OOB IP addresses for each of
the one or more target nodes, on the one or more host servers, comprises:
- initiating, by the processing unit [204], at the central controller [200a], an OS install script for installation of one or more OS in the one or more target nodes, from the one or more host servers;
- logging, by the processing unit [204], at the central controller [200a], to the one or more target nodes;
- executing, by the processing unit [204], at the central controller [200a], one or more ansible scripts; and
- parsing, by the processing unit [204], at the central controller [200a], one or more ansible script logs to detect one of a successful attachment status and an unsuccessful attachment status of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers.
3. The method as claimed in claim 2, wherein, installation of one or more OS in the one
or more target nodes, comprises:

- configuring, by a configuration unit [206], at the central controller [200a], one or more image Uniform Resource Locators (URLs) associated with the one or more OS to be installed in the one or more target nodes, for one or more host servers.
4. The method as claimed in claim 2, wherein the successful attachment status and the unsuccessful attachment status of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers, is displayed at a user interface of the central controller [200a].
5. The method as claimed in claim 1, wherein the one or more OOB login credentials for the one or more target nodes are received, by a user input, at a user interface of the central controller [200a].
6. The method as claimed in claim 1, wherein, the one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes, are received by a user input at a user interface of the central controller [200a].
7. The method as claimed in claim 1, wherein the temporary attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers, does not persist on rebooting of the one or more host servers.
8. A system for attaching one or more temporary internet protocol addresses to one or more target nodes, the system comprising:
- a transceiver unit [202], at a central controller [200a], configured to:
o receive one or more Out-Of-Band (OOB) login credentials for the one or more
target nodes; and o receive one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes; and
- a processing unit [204] configured to execute, at the central controller [200a], a
configure IP script to initiate temporary attachment of the one or more SSH IP

addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on one or more host servers.
9. The system as claimed in claim 8, wherein, for the temporary attachment of the one or
more SSH IP addresses with the respective one or more OOB IP addresses for each of
the one or more target nodes, on the one or more host servers, by the processing unit
[204], at the central controller [200a], the processing unit [204] is further configured
to:
- initiate an OS install script for installation of one or more OS in the one or more target nodes;
- log-in to the one or more target nodes;
- execute, one or more ansible scripts; and
- parse one or more ansible script logs to detect one of a successful attachment status and an unsuccessful attachment status of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers.

10. The system as claimed in claim 9, wherein the system comprises: a configuration unit [206], at the central controller [200a], the configuration unit is configured to configure one or more image Uniform Resource Locators (URLs) associated with the one or more OS to be installed in the one or more target nodes, for one or more host servers.
11. The system as claimed in claim 9, wherein the successful attachment status and the unsuccessful attachment status of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on the one or more host servers, is displayed at a user interface of the central controller [200a].
12. The system as claimed in claim 8, wherein the one or more OOB login credentials for the one or more target nodes are received, by a user input, at a user interface of the central controller [200a].
13. The system as claimed in claim 8, wherein, the one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the

one or more target nodes, are received by a user input at a user interface of the central controller [200a].
14. The system as claimed in claim 8, wherein the temporary attachment of the one or more
SSH IP addresses with the respective one or more OOB IP addresses for each of the one
or more target nodes, on the one or more host servers, does not persist on rebooting of
the one or more host servers.
15. A User Equipment (UE) [500] comprising:
- a processor [502] configured to:
o receive one or more Out-Of-Band (OOB) login credentials for one or more
target nodes; o receive one or more Secure Socket Shell (SSH) Internet Protocol (IP) addresses and a respective one or more OOB IP addresses for the one or more target nodes; and o execute a configure IP script to initiate temporary attachment of the one or more SSH IP addresses with the respective one or more OOB IP addresses for each of the one or more target nodes, on one or more host servers.