9.1.3.1 Configuring the second Host only Network Card
The second Host only network card is requires configuration to complete the access for the other VMWare servers using a static IP address which is in the same domain, for them to authenticate correctly.
Note: The Boot tab must be selected again with the select menu right-arrow key as shown in Figure 9.28 through to Figure 9.30 but reversing the Boot order to ensure the VMware server is now booted from the installed Hard Drive rather than the CD-ROM installation media.
Enter management then Enter Interfaces as shown in Figure 9.61:
Figure 9.61: Enter management | interfaces to start the configuration of the static IP network card
Enter list as shown in Figure 9.62:
Figure 9.62: Enter the list command to list the Network cards
Enter set as shown in Figure 9.63:
Figure 9.63: Enter the set command to configure a Network Card
Enter 2 from the list to configure the second Network Card, M.2, as shown in Figure 9.64
Figure 9.64: Enter 1 to configure the second Network Card
Enter 2 since we want to leave the first network card as the default in the prompt for: Make this interface the default interface?
We can now enter 2 (Manual IP configuration) after the next response to set the static IP address of the second Network Card interface (M2.) as shown in Figure 9.65:
Figure 9.65: Enter 1 to configure the second Network Card
Configure M.2 using the above responses. Then we reboot the system as shown in Figure 9.49 and the login in Figure 9.50 earlier. Log into the URL from a Chrome Browser as shown in Figure 9.55 earlier:
https://ecmukdemo77/login
Start up the Directory Server as shown earlier in Figure 9.58. Enter the URL:
https://192.168.50.131:12101/IDSWebApp/IDSjsp/IDSConsoleFrameWork.jsp
First time we need to use Login to Console admin. Enter superadmin password secret. Changed to admin/filenet as shown in Figure 9.66:
Figure 9.66: Select Configure and Change Admin DN Credentials
Edit a server using the console, using the following instructions. Using: https://192.168.50.131:12101/IDSWebApp/IDSjsp/Login.jsp?showConsoleAdminLogin=true
Log into the Directory Server Console using admin/filenet as shown in Figure 9.67
Figure 9.67: Select Login and return
Do either of the following. Expand Console administration in the navigation area, and then, click Manage console servers on the right side of the window as shown in Figure 9.68:
Figure 9.68: The Manage Console Servers link is clicked
A table of server host names and port numbers is displayed. Click Edit after selecting the Port 389 entry shown in Figure 9.69:
Figure 9.69: The Select Option is chosen for the port 389 entry and the Edit command button is clicked
The Add command to add a new Server for the second Network Card, M2 (10.10.10.177) as shown in Figure 9.70 is displayed:
Figure 9.70: We can use the Add command to add a new Server for the second Network Card, M2 (10.10.10.177)
Enter a unique name in the Server name field to identify a registered IBM Security Directory Server (TDS) server instance running on a specific host name or IP address and server port. (ECMUKDEMO7), as shown in Figure 9.71:
Figure 9.71: We add a new Server for the second Network Card, M2 (10.10.10.177)
Note: This changes the link as the latest IP (but is only accessible from one VMware server to another). The directory server is added as shown in the message shown in Figure 9.72:
Figure 9.72: The Directory server name, ECMUKDEMO7 is added with the ip address 10.10.10.177 on port 389
This is done using Configure Directory Suite as shown in Figure 9.73:
Figure 9.73: The Admin DN is changed as highlightedWe can now change the Admin DN Credentials from a VMware Linux server as shown earlier, in Figure 9.66. We need to restart the Directory Server for the Admin DN change to take effect as shown in Figure 9.74:
Figure 9.74: The Admin DN change is updated after the Directory Server is restarted
First, we add the Directory server to the /etc/hosts file of a VMware Linux server cluster member as shown in Figure 9.75:
Figure 9.75: The ECMUKDEMO7 LDAP server we created is entered in /etc/hosts
The updated /etc/hosts entry can now be pinged as shown in Figure 9.76.
Figure 9.76: The ECMUKDEMO7 LDAP server entry can now be pinged
We need to open the firewall For the IBM Security Directory Suite port 389 incoming connections:
firewall-cmd –zone=public –permanent –add-port=389/tcp
firewall-cmd –reload
We can now log into the VMware server to access the Directory Server using cn=admin, password filenet:
https://192.168.50.131:12101/IDSWebApp/IDSjsp/IDSConsoleFrameWork.jsp
Now we can get access to the Directory server as shown in Figure 9.77:
Figure 9.77: The Directory management menu item is selected
The IBM Security Directory Server Web Administration Tool console is displayed with various server management tasks. The server management tasks vary depending upon the capabilities of the server and the type of user that you have logged on as.
