 network element configurations. Steps for implementing an automated eNodeB bring up will involve: An automated self-test and self-discovery. This will involve eNodeB identifying the backhaul and management links that are connected to it. Also, the base band unit and the remote radio head unit will need to be able to detect and identify each other in this step so they can communicate within it. IP assignment. IP planning is done as part of preplanning, and the IP assignment can be done using a local console or dynamic host configuration protocol (DHCP). Here, the IP address assignment is not only for the new node, but also for the other connections that are configured, such as IP addresses for the Mobility Management Entitiy (MME), Serving gateway (SGW), other neighboring eNodeBs, and so forth. Automatic software management. Once the secure tunnels are established with the EMS, the eNodeB will attempt to download the software from the central repository. Automatic software management involves centrally maintaining (at the element management system level) the software versions that are used in individual network elements (eNodeB in this case), keeping track of the latest available software, and scheduling the upgrade for individual eNodeBs. Typically, an eNodeB will have a base band unit (BBU) and remote radio head (RRH) as its two main components, and there would be separate software versions maintained for these two units. Management is required for each software component separately. Automatic software management will also require the element management system to support preplanning software loads for newly commissioned eNodeBs and provision a default image for these eNodeBs. Another important aspect of automatic software management is support for a "backup" and "rollback." In cases of unsuccessful upgrade events, there should be a possibility for a rollback to the previous version of the software. Automatic configuration. Automatic configuration refers to the process by which the eNodeB configuration parameter