Using Shell Commands

Transcription

1 This chapter contains the following sections: General Administration, page 1 Working with Databases, page 9 Importing Certificates, page 13 Accessing Root Privileges, page 14 Using a Multi-Node Setup, page 16 General Administration This section describes how to execute common administration tasks such as changing your password, stopping and starting services, as well as other common system administration tasks. Examining the Version Information You can verify the Cisco UCS Director version and build number by choosing Show Version. This information is required for debugging purposes. From the Cisco UCS Director Shell menu choose Show Versionand press Enter. Cisco UCS-D Version : Build Number : 22 Press Enter to complete the process. OL

2 Stopping Cisco Services Stopping Cisco Services You can stop all Cisco services that are part of the Cisco UCS Director appliance by choosing Stop Services. You can verify that all services are stopped by choosing Display Service Status. From the Cisco UCS Director Shell menu choose Stop Services. Press Enter. The following information displays: Stopping broker [PID=17364]/[Child=17365] Stopping controller [PID=17402]/[Child=17404] Stopping eventmgr [PID=17471]/[Child=17473] Stopping client [PID=17535]/[Child= ] Stopping idaccessmgr [PID=17613]/[Child=] /opt/infra/stopinfraall.sh: line 35: kill: (17613) - No such process Stopping inframgr [PID=17676]/[Child=] Tomcat is running with [PID=17779]. Stoping it and its child process Flashpolicyd is running with [PID=17807]. Stopping it Stopping websock[pid=17812] Press Enter to complete the procedure. Starting Cisco Services You can execute all services that are part of Cisco UCS Director by choosing Start Services. After using this option, you can choose Display Service Status to verify that all services are executed. Services started in the background are not displayed. From the Cisco UCS Director Shell menu choose Start Services. nohup: appending output to `nohup.out' Press Enter to complete the process. Choose Display Service Status to verify that the services are executed. 2 OL

3 Displaying the Status of Your Services Displaying the Status of Your Services The Display Services option displays all executed services. You can execute seven services at any one time. Broker Controller Eventmgr Client Idaccessmgr Inframgr Tomcat Websock (VNC interface) Database (mysqld) Ensure that all of the above services are up and operating. If a service is not executed on Cisco UCS Director, restart the service through the shell client. From the Cisco UCS Director Shell menu choose option Display Service Status. The following list of services appears: Cisco UCS Director Shell Menu Select a number from the menu below 1) Change ShellAdmin password 2) Display Services Status 3) Stop Services 4) Start Services 5) Stop Database 6) Start Database 7) Backup Database 8) Restore Database 9) Time Sync 10) Ping Hostname/IP Address 11) Show version 12) Import CA Cert (JKS) File 13) Import CA Cert(PEM) File for VNC 14) Configure Network Interface 15) Display Network Details 16) Enable Database for Cisco UCS Director Baremetal Agent 17) Add Cisco UCS Director Baremetal Agent Hostname/IP 18) Tail Inframgr logs 19) Apply Patch 20) Shutdown Appliance OL

4 Changing Your Password 21) Reboot Appliance 22) Manage Root Access 23) Login As Root 24) Quit SELECT> 2 Service Status PID broker RUNNING controller RUNNING eventmgr RUNNING client RUNNING idaccessmgr RUNNING inframgr RUNNING TOMCAT RUNNING websock RUNNING ? 00:00:00 mysqld_safe 3192? 7-10:59:53 mysqld The corresponding status and process ID (PID) of each service is also displayed in the menu. Changing Your Password You can change your Cisco UCS Director shell password by choosing Change ShellAdmin password. From the Cisco UCS Director Shell menu choose Change ShellAdmin passwordand press Enter. The following information is displayed: Changing password for user shelladmin. New UNIX password: Enter your new UNIX password and press the Enter key. Enter your new UNIX password once again and press the Enter key. passwd: all authentication tokens updated successfully. Press return to continue... 4 OL

5 Synchronizing the System Time Synchronizing the System Time You can synchronize the system time to the hardware time as well as the NTP server by choosingtime Sync. From the Cisco UCS Director Shell menu choose Time Sync. Press Enter. Time Sync... System time is Tue Sep 17 15:57:34 UTC 2013 Hardware time is Tue Sep 17 15:57: seconds Do you want to sync systemtime [y/n]? y NTP Server IP Address: Dec 03:24:02 ntpdate[5017]: step time server offset sec Sync'ed with NTP SERVER Step 5 Press Y and press Enter to synchronize to system time. Press Y and press the Enter to synchronize to the NTP server. Press Enter key to complete the process. Pinging the Hostname and IP Address You can ping a hostname or IP address to test your connectivity by choosing Ping Hostname/IP address. From the Cisco UCS Director Shell menu choose option Ping Hostname/IP addres and press Enter. Enter your IP address and press Enter. Enter IP Address : PING ( ) 56(84) bytes of data. 64 bytes from : icmp_seq=1 ttl=64 time=9.90 ms 64 bytes from : icmp_seq=2 ttl=64 time=0.316 ms 64 bytes from : icmp_seq=3 ttl=64 time=0.254 ms 64 bytes from : icmp_seq=4 ttl=64 time=0.198 ms 64 bytes from : icmp_seq=5 ttl=64 time=0.267 ms ping statistics packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 0.198/2.187/9.901/3.857 ms OL

6 Configuring a Network Interface Press Enter to exit out of the operation. Configuring a Network Interface You can configure a network interface for the Cisco UCS Director appliance by choosing Configure a Network Interface. From the Cisco UCS Director Shell menu choose Configure a Network Interface and press Enter. The following information displays: Do you want to Configure DHCP/STATIC IP [D/S]? : S Choose one of the following configuration selections: Choose D to configure a DHCP IP address. Choose S to configure a static IP address. Enter s to configure a static IP address and press Enter. The following information is displayed. Configuring STATIC configuration.. Enter the ethernet interface that you want configure E.g. eth0 or eth1: Enter the Ethernet interface to configure (for example, eth1) and press Enter. The following information displays: Configuring STATIC IP for eth1... IP Address: Netmask: Gateway: DNS Server1: DNS Server2: Configuring Network with : INTERACE(eth1), IP( ), Netmask( ), Gateway( ), DNS Server1( ), DNS Serverx 2( ) Step 5 Do you want to continue [y/n]? : Enter n to discontinue the configuration process. Press Enter to return to complete the process. Displaying Appliance Network Details You can display the Cisco UCS Director appliance network details by choosing option 15, Display Appliance Network Details. From the Cisco UCS Director Shell menu choose option 15 and press Enter. 6 OL

7 Adding the BMA Hostname and IP Address Network details... eth0 Link encap:ethernet HWaddr 00:50:56:97:1E:2D inet addr: Bcast: Mask: inet6 addr: fe80::230:56gg:fe97:1e2d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets: errors:14832 dropped:17343 overruns:0 frame:0 TX packets: errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes: (98.4 GiB) TX bytes: (25.6 GiB) Interrupt:59 Base address:0x2000 lo Link encap:local Loopback inet addr: Mask: inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets: errors:0 dropped:0 overruns:0 frame:0 TX packets: errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes: (305.3 GiB) TX bytes: (305.3 GiB) Press Enter to complete the process. Adding the BMA Hostname and IP Address Choose this option to add Bare Metal Agent (BMA) appliance hostname and IP address entries into the Cisco UCS Director appliance's /etc/hosts file. From the Cisco UCS Director Shell menu choose option Add Cisco VCS Director Baremetal Agent and press Enter. The following information displays: Adding Cisco UCS Direcor Baremetal Agent Hostname and IP Address entry to /etc/hosts Enter Cisco UCS Director Baremetal Agent IP Address: Enter Cisco UCS Director Baremetal Agent Hostname: Adding host entry to /etc/hosts Entry does not exists Backed up old file... Added new entry Added To /etc/hosts Press Enter to return to complete the process. OL

8 Viewing Tail Inframgr Logs Viewing Tail Inframgr Logs You can view inframgr logfiles. You can choose the required logfile to view by choosing Tail Inframgr Logs. From the Cisco UCS Director Shell menu choose Tail Inframgr Logs and press Enter. Enter the logfile sequence 0, 1, 2 (Eg. 0-logfile.txt, 1-logfile.txt.1, 2-logfile.txt.2): Choose the file you need to view. Type Ctrl + C to exit the process. This step logs you out of the shelladmin. Log back in to conduct another procedure. Applying a Patch to Cisco UCS Director Choose this option to apply a patch to the appliance. It is recommended that you review the patch release notes before applying a patch. The patch file (zip file) is provided by Cisco UCS Director. It is also recommended that you take a snapshot of your VM before applying a patch. It is recommended that you stop the appliance services before applying a patch. Before You Begin Download the patch file Place the file in a web server or FTP server Choose Apply Patch from the Cisco UCS Director Shell menu Provide patch URL ( From the Cisco UCS Director Shell menu choose Apply Patch and press Enter. Applying Patch... Applying Patch: Patch URL :xxx.xxx.x.xxx/testpkg.zip 8 OL

9 Working with Databases Applying the Patch [y/n]? y Step 5 Enter your IP address and press Enter. Enter the patch URL. Press Enter. Enter y to apply the patch. Follow the onscreen prompts to complete the process. What to Do Next After the patch is applied, choose Stop Services and Start Services. Refer to the Cisco UCS Director BMA Installation Guide for additional information. Working with Databases Stopping the Database This section describes how to enable, start and stop, as well as backup and restore a database. You can halt the mysql daemon (mysqld) by choosing option 5, Stop Database. This option stops all of the following Cisco services: Broker Controller Eventmgr Client Idaccessmgr Inframgr Tomcat Websock From the Cisco UCS Director Shell menu choose option 5. Do you want to stop the database [y/n]? Stopping database... Database stopped... y OL

10 Starting the Database Stopping broker [PID=21921]/[Child=21923] Stopping controller [PID=21959]/[Child=21961] Stopping eventmgr [PID=21993]/[Child=21995] Stopping client [PID=22052]/[Child= ] Stopping idaccessmgr [PID=22099]/[Child=] Stopping inframgr [PID=22158]/[Child=] Tomcat is running with [PID=22213]. Stoping it and its child process Flashpolicyd is running with [PID=22237]. Stopping it Stopping websock[pid=22242] Follow the onscreen prompts to complete the process by choosing option 6, Start Database. Starting the Database You can start the mysql daemon (mysqld) by choosing Start Database. This option starts the appliance database only. From the Cisco UCS Director Shell menu choosestart Database. Press Enter. Starting database... directory (/var/lib/mysql/data/confmgr_production) exists directory (/var/lib/mysql/data/db_private_admin) exists the file (/var/lib/mysql/data/ib_logfile1) exists the file (/var/lib/mysql/data/ib_logfile0) exists the file (/var/lib/mysql/data/ibdata1) exists Database started :10:54 mysqld_safe Logging to '/var/log/mysqld.log' :10:54 mysqld_safe Starting mysqld daemon with databaes from /var/lib/mysql/data The Cisco services are not started automatically when you start the appliance database. Choose Start Services to start the Cisco services. Backing Up the Database You can backup the appliance database to a FTP server. You should stop the Cisco services before you begin the backup process. To stop the services choose Stop Services. You need the following information in order to execute the task: 10 OL

11 Restoring the Database FTP server's IP address (where the database is to be backed up) FTP server's login credentials After the FTP credentials are provided, the entire database of the Cisco UCS Director appliance is backed up at the specified FTP location. You can then start the Cisco services by choosing Start Services. From the Cisco UCS Director Shell menu choose Backup Database. Press Enter. Backing database... Backup will Upload file to an FTP server. Provide the necessary access credentials FTP Server IP Address: Step 5 Enter your FTP Server IP address and press Enter. Enter your FTP Server login and press Enter. Enter your FTP Server password and press Enter. Restoring the Database Before restoring the database, stop the Cisco services. To stop the services, choose Stop Services. Provide the following information in order to execute the task: FTP server's IP address (where the database is to be restored from) FTP server's login credentials Restore filename Confirm to restore After FTP credentials are provided, the entire database of the Cisco UCS Director appliance is restored from the specified FTP location. You can then start the Cisco services by choosing Start Services. From the Cisco UCS Director Shell Menu choose option Restore Services. Press Enter. The following information displays: Restore database... Restore will recover file from an FTP server. Provide the necessary access credentials OL

12 Enabling the Database for BMA FTP Server IP Address: FTP Server Login: root FTP Server Password: Step 5 Step 6 Step 7 Enter your FTP server IP address and press Enter. Enter your FTP server login and press Enter. Enter your FTP server password and press the Enter. Follow the onscreen prompts to complete the process. Choose option Start Services to restart the Cisco services. Enabling the Database for BMA You can enable remote database access for the BMA appliance by choosing Enabling the Database for BMA. This option is required for configuration of the Cisco UCS Director appliance with the BMA appliance. From the Cisco UCS Director Shell menu chooseenabling the Database for Cisco UCS Directory Baremetal Agent and press Enter. Do you want to enable 'remote database' access for Cisco UCS Director Baremetal Agent [y/n]? y Cisco UCS Director Baremetal Agent Hostname/IP Address: Choose y and press Enter. Cisco UCS Director Baremetal Agent Hostname/IP Address: Enabling 'remote database' access for Enabling remote database access to About to enable remote access to database - please be catious that this is only supported for Cisco UCS Director Baremetal Agent About to enable remote access to database ( ) please be catious that this is only supported for Cisco UCS Director Baremetal Agent INFO (DBEnableRemoteAccess.java:195) About to enable remote access to database ( ) please be catious that this is only supported for Cisco UCS Director Baremetal Agent Remote DB access enabled INFO (DBEnableRemoteAccess.java:213) About to enable remote access to datbase - please be catious that this is only supported for Cisco UCS Director Baremetal Agent flushprivileges - About to enable remote access to database - please be catious that this is only supported for Cisco UCS Director Baremetal Agent INFO (DBEnableRemoteAccess.java:119) flushprivileges - About to enable remote access to database - please be catious that 12 OL

13 Importing Certificates this is only supported for Cisco UCS Director Baremetal Agent Enabled 'Remote' database access INFO (DBEnableRemoteAccess.java:219) Enabled 'Remote' database access Sucessfully added credential for ipaddress flushprivileges - About to enable remote access to database - please be catious that this is only supported for Cisco UCS Director Baremetal Agent INFO (DBEnableRemoteAccess.java:119) flushprivileges - About to enable remote access to database - please be catious that this is only supported for Cisco UCS Director Baremetal Agent Enabled 'Remote' database access for: INFO (DBEnableRemoteAccess.java:679) Enabled 'Remote' database access for: Completed remote database access... Press Enter to return to the main menu. Importing Certificates This section describes how to import certification authority (CA) certificates. Both the Java KeyStore (JKS) and Privacy-enhanced Electronic Mail (PEM) certificates are utilized. A JKS certificate is a repository of security certificates used in SSL encryption. A PEM file is a container format that may include just the public certificate or may include an entire certificate chain that includes a public key, private key, and root certificates. Importing a CA Certificate (JKS) File You can import a CA signed certificate file by choosing option 12, Importing a CA Certificate (JKS) file. From the Cisco UCS Director Shell Menu choose option 12 and press Enter. Import CA signed certificate from URL. E.g. URL --> URL: Enter your URL that points to the CA signed certificate file and press Enter. Importing a CA Certificate (PEM) File for VNC You can import a CA signed certificate (PEM) file by choosing Import CA Certificate (PEM) File for VNC. From the Cisco UCS Director Shell menu choose Import CA Certificate (PEM) File for VNC and press Enter. OL

14 Accessing Root Privileges Import CA signed certificate (in PEM format) from URL. E.g. URL --> URL: Enter your URL that points to the CA signed certificate (PEM) file and press Enter. Accessing Root Privileges This section describes how to access root. Tasks that require root privileges include moving directories or files into other directories, providing or revoking user privileges, general system repairs, and occasionally installing applications. Compiling software as root is not recommended for security reasons. Enabling Root Access You can enable root privileges by choosing Manage Root Access. From the Cisco UCS Director Shell Menu choosemanage Root Access and press Enter. The following information displays: Enable/Disable/Configure (root privalege) [e/d/c]: Enter e and press Enter. Do you want to Enable Root Access [y/n]? : Enter y and press Enter. Enabling root access... Unlocking password for user root. passwd: Success. Root access enabled successfully Press return to continue Press Enter to return to compete the process. 14 OL

15 Disabling Root Access Disabling Root Access Choose this option to disable root privileges. From the Cisco UCS Director Shell menu choose Manage Root Access and press the Enter key. The following information displays: Enable/Disable/Configure (root privalege) [e/d/c]: Enter d and press the Enter key. The following information displays: Do you want to Disable Root Access [y/n]? : Enter y and press the Enter key. disabling root access... Locking password for user root. Passwd: Success Root access disabled sucessfully Press return to continue... Press the Enter key to return to the main menu. Configuring Root Access You can enable root privileges by choosing Manage Root Access. Step 5 From the Cisco UCS Director Shell choose Manage Root Access and press Enter. Enable/Disable/Configure (root privalege) [e/d/c]: Enter c and press Enter. Do you want to Configure/Set Root Privilege/Password [y/n]? : Enter y and press Enter. Changing root password... Changing password for user root. New UNIX password: Enter a new UNIX password and press Enter. Retype new UNIX password: Enter your new UNIX password and press Enter. The following information displays: passswd: all authentication tokens updated successfully. Root passwd changed successfully Press return to continue... OL

16 Logging in as Root Step 6 Press Enter to complete the process. Logging in as Root You can login in as root by choosing Login As Root. Step 5 From the Cisco UCS Director Shell Menu chooselogin As Root and press Enter. Do you want to Login As Root [y/n]? : Enter y and press Enter. Logging in as root password: Enter your root password and press Enter. Logging as root Password: [root@localhost shelladmin]# Enter your password and press Enter. Enter exit to return to the shelladmin. [root@localhost shelladmin]# cd /opt [root@localhost opt]# exit exit Sucessful login Using a Multi-Node Setup The multi-node setup is supported for Cisco UCS Director on VMware vsphere only. With a multi-node setup, you can scale Cisco UCS Director to support a larger number of VMs than is supported by a single installation of Cisco UCS Director. This setup has the following nodes: One primary node One or more service nodes One monitoring database One inventory database 16 OL

17 Database Nodes For a multi-node setup, you have to install the license on the primary node only. A multi-node setup improves scalability by offloading the processing of system tasks, such as inventory data collection, form the primary node to one or more service nodes. You can assign certain systems tasks to one or more service nodes. The number of nodes determines how the processing of system tasks are scaled. Node pools group service nodes and enable you to assign system tasks to more than one service node. If one service node is busy when a system task needs to be run, Cisco UCS Director uses a round-robin assignment to determine which service node should process the system task. If all, service nodes are busy, you can have the primary node run the system task. For more information about how to configure the primary node and service nodes, and how to assign system tasks, see the Cisco UCS Director Administration Guide Database Nodes The inventory and monitoring databases are created from the Cisco UCS Director MySQL database. The data that Cisco UCS Director collects is divided between the two databases. The multi-node setup segregates the data collection which is historically very heavy on the database into a separate database. Inventory Database A multi-node setup can have only one inventory database. This database contains the following: Physical and virtual accounts and their related inventory data Data used in the normal operation of Cisco UCS Director for all supported features Monitoring Database A multi-node setup can have only one monitoring database. This database contains the data that Cisco UCS Director uses for historical computations, such as aggregations and trend reports. The parameters of the monitoring database depend upon the number of devices and VMs you plan to configure and manage through Cisco UCS Director Summary of Steps for Configuring a Multi-Node Setup This procedure provides a high-level summary of the steps involved in configuring a multi-node setup. Plan your multi-node setup carefully. You can only change a service node to a primary node. You cannot change any other type of node after you configure it. For example, you cannot reconfigure a primary node as a service node or an inventory database node as a monitoring database node. Deploy a Cisco UCS Director VM for each node in the multi-node setup. For more information, see the relevant installation and upgrade guide. OL

18 Creating the Inventory Database For example, if your multi-node setup, includes a primary node, an inventory database, a monitoring database, and three service nodes, deploy six Cisco UCS Director VMs. In the Cisco UCS Director shelladmin, configure the nodes in the following order: 1 Creating the Inventory Database, on page 18 2 Creating the Monitoring Database, on page 19 3 Creating the Primary Node, on page 19 4 Creating a Service Node, on page 20 You must create and start the inventory database and the monitoring database nodes before you configure the primary node and any service nodes. Update the license file in the Cisco UCS Director node that will be the primary node. You do not need to update the license file on any other node. See the "Updating the License" topic in the relevant installation and upgrade guide. In Cisco UCS Director on the primary node, configure the system tasks as follows: a) Create one or more node pools if you want to control the assignment of system tasks by service node, or accept the default node pool. b) Create one or more system task policies if you want to control the assignment of system tasks by service node, or accept the default task policy. c) Configure the service nodes. d) Configure the primary node. e) Assign the system tasks to system policies if you want to control the assignment of system tasks by service node. See the Cisco UCS Director Administration Guide. Creating the Inventory Database Step 5 Log into the Cisco UCS Director shelladmin on the inventory database node. From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter. From the menu, choose Configure Inventory Database and press Enter. When prompted, press Enter to continue. To verify that the services for the inventory database are up and running, choose Display Services Status and press Enter. You should see the following lines: 2838? 00:00:00 mysqld_safe 3172? 3-02:51:38 mysqld After you return to the shelladmin, the menu options change to those available for an inventory database node. 18 OL

19 Creating the Monitoring Database Creating the Monitoring Database Step 5 Log into the Cisco UCS Director shelladmin on the monitoring database node. From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter. From the menu, choose Configure Monitoring Database and press Enter. When prompted, press Enter to continue. To verify that the services for the monitoring database are up and running, choose Display Services Status and press Enter. You should see the following lines: 2838? 00:00:00 mysqld_safe 3172? 3-02:51:38 mysqld After you return to the shelladmin, the menu options change to those available for a monitoring database node. Creating the Primary Node Before You Begin The inventory and monitoring databases must be up and running before you create the primary node. Do not run any daemons on the primary database. Step 5 Log into the Cisco UCS Director shelladmin on the primary node. From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter. From the menu, choose Configure Primary Node and press Enter. At the Provide Inventory DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for the inventory database. This step registers the VM as a primary node with the inventory database. At the Provide Monitoring DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for the monitoring database. This step registers the VM as a primary node with the monitoring database. OL

20 Creating a Service Node Step 6 Step 7 When prompted, press Enter to continue. To verify that the services for the primary node are up and running, choose Display Services Status and press Enter. You should see the following lines: Service Status PID broker RUNNING controller RUNNING eventmgr RUNNING client RUNNING idaccessmgr RUNNING inframgr RUNNING TOMCAT RUNNING websock RUNNING Node Type : primary Inventory DB( :3306 ) status Monitor DB( :3306 ) status : UP : UP After you return to the shelladmin, the menu options change to those available for a primary node. Creating a Service Node Before You Begin The inventory and monitoring databases must be up and running before you create the primary node. Step 5 Step 6 Step 7 Log into the Cisco UCS Director shelladmin on the service node. From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter. From the menu, choose Configure Service Node and press Enter. At the Provide Inventory DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for the inventory database. This step registers the VM as a service node with the inventory database. At the Provide Monitoring DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for the monitoring database. This step registers the VM as a service node with the monitoring database. When prompted, press Enter to continue. To verify that the services for the service node are up and running, choose Display Services Status and press Enter. 20 OL

21 Creating a Service Node You should see the following lines: Service Status PID broker RUNNING controller RUNNING eventmgr RUNNING client RUNNING idaccessmgr RUNNING inframgr RUNNING TOMCAT RUNNING websock RUNNING Node Type : service Inventory DB( :3306 ) status Monitor DB( :3306 ) status : UP : UP After you return to the shelladmin, the menu options change to those available for a service node. Step 8 Repeat this procedure for every service node. OL

22 Creating a Service Node 22 OL