Oracle® Communications Platform 6.
Oracle® Communications Platform 6.0 Configuration Procedure Reference Copyright © 2010 , 2014, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.
Table of Contents Chapter 1: 1 Introduction..............................................................................9 1.1 References........................................................................................................................................10 1.2 Acronyms........................................................................................................................................10 1.3 Terminology.....................................................................
3.2.11 Configure QoS (DSCP and/or CoS) on HP 6120XG Switches..............................111 3.3 Brocade Switch - SwitchConfig Procedures.............................................................................112 3.3.1 Configure Brocade Switches........................................................................................112 3.3.2 Upgrade Brocade Switch Firmware...........................................................................115 3.3.3 Configure Zones in Brocade Switches............
3.8.3 TVOE Network Configuration....................................................................................189 3.8.4 Deploy PM&C Guest....................................................................................................195 3.8.5 Setup PM&C..................................................................................................................197 3.8.6 Configure PM&C application......................................................................................201 3.8.
3.11.10 Create LV and Filesystem for Netbackup Client Software.................................295 3.11.11 Migrate Netbackup Client to New Filesystem......................................................295 3.11.12 Create Netbackup Client Config File.....................................................................296 3.12 TVOE Host Procedures.............................................................................................................297 3.12.
List of Figures Figure 1: Example Of An Instruction That Indicates The Server To Which It Applies.........................
List of Tables Table 1: Acronyms............................................................................................................................................10 Table 2: Terminology.......................................................................................................................................
Chapter 1 1 Introduction Topics: • • • • 1.1 References.....10 1.2 Acronyms.....10 1.3 Terminology.....11 1.4 Customer Care Center.....12 This document describes the procedures to configure the hardware and platform components of an HP c-Class system. An HP c-class system consists of enclosures and server blades. In addition, it may include components such as switches, SAN controllers, and management servers.
1 Introduction 1.1 References Internal References 1. Formal Peer Review Process, PD001866, v6.21, Nov 2008 2. 909-1638-001 Disaster Recovery for HP c-Class 3. HP Solutions Firmware Upgrade Pack, 795-0000-2xx, v2.2.x (latest recommended, 2.2.1 minimum) 4. TR006683: NOAMP on HP DL380 Network Interconnect 5. TR006851: Platform 5.0 Generic HP c-Class Networking Interconnect Refer to D.1 Accessing Tekelec’s Customer Support Site to access the Tekelec documentation. External References 6.
1 Introduction Acronym Definition RMS Rack Mount Server SAN Storage Area Network SFTP Secure File Transfer Protocol SNMP Simple Network Management Protocol TPD Tekelec Platform Distribution VSP Virtual Serial Port 1.3 Terminology Multiple server types may be involved with the procedures in this manual. Therefore, most steps in the written procedures begin with the name or type of server to which the step applies.
1 Introduction Server A generic term to refer to a server, regardless of underlying hardware, be it physical hardware or a virtual TVOE guest server. Non-Segregated Network PM&C network interconnect where all networks (control, management, and others as needed) utilize the same physical network (i.e. same bond, same switch infrastructure). Typically, this means the control VLAN is optionally tagged, and the management and other possible VLANs are required to be tagged.
1 Introduction 8:00 a.m. through 5:00 p.m. (GMT minus 5 hours), Monday through Friday, excluding holidays • Caribbean and Latin America (CALA) Phone: +1-919-460-2150 TAC Regional Support Office Hours (except Brazil): 10:00 a.m. through 7:00 p.m. (GMT minus 6 hours), Monday through Friday, excluding holidays • Argentina Phone: 0-800-555-5246 (toll-free) • Brazil Phone: 0-800-891-4341 (toll-free) TAC Regional Support Office Hours: 8:00 a.m. through 5:48 p.m.
1 Introduction 0800-176-6497 • Europe, Middle East, and Africa Regional Office Hours: 8:30 a.m. through 5:00 p.m. (GMT), Monday through Friday, excluding holidays • Signaling Phone: +44 1784 467 804 (within UK) • Software Solutions Phone: +33 3 89 33 54 00 • Asia • India Phone: +91-124-465-5098 or +1-919-460-2150 TAC Regional Support Office Hours: 10:00 a.m. through 7:00 p.m.
Chapter 2 2 Acquiring Firmware Topics: • 2.1 Acquiring Firmware.....
2 Acquiring Firmware 2.1 Acquiring Firmware Several procedures in this document pertain to the upgrading of firmware on various servers and hardware devices that are part of the Platform 6.0 configuration. The required firmware media and binaries are managed and distributed as part of the HP Solutions Firmware Upgrade Pack 2.2.x, released under Tekelec Part Number 795-0000-2yy The minimum firmware release required for Platform 6.0 is HP Solutions Firmware Upgrade Pack 2.2.
Chapter 3 3 Procedures Topics: • • • • • • • • • • • • 3.1 Aggregation Switch - NetConfig Procedures.....18 3.2 C-Class Enclosure Switch - NetConfig Procedures.....74 3.3 Brocade Switch - SwitchConfig Procedures.....112 3.4 SAN Storage Arrays Procedures.....126 3.5 Blade Server Procedures.....139 3.6 C7000 Enclosure Procedures.....148 3.7 DL360 and DL380 Server Procedures.....176 3.8 PM&C Procedures.....186 3.9 Configuring SAN.....248 3.10 Virtualization Procedures.....252 3.
3 Procedures 3.1 Aggregation Switch - NetConfig Procedures 3.1.1 Configure Cisco 4948/4948E/4948E-F aggregation switches (PM&C installed)(netConfig) This procedure will configure 4948/4948E/4948E-F switches with an appropriate IOS and configuration from a single management server and virtual PM&C for use with the c-Class or RMS platform. This procedures assumes a Platform 6.0 interconnect. If the system being configured follows a Platform 5.0 interconnect, then Platform 5.0 procedures should be followed.
3 Procedures Fill in the appropriate value for this site: Fill in the appropriate value for this site: Fill in the appropriate value for this site: Fill in the appropriate value for this site: Fill in the appropriate value for this site: Fill in the appropriate value for this site: Fill in the appropriate value for t
3 Procedures On Server1A login to iLO in IE using password provided by application: http:// Click in the Remote Console tab and launch the Integrated Remote Console on the server. Click Yes if the Security Alert pops up. If not already done so, login as root. 2. Management server: Procedure pre-check - verify hardware type Certain steps in this procedure require enabling and disabling ethernet interfaces. This procedure supports DL360 and DL380 servers.
3 Procedures 5. Management server: Setup conserver serial access for switch1A and switch1B and open the firewall to allow for future tftp use in this procedure.
3 Procedures If the output does not contain "Product Name: PMAC" or does not contain a PMAC version of 5.0 or higher, then stop this procedure and refer back to the application instructions 8. Virtual PM&C: Get IOS image and PROM information on the switches. Note: ROM & PROM are intended to have the same meaning for this procedure Connect to switch1A, check the IOS and PROM version. Connect serially to switch1A by issuing the following command.
3 Procedures 10. Virtual PM&C: Verify IOS & PROM images on the system. If the appropriate image does not exist, copy the image to the management server and upload the switch. Determine if the IOS & PROM images for the 4948/4948E/4948E-F is on the management server. # ls /var/TKLC/smac/image/ # ls /var/TKLC/smac/image/ If the file exists, skip the remainder of this step and continue with the next step.
3 Procedures If the output is "0" then, execute the commands that enable tftp transfer. # tpdProvd --client --noxml --ns=Xinetd startXinetdService service tftp Login on Remote: platcfg Password of platcfg: 12. Virtual PM&C -> Management Server: Manipulate host server physical interfaces. Note: On a TVOE host, If you launch the virsh console, i.e.
3 Procedures [Enter `^Ec?' for help] Press Enter If the switch is not already in enable mode ("switch#" prompt) then issue the "enable" command, otherwise continue with the next step.
3 Procedures If the model is C4948E or 4948E-F, execute these commands: Switch(config-if)# switchport mode trunk Switch(config-if)# spanning-tree portfast trunk Switch(config-if)# end Switch# write memory Now issue ping command: Note: The ip address should be in the reference table at the beginning of this procedure. Switch# ping Type escape sequence to abort.
3 Procedures The switch will reboot when the firmware upgrade completes. Allow it to boot up. Wait for the following line to be printed: Press RETURN to get started! Would you like to terminate autoinstall? [yes]: [Enter] Switch> show version | include ROM ROM: 12.2(31r)SGA1 System returned to ROM by reload Review the output and look for the ROM version. Verify that the version is the desired new version. If the switch does not boot properly or has the wrong ROM version, contact Tekelec Customer Care. 19.
3 Procedures Switch# show version | include register Configuration register is 0xXXXX (will be 0x2102 at next reload) Switch# reload Proceed with reload? [confirm] Wait until the switch reloads, then issue the following command to ensure the switch is at the appropriate IOS version: Switch> show version | include image System image file is "bootflash:cat4500-ipbasek9-mz.122-53.SG2.bin" If the switch is not at the appropriate version, stop here and contact Customer Care Center.
3 Procedures Ensure that the tftp service is not running. A zero is expected. # tpdProvd --client --noxml --ns=Xinetd getXinetdService service tftp Login on Remote: platcfg Password of platcfg: 0 # If it returns a 1, stop the process by executing this command: # tpdProvd --client --noxml --ns=Xinetd stopXinetdService service tftp force yes Login on Remote: platcfg Password of platcfg: 1 # This should return a 1. Repeat this process until stopXinetdService returns a 1.
3 Procedures as the answers are site specific that the user MUST modify. Other prompts that don't have a as an answer must be entered EXACTLY as they are shown here.
3 Procedures dir: /var/TKLC/smac/image # 30. Virtual PM&C: Setup netConfig repository with necessary ssh information. Use netConfig to create a repository entry that will use the ssh service. This command will provide the user with several prompts. The prompts with as the answers are site specific that the user MUST modify. Other prompts that don't have a as answer must be entered EXACTLY as they are shown here.
3 Procedures What is the address used for network device access? Should the live oob adapter be added (y/n)? y Adding cli protocol for switch1A using oob... OOB device access already set: console_service Device named switch1A successfully added. To check that you entered the information correctly, use the following command: # netConfig --repo showDevice name=switch1A and check the output, which will be similar to the one shown below.
3 Procedures To check that you entered the information correctly, use the following command: # netConfig --repo showDevice name=switch1B and check the output, which will be similar to the one shown below. # netConfig --repo showDevice name=switch1B Device: switch1A Vendor: Cisco Model: 4948E FW Ver: 0 Access: Network: 10.240.64.35 Access: OOB: Service: console_service Console: switch1B_console Init Protocol Configured Live Protocol Configured # 33.
3 Procedures Use netConfig to get the hostname of the switch, to verify that the switch was initialized properly, and to verify that netConfig can connect to the switch. # netConfig --device=switch1B getHostname Hostname: switch1B # Note: If this command fails, stop this procedure and contact Customer Care Center 34. Virtual PM&C: Configure both switches Configure both switches by issuing the following command: # netConfig --file=/usr/TKLC/smac/etc/switch/xml/4948_4948E_configure.
3 Procedures Attach switch1B customer uplink cables and detach switch1A customer uplink cables. Refer to application documentation for which ports are uplink ports. Note: If the customer is using standard 802.1D spanning-tree, the links may take up to 50 seconds to become active. 40. Virtual PM&C: Verify access to customer network Verify connectivity to the customer network by issuing the following command: # ping PING ntpserver1 (10.250.32.51) 56(84) bytes of data.
3 Procedures Steps within this procedure may refer to variable data indicated by text within "<>". Refer to this table for the proper value to insert depending on your system type.
3 Procedures Note: Uplinks must be disconnected from the customer network prior to executing this procedure. One of the steps in this procedure will instruct when to reconnect these uplink cables. Refer to the application appropriate schematic or procedure for determining which cables are used for customer uplink. Needed Material: • • • • • HP Misc.
3 Procedures If the output from the above command is not successful, refer back to the application documentation. 3. Management Server: Procedure pre-check - Determine Platform Version Determine Platform version of the system by issuing the following command: # appRev If the following is shown in the output, the Platform version is 6.0: Base Distro Release: 6.0.x-x.x.x The values of x-x.x.x do not matter. The value of 6.0 shows the platform version.
3 Procedures Press Enter Switch> show version | include image System image file is "bootflash:cat4500-ipbasek9-mz.122-53.SG2.bin" Switch> show version | include ROM ROM: 12.2(31r)SGA1 System returned to ROM by reload Note the image version for comparison in a following step. To exit from console enter , , <.> and you will be returned to the server prompt. 6. Management Server: Determine if switch IOS and/or PROM upgrade is required.
3 Procedures The command output should contain the IP address of the variable .
3 Procedures If configuring switch1A, use this comand: Switch(config-if)# ip address If configuring switch1B, use this command: Switch(config-if)# ip address Continue with these commands: Switch(config-if)# Switch(config-if)# Switch(config-if)# Switch(config-if)# no shut int range gi1/2 - 4 shut int range gi1/1, gi1/40 If the model is C4948, execute this command: Switch(config-if)# switchport trunk encap dot1q Continue w
3 Procedures 13. Management Server (Switch console session): Reload the switch Switch# reload System configuration has been modified. Save? [yes/no]: no Proceed with reload? [confirm] [Enter] === Boot messages removed === Type [Control-C] when Type control-C to prevent autobooting is displayed on the screen. 14. Management Server (Switch console session): Upgrade PROM rommon 1 > boot bootflash: === PROM upgrade messages removed === System will reset itself and reboot within few seconds...
3 Procedures Note: Take note which filename matches with because the other filename is the value for the variable which will be used to define which file is deleted. 17. Management Server (switch console session): Set the active IOS image and config-register from the switch console session that was established.
3 Procedures Press Enter Switch> en Switch# conf t Switch(config)# config-register 0x2101 Switch(config)# no vlan 2-4094 Switch(config)# end Switch# write erase [confirm] Switch# reload To exit from console enter , , <.> and you will be returned to the server prompt.
3 Procedures If it returns a 1, stop the process by executing this command: # tpdProvd --client --noxml --ns=Xinetd stopXinetdService service tftp force yes Login on Remote: platcfg Password of platcfg: 1 # This should return a 1. Repeat this process until stopXinetdService returns a 1. Then run Appendix E Disabling TFTP to ensure tftp is turned off.
3 Procedures Host: 10.240.64.36 Options: password: D8396824B3B2B9EE user: platcfg # 24. Management server: Setup netConfig repository with necessary tftp information. Use netConfig to create a repository entry that will use the tftp service. This command will give the user several prompts. The prompts with as the answers are site specific that the user MUST modify. Other prompts that don't have a as an answer must be entered EXACTLY as they are shown here.
3 Procedures To ensure that you have entered the information correctly, use the following command and inspect the output, which will be similar to the one shown below. # netConfig --repo showService name=ssh_service Service Name: ssh_service Type: ssh Host: 10.240.64.36 Options: password: C20F7D639AE7E7 user: root # 26. Management Server: Setup netConfig repository with switch information Use netConfig to create a repository entry for switch1A. This command will give the user several prompts.
3 Procedures Service: console_service Console: switch1A_console Init Protocol Configured Live Protocol Configured # Note: The model will be either 4948, 4948E, or 4948E-F depending on the model of the device. If you do not know, stop now and contact Customer Care Center. Add switch1B to the repository: # netConfig --repo addDevice name=switch1B --reuseCredentials Device Vendor? Cisco Device Model? 4948 Should the init oob adapter be added (y/n)? y Adding consoleInit protocol for switch1B using oob...
3 Procedures 28. Management Server: Modify 4948_4948E_configure.xml file for information needed to initialize the switch Update the 4948_4948E_configure.xml file for site specific information. Values to be edited in those files are preceded with a dollar sign, an example is $ some_variable_name . When done editing the file, save and quit. 29.
3 Procedures Configure the switch by issuing the following command: # netConfig --file=/usr/TKLC/plat/etc/switch/xml/4948_4948E_configure.xml Processing file: file=/usr/TKLC/plat/etc/switch/xml/4948_4948E_configure.xml # Note: This step takes about 2-3 minutes to complete. Check the output of this command for any errors. If this fails for any reason, stop this procedure and contact Customer Care Center. A successful completion of netConfig will return the user to the prompt. 31.
3 Procedures Note: If the customer is using standard 802.1D spanning-tree, the links may take up to 50 seconds to become active 37. Perform 3.1.5 Backup Cisco 4948/4948E/4948E-F Aggregation Switch and/or Cisco 3020 Enclosure Switch (netConfig) for each switch configured in this procedure. 3.1.3 Replace a failed 4948/4948E/4948E-F switch (PM&C Installed) (netConfig) The procedure details the steps necessary to replace a failed 4948/4948E/4948E-F switch. This procedures assumes a Platform 6.0 interconnect.
3 Procedures Fill in the appropriate value for this site: ____________________________________ Fill in the appropriate value for this site: ____________________________________ Fill in the appropriate value for this site ________________________________________ Ethernet Interface DL360 DL380 eth01 eth01 eth02 eth03 Variable Platform 6.
3 Procedures If not already done so, determine whether switch1A or switch1B failed, locate the failed switch, and detach all network and console cables from the failed switch. Note: If needed label cables prior to removal. 3. Cabinet: Replace switch If not already done so, remove failed switch and replace with new switch of same model. 4.
3 Procedures If the "autoinstall" line below does not appear, the switch may not be in factory default condition, continue with the step, disregarding this line: Would you like to terminate autoinstall? [yes]: Enter Switch> enable Switch# If "enable" command above prompts for a password, the switch in not in factory default configuration. If this is the case, do not proceed and contact Customer Care Center for corrective action. This procedure is for a replacement switch with manufacturing default state.
3 Procedures If configuring either switch1A or switch1B, and the model is C4948, execute this command: Switch(config-if)# Switch(config-if)# Switch(config-if)# Switch(config-if)# Switch(config-if)# Switch(config-if)# Switch(config-if)# Switch(config-if)# Switch(config-if)# switchport trunk encap dot1q switchport mode trunk spanning-tree portfast trunk int range gi1/1 – 4 switchport trunk encap dot1q switchport mode trunk spanning-tree portfast trunk channel-group 8 mode active end If configuring either s
3 Procedures Verify your location on the server # pwd /some/user/home/dir/path 16. Virtual PM&C: Copy the switch backup files to the current directory # cp /usr/TKLC/smac/etc/backup/-backup* . Get a list of the file copied over. Note: 'switch1A' is shown as an example. # ls switch1A-backup switch1A-backup.info switch1A-backup.vlan 17. Virtual PM&C: Verify switch is initialized Verify switch is at least initialized correctly and connectivity to the switch by verifying hostname.
3 Procedures 64 bytes from ntpserver1 (10.250.32.51): icmp_seq=1 ttl=62 time=0.223 ms 64 bytes from ntpserver1 (10.250.32.51): icmp_seq=2 ttl=62 time=0.152 ms 23. Cabinet: Connect network cables from customer network Re-attach the uplink cables that were disconnected in step 21. 3.1.4 Replace a failed 4948/4948E/4948E-F switch (RMS system no PM&C)(netConfig) The procedure details the steps necessary to replace a failed 4948/4948E/4948E-F switch. This procedures assumes a Platform 6.0 interconnect.
3 Procedures Fill in the appropriate value for this site: ____________________________________ Fill in the appropriate value for this site: ____________________________________ Fill in the appropriate value for this site: ____________________________________ Fill in the appropriate value for this site: ____________________________________ Fill in the appropri
3 Procedures If not already done so, determine whether switch1A or switch1B failed, locate the failed switch, and detach all network and console cables from the failed switch. Note: If needed label cables prior to removal. 3. Cabinet: Replace switch If not already done so, remove failed switch and replace with new switch of same model. 4.
3 Procedures b) Connect serially to switch1B by issuing the following command: # /usr/bin/console -M -l platcfg switch1B_console Enter platcfg@localhost's password: [Enter `^Ec?' for help] Press Enter If the "autoinstall" line below does not appear, the switch may not be in factory default condition, continue with the step, disregarding this line: Would you like to terminate autoinstall? [yes]: Enter Switch> enable Switch# If "enable" command a
3 Procedures 13. Management Server: Restore the switch to the latest known good configuration. Navigate to the home directory. # cd ~ Verify your location on the server # pwd /some/user/home/dir/path 14. Management Server: Copy the switch backup files to the current directory # cp /usr/TKLC/plat/etc/switch/backup/-backup* . Get a list of the file copied over. Note: 'switch1A' is shown as an example. # ls switch1A-backup switch1A-backup.
3 Procedures Verify connectivity to the customer network by issuing the following command: # ping PING ntpserver1 (10.250.32.51) 56(84) bytes of data. 64 bytes from ntpserver1 (10.250.32.51): icmp_seq=0 ttl=62 time=0.150 ms 64 bytes from ntpserver1 (10.250.32.51): icmp_seq=1 ttl=62 time=0.223 ms 64 bytes from ntpserver1 (10.250.32.51): icmp_seq=2 ttl=62 time=0.152 ms 21. Cabinet: Connect network cables from customer network.
3 Procedures 1. Verify switch is at least initialized correctly and connectivity to the switch by verifying hostname # netConfig --device= getHostname Hostname: switch1A # Note: The value beside "Hostname:" should be the same as the variable. 2. Run command "netConfig --repo showService name=ssh_service" and look for ssh service. # netConfig --repo showService name=ssh_service Service Name: ssh_service Type: ssh Host: 10.250.62.
3 Procedures 3.8.2 Installing TVOE on the Management Server, 3.8.3 TVOE Network Configuration, 3.8.4 Deploy PM&C Guest, and 3.8.5 Setup PM&C are required to be completed before this procedure is attempted. Application management network interfaces must be configured on the management servers prior to executing this procedure. • Application username and password for creating switch backups must be configured on the management server prior to executing this procedure.
3 Procedures Value gathered from site survey pmacadmin Refer to TR006061 Note: The onboard administrators are not available during the configuration of Cisco 4948/4948E/4948E-F switches. Note: Uplinks must be disconnected from the customer network prior to executing this procedure. One of the steps in this procedure will instruct when to reconnect these uplink cables.
3 Procedures On each management server, determine the Platform version of the system by issuing the following command: # appRev If the following is shown in the output, the Platform version is 6.0: Base Distro Release: 6.0.x-x.x.x The values of x-x.x.x do not matter. The value of 6.0 shows the platform verison. If the command shows a Base Distro Release version lower than 6.0, or fails to execute, stop this procedure and refer back to application procedures.
3 Procedures From management server1A, log into the console of the virtual pmac instance found in step 4. # virsh console vm-pmac1A Connected to domain vm-pmac1A Escape character is ^] CentOS release 6.2 (Final) Kernel 2.6.32-220.7.1.el6prerel6.0.0_80.13.0.x86_64 on an x86_64 vm-pmac1A login: root Password: Last login: Fri May 25 16:39:04 on ttyS4 If this command fails, it is likely that a virtual instance of PM&C is not installed.
3 Procedures Options: password: D8396824B3B2B9EE user: platcfg # 9. Virtual PM&C: Setup netConfig repository with necessary tftp information. Use netConfig to create a repository entry that will use the tftp service. This command will give the user several prompts. The prompts with as the answers are site specific that the user MUST modify. Other prompts that don't have a as an answer must be entered EXACTLY as they are shown here.
3 Procedures To ensure that you entered the information correctly, use the following command and inspect the output, which will be similar to the one shown below. # netConfig --repo showService name=ssh_service Service Name: ssh_service Type: ssh Host: 10.250.62.85 Options: password: C20F7D639AE7E7 user: root # 11. Virtual PM&C: Setup netConfig repository with Aggregation switch information. Note: If there are no aggregation switches in this deployment, skip to the next step.
3 Procedures Console: switch1A_console Init Protocol Configured Live Protocol Configured # Create the Repository entry for switch1B Note: The model can be 4948, 4948E, or 4948E-F depending on the model of the device. If you do not know, stop now and contact Customer Care Center. # netConfig --repo addDevice name=switch1B --reuseCredentials Device Vendor? Cisco Device Model? 4948E Should the init oob adapter be added (y/n)? y Adding consoleInit protocol for switch1A using oob...
3 Procedures Note: The device name must be 20 characters or less # netConfig --repo addDevice name=C3020_IOBAY1 --reuseCredentials Device Vendor? Cisco Device Model? 3020 Should the init network adapter be added (y/n)? y Adding netBootInit protocol for C3020_IOBAY1 using network...
3 Procedures What is the device privileged mode password? Verify Password: Should the live oob adapter be added (y/n)? n Should the init network adapter be added (y/n)? y Adding sshInit protocol for 6120XG_IOBAY1 using network... Network device access already set: 10.240.8.9 Device named 6120XG_IOBAY1 successfully added.
3 Procedures See referring application documentation Fill in the appropriate value for this site: Fill in the appropriate value for this site: Fill in the appropriate value for this site: Fill in the appropriate value for this site: Fill in the appropriate value for this site: Fill in the ap
3 Procedures Switch(config)# crypto key generate rsa usage-keys label sshkeys modulus 768 Switch(config)# aaa new-model Switch(config)# aaa authentication login onconsole line Switch(config)# username secret Switch(config)# enable secret Switch(config)# line vty 0 15 Switch(config-line)# no password Switch(config-line)# transport input ssh Switch(config)# exit Switch(config)# line console 0 Switch(config-line)# login authenticat
3 Procedures Prerequisites: • • • • It is essential that PM&C is installed. In addition, 3.6.1 Configure Initial OA IP and 3.6.2 Configure initial OA settings via configuration wizard must be completed. Also, It is essential that 3.2.9 Upgrade 3020 Switch IOS Firmware has been completed successfully. Conditional Prerequisite: If the aggregation switches are provided by Tekelec, then the Cisco 4948/4948E/4948E-F switches must be configured using 3.1.
3 Procedures If the /etc/xinetd.d/tftp file matches the output below, proceed to step 6. If the /etc/xinetd.d/tftp file does not match the output below then proceed to step 5. # cat /etc/xinetd.d/tftp service tftp { socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd server_args = -s /var/TKLC/smac/image disable = no per_source = 11 cps = 100 2 flags = IPv4 } 5. Virtual PM&C: Configure TFTP Service Ensure that the tftp service is not running. A zero is expected.
3 Procedures Service Name: tftp_service Type: tftp Host: 10.240.8.4 Options: dir: /var/TKLC/smac/image [root@pmac5000101 ~]# If tftp_service is already configured, skip to step 9. Otherwise, continue on to step 8. 8. Virtual PM&C: Setup netConfig repository with necessary tftp information Use netConfig to create a repository entry that will use the tftp service. This command will give the user several prompts. The prompts with as the answers are site specific that the user MUST modify.
3 Procedures What is the address used for network device access? What is the platform access username? What is the platform user password? Verify Password: What is the device privileged mode password? Verify Password: Should the init file adapter be added (y/n)? y Adding netBootInit protocol for C3020_IOBAY1 using file...
3 Procedures Update the 3020_configure.xml file for the values noted in the next sentence. Values to be modified by the user will be notated in this step by a preceding dollar sign. So a value that has $some_variable_name will need to be modified, removing the dollar sign and the less than, greater than sign. When done editing the file, save and quit. 12. Virtual PM&C: Prepare the system for tftp Note: Before executing this step, ensure that no IPM activity is taking place First, look at the /etc/xinetd.
3 Procedures A new page will be opened. If you are asked for a username and password, leave the username blank and use the appropriate password provided by the application documentation. Then click OK. If you are prompted with the "Express Setup" screen, click Refresh.
3 Procedures If you are prompted with "Do you want a secured session with the switch?", click on No. Then a new Catalyst Blade Switch 3020 Device Manager will be opened. 14. OA GUI: Restore switch to factory defaults Navigate to Configure > Restart/Reset.
3 Procedures Click the circle that says "Reset the switch to factory defaults, and then restart the switch". Then click the "Submit" button. A pop-up window will appear that looks like this: Click OK and the switch will be reset to factory defaults and reloaded. 15. Virtual PM&C: Initialize the switch Note: This command must be entered at most 5 minutes after step 12 is completed. If it is not, repeat step 12.
3 Procedures Check the output of this command for any errors. If this fails for any reason, stop this procedure and contact Customer Care Center. A successful completion of netConfig will return the user to the prompt. Go back to step 9 and repeat for each 3020 switch. 16. Virtual PM&C: Configure the switches Configure both switches by issuing the following command: # netConfig --file=/usr/TKLC/smac/etc/switch/xml/3020_configure.xml Processing file: /usr/TKLC/smac/etc/switch/xml/3020_configure.
3 Procedures 3.2.2 Reconfigure a failed 3020 switch (netConfig) The procedure describes all of the required steps to configure a replacement 3020 switch. Prerequisite: Prerequisites for this procedure are to follow the prerequisites for procedures referenced in the steps of this procedure. It also assumed the user can determine which switch is the failed switch. Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.
3 Procedures Note: 'switch1A' is shown as an example. # ls switch1A-backup switch1A-backup.info switch1A-backup.vlan 8. Virtual PM&C: Verify switch is initialized Verify switch is at least initialized correctly and connectivity to the switch by verifying hostname. # netConfig --device= getHostname Hostname: switch1A # Note: The value beside 'Hostname:' should be the same as the variable. 9.
3 Procedures 1. Virtual PM&C: Prepare for switch configuration If the aggregation switches are provided by Tekelec, login to the management server, then run: # ping -w3 # ping -w3 # ping -w3 If the aggregation switches are provided by the customer, login to the management server, then run: # ping -w3 2.
3 Procedures • Where [single,LAG] are variables for either one of 2 files-see the following: • 6120XG_SingleUplink_configure.xml is for one uplink per enclosure switch topology • 6120XG_LAGUplink_configure.xml is for LAG uplink topology 5. Virtual PM&C: verify the switch configuration file template in the tftp directory Verify the switch initialization template file and configuration file template are in the correct directory. # ls -l /usr/TKLC/smac/etc/switch/xml/*6120XG*.
3 Procedures Add service for ssh_service successful # To ensure that you entered the information correctly, use the following command and inspect the output, which will be similar to the one shown below. # netConfig --repo showService name=ssh_service Service Name: ssh_service Type: ssh Host: 10.240.8.4 Options: password: C20F7D639AE7E7 user: root # 8.
3 Procedures Apply the QoS traffic template settings. # netConfig --file=/usr/TKLC/smac/etc/switch/xml/addQOS_trafficTemplate_6120XG.xml Note: The switch will reboot after this command. This step will take 2-5 minutes. 12. Virtual PM&C: Verify proper configuration of HP 6120XG switches Once each HP 6120XG has finished booting from the previous step, verify network reachability and configuration.
3 Procedures 5. Virtual PM&C: Copy the switch backup files to the current directory # cp /usr/TKLC/smac/etc/switch/backup/-backup* . 6. Backup File: Remove Uplink-Failure-Detection Note: These lines will be used later, take note of and .
3 Procedures Procedure Reference Tables: Variable Value hostname of the switch 1. Verify switch is at least initialized correctly and connectivity by verifying hostname # netConfig --device= getHostname Hostname: 6120_IOBAY3 # Note: The value beside "Hostname:" should be the same as the variable. 2. Verify the ssh service is configured by running command "netConfig --repo showService name=ssh_service" and look for ssh service.
3 Procedures 3. Ensure the directory where the backups will be stored exists. # ls -l /usr/TKLC/smac/etc/switch/backup If you receive an error such as the following: -bash: ls: /usr/TKLC/smac/etc/switch/backup: No such file or directory Then the directory must be created by issuing the following command: # mkdir -p /usr/TKLC/smac/etc/switch/backup 4. Navigate to the backup directory. # cd /usr/TKLC/smac/etc/switch/backup 5.
3 Procedures See Application Documentation See Application Documentation See Application Documentation 1. Virtual PM&C: Log into the PM&C Guest Log into the PM&C Guest. 2. Virtual PM&C: Determine the port mirror source devices use netConfig to list the devices in its repository and determine which devices should be configured with port mirroring.
3 Procedures For Port Mirroring: # netConfig --device= addPortMirror session=1 interface= destInterface= direction=both Note: The interface option allows for more than one source interface. The value can be entered as a single interface ex: GE1 (1Gb port) or tenGE1 (10Gb port) or it can be entered as a range of interfaces separated by commas and dashes ex: GE1-5,GE7,tenGE9-10. Note: The only direction supported by the HP6120XG is 'both.
3 Procedures Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document. 1. Management Server: Verify network connectivity to 6120XG switches For each 6120XG switch, verify reachability. # ping -w3 2.
3 Procedures 6. Backup the Configuration Perform the 3.2.5 Backup 6120XG Enclosure Switch procedure and then return to this procedure and continue with step 7 of this procedure. 7. Restore the Configuration Perform steps 3-8 of the 3.2.4 Reconfigure a failed HP 6120XG switch (netConfig) procedure and continue with step 8 of this procedure. 8. Verify the Configuration Once each HP 6120XG has finished booting from the previous step, verify network reachability and configuration.
3 Procedures Switch(config)# line vty 0 15 Switch(config-line)# no password Switch(config-line)# transport input ssh Switch(config)# exit Switch(config)# ip ssh version 2 Switch(config)# no ip http server Switch(config)# no ip http secure-server Switch(config)# no ip domain lookup Switch(config)# end Switch# write memory 4. Switch CLI: Reload the switch and verify configuration. Reload the switch and verify the configuration from step 3. If a command was not applied, repeat step 3.
3 Procedures • Must be familiar with "vim" command line editing tool Needed material: • HP Misc. Firmware ISO or DVD • HP Solutions Firmware Upgrade Pack Release Notes [3] • Application specific documentation (documentation that referred to this procedure) Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document. 1. Virtual PM&C: Login as root to the Virtual PM&C server.
3 Procedures Ensure that the tftp service is not running. A zero is expected. # tpdProvd --client --noxml --ns=Xinetd getXinetdService service tftp Login on Remote: platcfg Password of platcfg: 0 # If this command returns a 1 perform the steps in Appendix E Disabling TFTP and then continue this procedure at the next step. 5. Virtual PM&C: Edit the /etc/xinetd.d/tftp file until it matches the output in Step 3. 6. Virtual PM&C: Modify PM&C Feature to allow TFTP. Enable the DEVICE.NETWORK.
3 Procedures To check that you entered the information correctly, use the following command: # netConfig --repo showService name=tftp_service and check the output, which will be similar to the one shown below (Note: only the tftp service info has been shown in this example. If the previous step and this step were done correctly, both the console_service and tftp_service entries would show up) # netConfig --repo showService name=tftp_service Services: Service Name: tftp_service Type: tftp Host: 10.240.8.
3 Procedures First, look at the /etc/xinetd.d/tftp file to ensure proper values. # cat /etc/xinetd.d/tftp | grep server_args server_args = -s /var/TKLC/smac/image # If the command does not show the directory, edit the file so that it has the appropriate values. Then, turn on tftp: # tpdProvd --client --noxml --ns=Xinetd startXinetdService service tftp Login on Remote: platcfg Password of platcfg: Note: This should return a '1'. If it does not, retry the command.
3 Procedures If you are prompted with the "Express Setup" screen, click Refresh. If you are prompted with "Do you want a secured session with the switch?" click on No.
3 Procedures Then a new Catalyst Blade Switch 3020 Device Manager will be opened. 15. OA GUI Restore switch to factory defaults. Navigate to Configure > Restart/Reset. Click the circle that says "Reset the switch to factory defaults, and then restart the switch". Then click the Submit button.
3 Procedures Click OK and the switch will be reset to factory defaults and reloaded. 16. 3020 Switch CLI: Use telnet to connect to the command line interface of the 3020 switch once it has had time to restart and acquire the configuration from the "network-confg" file. Then login and enter enabled mode: User Access Verification Password:tklc Switch>en Password:tklc Switch# 17.
3 Procedures Image to be installed already exists...will be removed before download. Deleting `flash:cbs30x0-ipbasek9-mz.122-58.SE1' to create required space Extracting images from archive into flash... cbs30x0-ipbasek9-mz.122-58.SE1/ (directory) extracting cbs30x0-ipbasek9-mz.122-58.SE1/cbs30x0-ipbasek9-mz.122-58.SE1.bin (13988491 bytes) Skipping many lines beginning with "extracting".
3 Procedures Disable TFTP. Perform the steps in Appendix E Disabling TFTP and then continue at the next step 21. Virtual PM&C: Clean up the network-confg and 3020 IOS firmware files, answering "yes" when prompted. The 3020 IOS filename used is an example. Make sure to remove any 3020 IOS firmware files present. # rm /var/TKLC/smac/image/network-confg rm: remove regular file `/var/TKLC/smac/image/network-confg'?yes # rm /var/TKLC/smac/image/cbs30x0-ipbasek9-tar.122-58.SE1.
3 Procedures 4. 6120XG Switch: Find current firmware version and compart to release notes Switch(config)# show version Image stamp: /sw/code/build/vern(Z 14 zin t4b) Sep 23, 2010 16:48:29 z.14.12 31 Boot Image: Secondary Record the firmware version (z.14.12 in this case) and the current Boot Image location being used (Secondary in this case). Compare the firmware version currently being used to the latest version specified in the HP Solutions Firmware Upgrade Pack Release Notes [3].
3 Procedures Go into the switch's menu interface and type "y" to save the configuration Switch(config)# menu Do you want to save current configuration [y/n/^C]? y Select: 4. Event Log Then Select: End Keep this terminal window open. 8. Local Workstatiion: • • • • • • • • • • Open WinSCP on the local workstation Click on "Preferences" in the list on the left Select the "Commander" interface (click on the circle next to it) Then click on the "Preferences...
3 Procedures • Once WinSCP logs into the switch, in the left window find the fimware file that was copied to the local workstation in Step 1. • In the right window on the switch, oopen the folder labeld "os" • Drag the firmware file on the left to the window on the right. • A copy window pop up with "/os/*.*" written will appear. Replace *.* with either primary or secondary depending on which boot image is being upgraded. (in this example it would be primary) • Click the Copy button. 11.
3 Procedures Then select: 5. Command Line (CLI) Switch(config)# 13. 6120XG Switch: Check the firmware version. Run the show flash command to make sure the Image being updated has the correct firmware versiion. (in this example Primary Image has changed to z.14.22) Switch(config)# show flash Image Size(Bytes)Date Version -------------------------Primary Image : 7732899 10/21/10 Secondary Image : 7193633 06/23/10 Boot Rom Version: z.14.09 Default Boot : Secondary -------z.14.22 z.14.12 14.
3 Procedures Secondary Image : 7732899 Boot Rom Version: Z.14.09 Default Boot : Primary 10/21/10 Z.14.22 3.2.11 Configure QoS (DSCP and/or CoS) on HP 6120XG Switches Prerequisites: • It is essential that all switches have been configured successfully using 3.2.
3 Procedures 3. Virtual PM&C:Add DSCP and/or CoS Policy. Using the information from the previous step, use one of the following commands to configure DSCP and/or CoS marking on the device.
3 Procedures • • • • 3.6.1 Configure Initial OA IP, 3.8.2 Installing TVOE on the Management Server, 3.8.3 TVOE Network Configuration, and 3.8.4 Deploy PM&C Guest Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document. 1. OA shell: Login to the active OA Login to OA via ssh as root user. login as: root -------------------------------------------------------WARNING: This is a private system.
3 Procedures Press Enter Enter (Enter twice) and log in as root user. swd77 console login: root Password: Please change passwords for switch default accounts now. Use Control-C to exit or press 'Enter' key to proceed. Press Enter to see the prompt. 3. Brocade switch console : Set root user password swd77:root> passwd root Changing password for root Enter new password: Re-type new password: passwd: all authentication tokens updated successfully Saving password to stable storage.
3 Procedures Check if the change was applied with: swd77:root> tsclockserver Active NTPServer 10.250.32.10 Configured NTPServer List 10.250.32.10 10. Brocade switch console : Backup configuration swd77:root> configUpload Protocol (scp, ftp, local) [ftp]: scp Server Name or IP Address [host]: User Name [user]: pmacadmin File Name [config.
3 Procedures Login to OA via ssh as root user. login as: root -------------------------------------------------------WARNING: This is a private system. Do not attempt to login unless you are an authorized user. Any authorized or unauthorized access and use may be monitored and can result in criminal or civil prosecution under applicable law. -------------------------------------------------------Firmware Version: 3.00 Built: 03/19/2010 @ 14:13 OA BayNumber: 1 OARole: Active root@10.240.17.
3 Procedures -----------------------------------------FOS v6.2.1b v6.2.1b Check the FOS version. If the version is at level recommended by the Firmware Release Notes [3] there is no need to upgrade the firmware on this switch. Skip the rest of this procedure if firmware version of both switches has been verified. 4. Management server: Prepare to upgrade Brocade switch firmware Note: This step only needs to be done once on the management server. If needed , login to the management server as root.
3 Procedures Restarting system. 6. Brocade switch console : After the switch reboots, the console login prompt will appear. swd77 console login: admin Password: Please change passwords for switch default accounts now. Use Control-C to exit or press 'Enter' key to proceed. Press Control-C to skip changing passwords. swd77:admin> firmwaredownloadstatus [1]: Tue Mar 9 20:21:37 2010 Firmware is being downloaded to the switch. This step may take up to 30 minutes.
3 Procedures Prerequisites: • 3.3.1 Configure Brocade Switches has been completed. • Knowing the network cabling and SAN requirements by blade server is required. Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document. 1. General guide This procedure is optional. Skipping this procedure will allow switches to connect to all ports.
3 Procedures 3. Fibre Channel switch console: Navigate to Zone Admin Navigate to Zone Admin. 4. Fibre Channel switch console: Create new zone Select Zone tab. Click on New Zone.
3 Procedures Type in an appropriate name and click OK. 5. Fibre Channel switch console : Add port members into the zone In the popup menu choose the zone where ports should be added. Expand the Ports and Attached Devices twice. Select the appropriate ports under Ports and Attached Devices. A single Brocade port should be just in a single zone. Press the Add Member button. Then create “catch-all“ zone that covers all the remaining devices (blade servers and ports) that are not in the zones specified above.
3 Procedures Enter appropriate name such as "Production_Zone_Config" and click OK. 7. Fibre Channel switch console : Add Zones into Zone Config Expand the Zones Selection List. Select all desired zones and press Add Member button. Press Save Config and then Yes.
3 Procedures Observe the status at the botton of the screen. Make sure that the "Successfully committed the changes to the fabric" message is displayed in blue at the bottom of the window. 8. Fibre Channel switch console : Enable Zone Config Press Enable Config Use the pull down menu to select the Zone Config to apply. Press OK Press Yes Observe the status at the botton of the screen. Make sure Successfully committed the changes to the fabric appears in blue at the bottom of the window. 9.
3 Procedures 2.
3 Procedures Trap recipient Severity level : (0..5) [0] 2 Trap recipient Port : (0..65535) [162] Community (ro): [common] Trap Recipient's IP address : [0.0.0.0] Trap recipient Severity level : (0..5) [0] 2 Trap recipient Port : (0..65535) [162] Community (ro): [FibreChannel] Trap Recipient's IPaddress : [0.0.0.0] Committing configuration...done. Replace the passwords in the following examples with the appropriate passwords provided by the application.
3 Procedures sysDescr: [Fibre Channel Switch.] sysLocation: [End User Premise.] sysContact: [Field Support.] authTrapsEnabled (true, t, false, f): [true] Committing configuration...done. Verify the settings are correct: swd77:admin> snmpconfig --show systemGroup 7. Brocade switch console: Log out swd77:aadmin> logout 8. Configure settings for the other Brocade switch Repeat steps 1 through 7 on the other Brocade switch in the enclosure. 3.4 SAN Storage Arrays Procedures 3.4.
3 Procedures The user may have to log in using the manage username and the corresponding password.
3 Procedures 5. Fibre Channel Disk Controller: Delete ftp user # delete user ftp 6. Fibre Channel Disk Controller Delete admin user Note: This step only required if device is a P2000 G3 array # delete user admin This account is an additional management account added by HP and is not needed 7. Fibre Channel Disk Controller: Change password for manage account # set password manage Use the appropriate password provided by the application documentation. 8.
3 Procedures Verify service and security protocols status: # show protocols Verify user settings: # show users 11. Fibre Channel Disk Controller: Configure SNMP trap host # set snmp-parameters enable crit add-trap-host This will enable delivery of critical events to the target destination. 12. Fibre Channel Disk Controller: Logout Logout from the Fibre Channel Disk Controller console. # exit 3.4.
3 Procedures Press Change System Configuration. 4. Fibre Channel Disk Controller GUI: Verify advanced settings Verify that the following message appears above the System Configuration area: 5. Fibre Channel Disk Controller GUI: Logout Logout by pressing the LOG OFF button on the left hand side. 3.4.4 Configuring Advanced Settings on P2000 Fibre Channel Disk Controllers This procedure configures advanced settings on each P2000 controller. Prerequisites: • 3.4.
3 Procedures 2. Fibre Channel Disk Controller: Configure advanced settings # set advanced-settings dynamic-spares disabled Info: Command completed successfully. - Parameter 'dynamic-spares' was set to 'disabled'. Success: Command completed successfully. - The settings were changed successfully. # set advanced-settings background-scrub enabled Info: Command completed successfully. - Parameter 'background-scrub' was set to 'enabled'. Success: Command completed successfully.
3 Procedures In the left column, click on MANAGE, then click on UPDATE SOFTWARE and if needed, controller software Look at the Current Storage Controller Code Version. If the version is at the level required by the Release Notes [3] or greater, there is no need to upgrade. Skip the remainder of this procedure. 3.
3 Procedures After about 20 minutes the user should be able to login to one of the controllers as in step 1 and verify the firmware version as in step 2. 3.4.6 Upgrade Firmware on MSA P2000 Disk Controllers This procedure will upgrade the firmware of the MSA P2000 disk controllers. Prerequisites: • 3.4.4 Configuring Advanced Settings on P2000 Fibre Channel Disk Controllers has been completed. • 3.8.9 Adding ISO Images to the PM&C Image Repository has been completed using Misc. Firmware CD.
3 Procedures 3. Prepare to upgrade Fibre Channel disk controller Copy the following file from the management server to the PC using an scp client: /usr/TKLC/smac/html/TPD/HPFW--872-2488-XXX--HPFW/files/.bin Windows users: Refer to Appendix A (A.1 Using WinSCP) to copy the file to the PC. 4. Fibre channel disk controller GUI: Upgrade firmware In the browser opened in step 2, execute the following commands: Click Browse… Browse to the location of the file copied in step 3.
3 Procedures Note: The vdisk reconstruction can take hours or days to complete, depending on the vdisk RAID level and size, disk speed, utility priority, and other processes running on the storage system. You can stop reconstruction only by deleting the vdisk. Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by refering to the 1.4 Customer Care Center section of this document. 1.
3 Procedures When a disk fails, the system looks for a dedicated spare first in order to reconstruct the vdisk. If it does not find a properly sized dedicated spare, it looks for a global spare. A properly sized vdisk spare is one whose capacity is equal to or greater than that of the largest disk in the vdisk. A properly sized global spare is one whose capacity is equal to or greater than that of the largest disk in the disk array.
3 Procedures If you choose to add a global spare to reconstruct a vdisk, in the Configuration View panel, right-click the system . Then in the right hand side blue bar menu click Provisioning and select Manage Global Spares Switch to Graphical representation if needed . Select the disk that was replaced by clicking the check box on it. It should be labeled with an AVAIL on it. Click the Modify Spares button . Verify that the color of the disk changes to blue and a GLOBALSP appears on the disk.
3 Procedures Switch to Graphical representation if needed . After ensuring the disk is in the correct enclosure, select the replaced disk by clicking the check box on it. It should be labeled with an AVAIL on it. Click the Modify Spares button . Verify that the color of the disk changes to green and SPARE appears on the disk. If there is a problem, new popup will explain the failure. Popups must be allowed for this message to be seen. Log off of the disk controller by clicking Log off.
3 Procedures 3.5 Blade Server Procedures 3.5.1 Upgrade Blade Server Firmware This procedure will provide the steps to upgrade the firmware on the Blade servers. The HP Support Pack for Proliant installer automatically detects the firmware components available on the target server and will only upgrade those components with firmware older than what is on the current ISO.
3 Procedures Note: A maximum of 8 blades should be upgraded concurrently at one time. If the c7000enclosure has more than 8 blades they will need to be upgraded in multiple sessions. 5. OA Web GUI: Connect to USB Drive Once the blades are selected, connect them to the ISO on the USB Drive, by selecting the Connect to usb… item from the DVD menu. 6.
3 Procedures Note: The Refresh button may need to be clicked in order to see the current status of all blades. 7. OA Web GUI: Power Down Blades If needed, reselect the UID checkbox for each blade to be upgraded and then select the Momentary Press option under the Virtual Power menu. When prompted click the OK button to confirm the action. 8. OA Web GUI: Verify Power Down The power down sequence can take several minutes to complete.
3 Procedures Note: The Refresh button may need to be clicked in order to see the current status of all blades. 9. OA Web GUI: Initiate Firmware Upgrade To power the blades back on and begin the automated firmware upgrade process, repeat Steps 7 and 8 this time being sure the Power State indicates On for each selected blade. 10. OA Web GUI: Monitor Firmware Upgrade From this point on each blade will boot into an automated firmware upgrade process that will last between 20 to 25 minutes.
3 Procedures during the firmware upgrade. Use the iLO's integrated remote console or a kvm connection to view the error. If necessary, repeat Steps 4 through 10 for the remaining blades in the enclosure to be upgraded. Proceed to the next step. 11. Remove USB Flash Drive The USB flash drive may now safely be removed from the Active OA module. 12.
3 Procedures 3. Active OA GUI: Verify/update Boot device Order Verify that the Boot order is as follows. If it is not, use the up and down arrows to adjust the order to match the picture below, then click on Apply 4. Active OA GUI: Repeat for the remaining blades Repeat Steps 2 and 3 for the remaining blades. Once done, exit out of the OA GUI. 3.5.
3 Procedures • 3.8.4 Deploy PM&C Guest Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document. 1. PM&C: Log into the PM&C as root using ssh. 2. PM&C: Create xml file In /usr/TKLC/smac/html/public-configs create an xml file with information similar to the following example. Change the Administrator password field only as instructed by the application. PAGE 1463 Procedures 7. PM&C: Remove temporary file On the PM&C remove the configuration file you created. This is done for security reasons, so that no one can reuse the file: # rm –rf /usr/TKLC/smac/html/public-configs/change_ilo_admin_passwd.xml 3.5.4 Accessing the c-Class iLO Virtual Serial Port This procedure describes the steps how to access iLO VSP. Prerequisite: 3.5.3 Configure Blade Server iLO Password for Administrator Accounthas been completed.
3 Procedures Run syscheck to verify that the test is working: # syscheck -v net defaultroute Running modules in class net... OK LOG LOCATION: /var/TKLC/log/ syscheck/fail_log Restart syscheck: # service syscheck restart Repeat for each blade. 3.5.6 Preparing HP Blade System for Extended Power Outage This procedure describes how to properly shutdown the HP blade system for extended period of time such as in the event of shipment from Manufacturing to the customer site.
3 Procedures If the aggregation switches are provided by the customer, request that the customer follow their policies for preparing devices for an extended power outage. 3.5.7 Bringing up HP Blade System After Extended Power Outage This procedure describes the steps how to properly power up the HP blade system. Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document. 1.
3 Procedures You will see following: Navigate to Enclosure Settings and press OK. Navigate to the OA1 Ipv4 and press OK. Navigate again to the OA1 Ipv4 and press OK. On the OA1 Network Mode screen choose static and press OK. On the OA1 IP address screen fill in IP, mask and gateway. Press OK and then press Accept All. Navigate to "OA2 Ipv4" on the Insight display and repeat the above steps to assign the IP parameters of OA2. 3.6.
3 Procedures Note: The enclosure should be provisioned with two Onboard Administrators. Note that the OA in Bay 2 will automatically acquire it’s configuration from the OA in Bay 1 once the configuration is complete. Note: This procedure should be used for initial configuration only. Follow 3.6.8 Replacing Onboard Administrator to learn how to correctly replace one of the Onboard Administrators.
3 Procedures Note: If needed Navigate to Wizards > First Time Setup to get to the screen above. Click on Next to choose enclosure you want to configure. You will see Rack and Enclosure Settings: 3.
3 Procedures Click on Next. 4. OA GUI: Skip Configuration Management You will see Configuration Management. Skip this step. Click Next. 5.
3 Procedures Fill in Rack Name in format xxx_xx. Fill in Enclosure name in format _ Example: Rack Name: 500_03 Enclosure Name: 500_03_03 Note: Enclosure positions are numbered from 1 at the bottom of the rack to 4 at the top. Check Set time using an NTP server item and fill in Primary NTP server (which is recommended to be set to the ). Set Poll interval to 720. Set Time Zone to UTC if customer does not have any specific requirements.
3 Procedures Change Administrator’s password (refer to application documentation) and click onNext. 7. OA GUI: Create pmacadmin and root user On the Local User Accounts screen click on New to add pmacadmin user. You will see User Settings screen. Fill in User Name and Password. Privilege Level set to Administrator. Refer to the application documentation for the password.
3 Procedures Go to the Device List section of the EBIPA Settings Screen (at the top). Fill in the iLO IP, Subnet Mask and Gateway fields for Device Bays 1-16. Do not fill in the iLO IP, subnet Mask or Gateway fields for Device Bays 1A-16A and 1B-16B Note: Bays 1A-16A and 1B-16B are used for double-density blades (f.e. BL2x220c) which are not supported in this release. Click Enabled on each Device Bay 1 through 16 that is in use.
3 Procedures Fill in the EBIPA Address, Subnet Mask and Gateway fields for each Interconnect Bay in use. Click Enable on each Interconnect Bay in use. By clicking Next you will apply those settings. System may restart devices such as interconnect devices or iLOs to apply new addresses. After finishing check the IP addresses to ensure that apply was successful. 9. OA GUI: Skip Directory Groups step To skip Directory Groups step, click Next. 10.
3 Procedures Click on Next. Note: If you change the IP address of the active OA, you will be disconnected. Then you will have to close your browser and sign in again using the new IP address. 12. OA GUI: SNMP Settings Mark Enable SNMP.
3 Procedures Fill in System Location that is equal to Enclosure name you have filled in Step 5. Do not set Read Community and Write Community. Note: This step does not set an SNMP Trap Destination, to do that please see section 3.6.9 Add SNMP trap destination on OA.. Click on Next. 13. OA GUI: Power Management The Power Mode setting on the Power Management screen must be configured for power supply redundancy.
3 Procedures DC-powered Enclosures: For all other settings on the Power Management screen, leave the default settings unchanged. Click on Next. 14. OA GUI: Finish First Time Setup Wizard Click on Finish. Note: If only one OA has been configured, skip the following step. 15.
3 Procedures Check the Enable Link Loss Failover and specify Failover Interval to be 180 seconds. Click Apply. 3.6.3 Configure OA Security This procedure will disable telnet access to OA. Prerequisite: Configure initial OA settings via configuration wizard has been completed. Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document. 1.
3 Procedures Then uncheck the Enable Telnet Click on Apply. 3.6.4 Upgrade or Downgrade OA Firmware This procedure will update the firmware on the OA’s. Prerequisites: • Obtain any customer approval needed for OA firmware updates. This procedure can change the version of firmware installed in one or both OAs.
3 Procedures • 3.8.9 Adding ISO Images to the PM&C Image Repository has been completed using Misc. Firmware CD/ISO. • 3.2.9 Upgrade 3020 Switch IOS Firmware MUST be completed before proceeding with this procedure, if the OA firmware is upgraded and the 3020 switch IOS is NOT upgraded, there could be a loss of connectivity for the blades. Needed material: • HP Misc.
3 Procedures Note: The HPFW_mount_point can be determined by running the following command on the management server: exportfs For example: https://10.240.4.198/TPD/HPFW--872-2488-XXX--HPFW/files/hpoa300.bin Check the Force Downgrade box if present. Click Apply If a confirmation dialog is displayed, click "OK". Note: The upgrade may take up to 25 minutes. 5. OA GUI: Observe OA firmware upgrade progress You should observe the following updates during the upgrade. 6.
3 Procedures 7. OA GUI: Verify the firmware upgrade Login to the OA again. It may take few minutes before the OA is fully functional and accepts the credentials. In the left navigation area, navigate to Enclosure Information > Active Onboard Administrator > Firmware Update Examine the Firmware Version shown in the Firmware Information table. Verify the firmware version information is correct. 8.
3 Procedures Store this file on local disk. For example: Press ctrl+s, choose file name, path, and as type choose text file. f.e. you may choose the following syntax for the configuration file name: _.conf 3. Management server: Backup configuration file Do the following to backup the file on the management server : Under directory /usr/TKLC/smac/etc you can create your own subdirectory structure.
3 Procedures provided, the backup file name indicates that it was created on 10/25/2011 at 10:02:51 am server time. 5. PM&C: Verify the Backup was successful Note: If the background task shows that the backup failed, then the backup did not complete successfully. STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document.
3 Procedures • 3.6.5 Store OA Configuration on Management Server has been performed in the past. • 3.6.1 Configure Initial OA IP has been completed prior to this procedure. If there is any doubt as to whether the aggregation switches are provided by Tekelec or the customer, contact Tekelec Technical Services and ask for assistance. Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document. 1.
3 Procedures A pop up appears after the restore is complete. This will contain logs from the restoration process. Check if there are any errors. 4. OA GUI: Log out Log out from the OA by pressing Sign Out at the top-right corner. 3.6.7 Adding a redundant Onboard Administrator to enclosure This procedure has become obsolete with Platform 5.0. 3.6.8 Replacing Onboard Administrator This procedure describes how to replace OA in an enclosure with Redundant OA.
3 Procedures 2. OA GUI: Record the IP configuration of the Active and Standby OAs. Navigate to Enclosure Information > Active Onboard Administrator > TCP/IP Settings. Record the Active OA's IP Address, Subnet Mask, and Gateway here: Active OA IP Address: Active OA Subnet Mask: Active OA Gateway: Navigate to Enclosure Information > Standby Onboard Administrator TCP/IP Settings.
3 Procedures If the OA you would like to replace is not the active OA for the enclosure, skip to step 5. Otherwise, continue with step 4. 4. OA GUI: Force active OA into standby mode On the left-hand side navigate to Enclosure Information > Enclosure Settings > Active to Standby, then click on the Transition Active to Standby button.
3 Procedures Wait about five minutes , until the application reloads itself and the following page appears: 5. Remove the OA to be replaced If you need to replace the Onboard Administrator from the OA Bay 2 location (right as viewed from rear) , remove it and skip to step 7. If you need to replace the Onboard Administrator from the OA Bay 1 location (left as viewed from rear), remove it and proceed with step 6. 6.
3 Procedures On the Rear View mouse over each OA and verify the that the Status value is OK. If the status of one OA or the other is shown as "Degraded" because of a firmware version mismatch, perform "3.6.4 Upgrade or Downgrade OA Firmware". 11. PM&C CLI: Delete OA SSH keys Log in to the PM&C CLI as the root user. Execute these three commands: # ssh-keygen -R -f ~pmacd/.ssh/known_hosts # ssh-keygen -R -f ~pmacd/.ssh/known_hosts # chown pmacd:pmacd ~pmacd/.
3 Procedures Type the host destination information into the 'Host:' box (indicated by the red arrow in the following figure). Additionally, type the community string to the 'Community String:' box (indicated by the green arrow in the following figure). Finally, click the Add button to the trap destination to the configuration.
3 Procedures The SNMP trap destination has now been added to the configuration and should show up in the list of configured destinations. Click Apply to activate the configuration. The following progress meter may appear. When the progress meter disappears, the configuration has been applied. 3.6.10 Delete SNMP trap destination on OA. This procedure will remove an SNMP trap destination from the Onboard Administrator. 1. Active OA GUI: Login Navigate to the IP address of the active OA.
3 Procedures All configured SNMP trap destinations will be shown in the box in the center of the SNMP Settings page. Select the trap destination that will be removed and click the Remove button. The SNMP trap destination has now been removed from the configuration and will no longer be listed as a configured destination. Click Apply to activate the configuration. The following progress meter will appear.
3 Procedures When the progress meter disappears the configuration has been applied. 3.7 DL360 and DL380 Server Procedures 3.7.1 IPM DL360 or DL380 Server This procedure provides instructions for configuring and IPMing the DL360 or DL380 server. Needed material: • 909-2130-001 Initial Product Manufacture [4] • TPD or TVOE installation media to be used for IPM. Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.
3 Procedures • 3.7.
3 Procedures Username = Password = 3. Determine which iLO steps to take a) If you are upgrading a G6 (iLO 2) server, continue at the next step. b) If you are upgrading a G7/Gen8 (iLO3/iLO4) server, continue at step 12. 4. iLO 2 Web GUI: Select Virtual Media page. Click the Virtual Media tab from the System Summary page. 5. iLO 2 Web GUI: Open the Virtual Media Applet .
3 Procedures 6. iLO 2 Web GUI: Acknowledge Security Warning. If a dialog similar to the one below is presented, click Yes to acknowledge the issue and proceed. If other warning dialogs are presented you may also acknowledge them as well to proceed to the Virtual Media applet. 7. iLO 2 VM Applet: Select the HP Support Pack for Proliant ISO. In the Virtual CD/DVD-ROM Panel, select the Local Image File option and click the Browse button.
3 Procedures 8. iLO 2 VM Applet: Create Virtual Drive Connection. Click the Connect button to create a virtual DVD-ROM connection to the ISO image file. When created the LED Light icon should be green. At this point, DO NOT close the applet but rather go back to the browser window containing the iLO Web GUI. 9. iLO 2 Web GUI: Access the Remote Console Page. At the ILO2 Web GUI, click on the Remote Console tab.
3 Procedures 10. iLO 2 Web GUI: Launch the Remote Console Applet. On the Remote Console page, click on the Remote Console link to launch the console applet. 11. iLO 2 - Java Security Prompt: Acknowledge Security Warning If a dialog similar to the one below is presented, click Yes to acknowledge the issue and proceed. Then skip to step 16. If other warning dialogs are presented you may also acknowledge them as well to proceed to the Java Integrated Remote Console applet. 12.
3 Procedures On the menu to the left navigate to the Remote Console page. Click on the Java Integrated Remote Console to open it. 13. iLO3/iLO4 - Java Security Prompt: Acknowledge Security Warning. If a dialog similar to the one below is presented, click Yes to acknowledge the issue and proceed. If other warning dialogs are presented you may also acknowledge them as well to proceed to the Java Integrated Remote Console applet. 14.
3 Procedures Navigate to the HP Support Pack for Proliant ISO ISO file copied to the workstation from the Copy the ISO images to the workstation procedure. Select the ISO image file and click Open. 15. iLO3/iLO4 - Remote Console: Verify Virtual Image connection. At the bottom of the remote console window you should now see a green highlighted drive icon and "VirtualM" written next to it. 16. Remote Console: Reboot the server.
3 Procedures 17. Remote Console: Perform an unattended firmware upgrade. The server will reboot into the HP Support Pack for Proliant ISO ISO and present the following boot prompt. Press [Enter] to select the Automatic Firmware Update procedure. If no key is pressed in 30 seconds the system will automatically perform an Automatic Firmware Update. 18. Remote Console: Analyze System.
3 Procedures Note: No progress indication is displayed during the system scan and analysis stage. In about 10 minutes, the installation will automatically proceed to the next step. 19. Remote Console: Monitor Installation. Once analysis is complete, the installer will begin to upgrade the eligible firmware components. A progress indicator is displayed at this time, as shown below. Note: If the iLO firmware is to be upgraded, it will be upgraded last.
3 Procedures Refer to the Proliant Server Firmware Errata section to determine if this HP Solutions Firmware Update Pack contains additional firmware errata updates that should be applied to the server at this time. 3.8 PM&C Procedures 3.8.1 Deploying Virtualized PM&C Overview Deployment Procedure Deploying a VM guest in the absence of a PM&C is a bit complicated.
3 Procedures • Determine the NetBackup network on the TVOE management server is to be tagged. If appropriate fill in the value in the table, otherwise the NetBackup network is not tagged. • Determine the bridge name to be used on the TVOE management server for the netbackup network. Fill in the value in the table. • Determine if the NetBackup network is to be configured with jumbo frames.
3 Procedures Variable Value Description Fill in the appropriate value for For non-segregated networks, this site: __________________ the control network may have a VLAN id assigned. In most cases, there is none.
3 Procedures Variable Value Fill in the appropriate value for The IP netmask for the control this site: __________________ network.
3 Procedures Note: The output below is for illustrative purposes only. It shows the control bond configured. # netAdm query --device= Protocol: none On Boot: yes IP Address: Netmask: Bonded Mode: active-backup Enslaving: If the bond has been configured, skip to the next step. Note: The output below is for illustrative purposes only.
3 Procedures Note: The output below is for illustrative purposes only. It shows the management bridge configured on a non-segregated network setup. # netAdm query --device=bond0.2 Protocol: none On Boot: yes IP Address: 10.240.5.2 Netmask: 255.255.255.0 Bridge: Member of bridge management If the device has been configured, skip to the next step. Note: The output below is for illustrative purposes only.
3 Procedures Note: The output below is for illustrative purposes only. It shows the management bridge configured on a non-segregated network setup. # netAdm query --type=Bridge --name=management Bridge Name: management On Boot: yes Protocol: none IP Address: 10.240.4.86 Netmask: 255.255.255.0 Promiscuous: no Hwaddr: 00:24:81:fb:29:52 MTU: Bridge Interface: bond0.2 If the bridge has been configured, skip to the next step. Note: The output below is for illustrative purposes only.
3 Procedures # netAdm set --device= --type=Ethernet --master= --slave=yes --onboot=yes --MTU= Interface updated # netAdm add --type=Bridge --name= --bootproto=none --onboot=yes --MTU= --bridgeInterfaces= --address= --netmask= • Option 2: Create netbackup bridge using an untagged native interf
3 Procedures Note: The output below is for illustrative purposes only. It shows the route on the NetBackup bridge is configured. If the netbackup route is to be a network route, then: # netAdm query --route=net --device= Routes for TABLE: main and DEVICE: netbackup * NETWORK: net GATEWAY: 169.254.253.
3 Procedures Note: It is recommended that you use the 14. TVOE Management Server: Ensure time set correctly. a) Set time based on NTP Server # service ntpd stop # ntpdate ntpserver1 # service ntpd start b) Reboot the server # init 6 15. Execute 3.11.3 Add SNMP trap destination on TPD based Application on the Management Server. 16. If the NetBackup feature is enabled for this system, configure the appropriate NetBackup client on the PM&C TVOE host.
3 Procedures • 3.8.2 Installing TVOE on the Management Server, • 3.8.3 TVOE Network Configuration, and • PM&C Installation Media. 1. TVOE Management Server iLO: Login and launch the integrated remote console Login to iLO in IE using password provided by application: http:// Click in the Remote Console tab and launch the Integrated Remote Console on the server. Click Yes if the Security Alert pops up. 2. TVOE Management Server: Mount the PM&C media to the TVOE Management server.
3 Procedures --controlNM= --managementBridge= --managementIP= --managementNM= --routeGW= --ntpserver= For this example, deploy a PM&C with the netbackup feature. Deploying a PM&C with the NetBackup feature requires the "--netbackupVol" option, which creates a separate netbackup logical volume on the TVOE host of PM&C.
3 Procedures then kill the existing process "kill -9 ". Then execute the "virsh console X" command. Your console session should now run as expected. Login using virsh, and wait until you see the login prompt: virsh # list Id Name State ---------------------------------13 myTPD running 20 pmacdev7 running virsh # console pmacdev7 [Output Removed] Starting ntdMgr: [ OK ] Starting atd: [ OK ] 'TPD Up' notification(s) already sent: [ OK ] upstart: Starting tpdProvd... upstart: tpdProvd started.
3 Procedures Run: # init 6 8. Gather and prepare configuration files that must be resident on the PM&C. These might be required to proceed with the Application installation after the PM&C has been deployed but before it has been initialized. These files are usually located within a given ISO on physical media (USB or CDROM). Note: This is an optional step only required if needed by an Application.
3 Procedures d) Execute the following commands to copy the required files from the TVOE host to the PM&C guest. Wildcards can be used as necessary. 1. If the application is on a physical disk: # scp -R /media/cdrom//* root@:/ 2. If using a USB Drive: # scp -R /mnt/upgrade//* root@:/ e) Remove the application media from the TVOE host: 1.
3 Procedures Note: If the PM&C application Product Release is not as expected, STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document. # appRev Install Time: Fri Sep 28 15:54:04 2012 Product Name: PMAC Product Release: 5.0.0_50.10.0 Part Number ISO: 872-2441-905 Part Number USB: 872-2441-105 Base Distro Product: TPD Base Distro Release: 6.0.0_80.22.0 Base Distro ISO: TPD.install-6.0.0_80.22.0-CentOS6.2-x86_64.iso OS: CentOS 6.2 11.
3 Procedures Navigate to Main Menu > Administration > PM&C Configuration. 2. PM&C GUI: Configure optional features Click on "Feature Configuration" in the navigation pane. The "Features" view allows you to enable/disable PM&C features, and manage the feature's network role. Application documentation will direct these decisions. The following image is for reference only: The "Enabled" checkbox selects the desired features.
3 Procedures When done, click on the "Apply" button. This foreground task will take a few moments, and then refresh the view with an Info or Error notice to verify the action. To discard changes, just navigate away from the view. 3. PM&C GUI: Reconfigure PM&C networks Note: The Network reconfiguration enters a tracked state. After you click on "Reconfigure", you should use a "Cancel" button to abort.
3 Procedures Note: The backup runs as a background task. To check the status of the background task use the PM&C GUI Task Monitor page, or issue the command " pmaccli getBgTasks ". The result should eventually be "PM&C Backup successful" and the background task should indicate "COMPLETE". Note: The "pmacadm backup" command uses a naming convention which includes a date/time stamp in the file name (Example file name: backupPmac_20111025_100251.pef ).
3 Procedures 3. PM&C GUI: Add Cabinet On the Configure Cabinets panel, press the Add Cabinet button 4. PM&C GUI: Enter Cabinet ID Enter the CabinetID and press the Add Cabinet button. 5.
3 Procedures 6. PM&C GUI: Navigate to Configure Enclosures Navigate to Main Menu > Hardware > System Configuration > Configure Enclosures. 7. PM&C GUI: Add Enclosure On the Configure Enclosures panel, press the Add Enclosure button 8. PM&C GUI: Provide Enclosure Details On the Add Enclosure panel, enter the Cabinet ID, Location ID, and two OA IP addresses (the enclosure's active and standby OA). Then click on Add Enclosure.
3 Procedures Note: Location ID is used to uniquely identify an enclosure within a cabinet. It can have a value of 1, 2, 3, or 4. The cabinet ID and location ID will be combined to create a globally unique ID for the enclosure (for example, an enclosure in cabinet 502 at location 1, will have an enclosure ID of 50201). 9. PM&C GUI: Monitor Add Enclosure The Configure Enclosures page is then redisplayed with a new background task entry in the Tasks table.
3 Procedures Open your web browser and enter: https:// Login as the pmacadmin user. 2. PM&C GUI: Navigate to Configure Enclosures Navigate to Main Menu > Hardware > System Configuration > Configure Enclosures. 3. PM&C GUI: Edit Enclosure On the Configure Enclosures panel, select a row from the list of provisioned enclosures and press the Edit Enclosure button 4. PM&C GUI: Confirm Edit Enclosure Press the OK button to proceed to the Edit Enclosure page. 5.
3 Procedures 6. PM&C GUI: Monitor Add Enclosure The Configure Enclosures page is then redisplayed with a new background task entry in the Tasks table. This table can be accessed by pressing the Tasks button located on the toolbar under the Configure Enclosures heading. When the task is complete and successful, its text will change to green, and its Progress column will indicate "100%". 3.8.
3 Procedures • After the image transfer is 100% complete, close the connection > quit Refer to the documentation provided by application for pmacftpusr password. 2. PM&C GUI: Login Open web browser and enter: https:// Login as pmacadmin user. 3. PM&C GUI: Attach the software image to the PM&C guest If in Step 1 the ISO image was transferred directly to the PM&C guest via sftp, skip the rest of this step and continue with step 4.
3 Procedures Navigate to Main Menu > Software > Manage Software Images 5. PM&C GUI:Add image Press the Add Image button . 6. PM&C GUI: Add the ISO image to the PM&C image repository. Select an image to add: • If in Step 1 the image was transferred to PM&C via sftp it will appear in the list as a local file "/var/TKLC/...". • If the image was supplied on a CD or a USB drive, it will appear as a virtual device ("device://…").
3 Procedures 7. PM&C GUI Monitor the Add Image status The Manage Software Images page is then redisplayed with a new background task entry in the table at the bottom of the page: 8. PM&C GUI Wait until the Add Image task finishes When the task is complete, its text changes to green and its Progress column indicates "100%".
3 Procedures 9. PM&C GUI: Detach the image from the PM&C guest If the image was supplied on CD or USB, return to the PM&C guest's "Media" tab used in Step 3, locate the image in the "Attached Media" list, and click its "Detach" button. After a pause, the image will be removed from the "Attached Media" list. This will release the virtual device for future use. Remove the CD or USB device from the Management Server. 3.8.
3 Procedures 3. PM&C GUI: Select Servers Select the servers you want to IPM. If you want to install the same OS on more than one server, you may select multiple servers by individually clicking multiple rows. Selected rows will be highlighted in green. Press the Install OS button. 4. PM&C GUI: Select Image The left side of the screen displays the servers to be affected by the OS installation.
3 Procedures 5. PM&C GUI: Supply Install Arguments (Optional) Install arguments can be supplied by entering them into the text box displayed under the list of bootable images. These arguments will be appended to the kernel line during the IPM process. If no install arguments need to be supplied for the OS being installed, leave the install arguments text box empty. 6. PM&C GUI: Start Install Press the Start Install button. 7. PM&C GUI: Confirm OS Install Press the OK button to proceed with the install. 8.
3 Procedures When the task is complete and successful, its text will change to green and its Progress column will indicate "100%". 3.8.11 Install/Upgrade Applications Using PM&C This procedure provides the steps for performing an application install/upgrade using an image from the PM&C image repository. Prerequisites: • Enclosures containing blade servers or servers containing a TVOE host targeted for application install/upgrade have been configured using the 3.8.
3 Procedures Navigate to Main Menu > Software > Software Inventory. 3. PM&C GUI: Select Servers Select the servers you want to upgrade. If you want to perform an upgrade on more than one server, you may select multiple servers by individually clicking multiple rows. Selected rows will be highlighted in green. Press the Upgrade button.
3 Procedures 5. PM&C GUI: Supply Upgrade Arguments (Optional) Upgrade arguments can be supplied by entering them into the text box displayed under the list of upgrade images. Each upgrade argument must be of the form key=value and supported by the version of TPD that the application being installed/upgraded is based on. Multiple arguments must be separated by spaces or entered on new lines.
3 Procedures When the task is complete and successful its text will change to green and its Progress column will indicate "100%". 9. PM&C GUI: Verify that the installed/upgraded application is fully functional. The application must provide the steps necessary for verifying its functionality. 10. PM&C GUI: Accept or Reject Upgrade (Platform 6.0 Applications Only) If the application you just upgraded or installed is based on a TPD 6.0 release, you must either accept or reject the upgrade.
3 Procedures Log in to iLO in IE using the password provided by application: http:// Click in the Remote Console tab and launch the Integrated Remote Console on the server. Click Yes if the Security Alert pops up. 2. Redundant Management Server TVOE: Mount the PM&C upgrade media from the PM&C server. # mount :/usr/TKLC/smac/html/TPD/ /mnt/upgrade # 3.
3 Procedures On the Manage Backup panel, enter the IP address of the redundant PM&C (redundant_management_server_mgmtVLAN_IP) and click on Update Settings. 9. Primary PM&C Server GUI: Verify update was successful Click on the Task Monitoring link to monitor the Update PM&C Backup Data status. Verify the task completes successfully. 10. Primary PM&C Server GUI: Perform initial backup to the redundant PM&C server Navigate to Main Menu > Administration > PM&C Backup > Perform Backup.
3 Procedures 11. Primary PM&C Server GUI: Verify the backup was successful Click on the Task Monitoring link to monitor the Backup PM&C status. Verify the task completes successfully. Note: This backup copies the existing PM&C backup files and all of the images added to the PM&C image repository from the primary PM&C Server to the redundant PM&C Server. 3.8.13 Configure Management Server SNMP trap target This procedure will configure SNMP settings for the Management Server. Prerequisites: • 3.8.
3 Procedures Click in the Remote Console tab and launch the Integrated Remote Console on the server. Click Yes if the Security Alert pops up. 3. TVOE Management Server iLO: Login with PM&C root credentials Note: On a TVOE host, If you launch the virsh console, i.e.
3 Procedures 3.8.15 Add Rack Mount Server to the PM&C System Inventory This procedure provides instructions to add a rack mount server to the PM&C system inventory. Prerequisite: • 3.8.6 Configure PM&C application has been completed. Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.4 Customer Care Center section of this document. 1. PM&C GUI: Login Open web browser and enter: https:// 2.
3 Procedures Note: The PM&C contains default credentials for the rack mount server management port (not to be confused with OS or Application credentials), however if you know the default credentials will not work then enter the valid credentials for the rack mount server management port. 5. PM&C GUI: Check errors If no error is reported to the user you will see the following: Or you will see an error message: 6.
3 Procedures The RMS inventory page is displayed. Periodically refresh the hardware information using the double arrow to the right of the title "Hardware Information" until the "Discovery state" changes from "Undiscovered" to "Discovered". If "Status" displays an error, contact the Customer Care Center for assistance by referring to the 1.4 Customer Care Center section of this document.
3 Procedures 3.8.16 Edit Rack Mount Server in the PM&C System Inventory This procedure provides instructions to edit a rack mount server in the PM&C system inventory. This option is used to modify the name, cabinet, or credentials of an already provisioned rack mount server. Prerequisite: • 3.8.15 Add Rack Mount Server to the PM&C System Inventory has been completed. Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.
3 Procedures 3. PM&C GUI: Edit RMS On the Configure RMS panel, select one row in the list of rack mount servers and click the Edit RMS button. 4. PM&C GUI: Confirmation A popup window appears asking you to confirm your desire to edit the rack mount server, click OK. 5. PM&C GUI: Edit RMS In the Edit RMS panel, modify the field that needs to be altered. Then click on the Edit RMSbutton.
3 Procedures 6.
3 Procedures 3.8.17 Finding and Adding a Rack Mount Server to the PM&C System Inventory This procedure provides instructions to find and add a rack mount server to the PM&C system inventory. This option is used to locate rack mount servers already running a Tekelec OS or within a specified IP Address range and then add those to the PM&C system inventory. Prerequisites: • 3.8.6 Configure PM&C application has been completed.
3 Procedures 5. PM&C GUI: Monitor Find RMS The Find unprovisioned RMS page is then redisplayed with a new background task entry in the Tasks table. This table can be accessed by pressing the Tasks button located on the toolbar under the Find unprovisioned RMS heading. When the task is complete and successful, its text will change to green, and its Progress column will indicate "100%". 6. PM&C GUI: Found RMS On the Configure RMS panel, click theFound RMS button. 7.
3 Procedures 8. PM&C GUI: Check errors If no error is reported to the user you will see the following: 9. PM&C GUI:Verify RMS discovered Navigate to Main Menu > Hardware > System Inventory > Cabinet xxx > RMS yyy Where xxx is the cabinet id selected when adding RMS (or "unspecified") and yyy is the name of the RMS. The RMS inventory page is displayed.
3 Procedures If "Status" displays an error, contact the Customer Care Center for assistance by referring to the 1.4 Customer Care Center section of this document. 3.8.18 Accepting Upgrades Using PM&C This procedure provides the steps for accepting upgrades via PM&C. Prerequisites: • Enclosures containing blade servers or servers containing a TVOE host targeted for accept upgrade have been configured using the 3.8.7 Add Cabinet and Enclosure to the PM&C system inventory procedure.
3 Procedures 3. PM&C GUI: Select Servers To accept upgrades, the servers must be in the pending accept/reject upgrade state. Servers in the pending accept/reject upgrade state will have Pending Acc/Rej displayed in their App Version column. Note that it may take up to 15 minutes for PM&C to discover and display the Pending Acc/Rej state after an upgrade completes. Select the servers whose upgrades you want to accept.
3 Procedures When the task is complete and successful, its text will change to green, and its Progress column will indicate "100%". 3.8.19 Rejecting Upgrades Using PM&C This procedure provides the steps for rejecting upgrades via PM&C. Prerequisites: • Enclosures containing blade servers or servers containing a TVOE host targeted for reject upgrade have been configured using the 3.8.7 Add Cabinet and Enclosure to the PM&C system inventory procedure.
3 Procedures 3. PM&C GUI: Select Servers To reject upgrades, the servers must be in the pending accept/reject upgrade state. Servers in the pending accept/reject upgrade state will have Pending Acc/Rej displayed in their App Version column. Note that it may take up to 15 minutes for PM&C to discover and display the Pending Acc/Rej state after an upgrade completes. Select the servers whose upgrades you want to reject.
3 Procedures When the task is complete and successful, its text will change to green, and its Progress column will indicate "100%". 3.8.20 Initialize PM&C Application Initialization of the PM&C application can be performed using the PM&C CLI if an initialization profile exists with the desired features. In the case where a PM&C feature needs to be enabled or modified the PM&C GUI is used to initialize the application. This procedure defines the initialization of the PM&C application and network resources.
3 Procedures If the "netbackup" device exists for the PM&C application guest then return to the procedure that invoked this procedure. Otherwise continue with this procedure. 3. PM&C GUI: Edit the PM&C application guest to add the "netbackup" virtual disk. Click "Edit" and enter the following data for the new netbackup virtual disk. • • • • Size (MB): "2048" Host Pool: "vgguests" Host Vol Name: "_netbackup.
3 Procedures Note: In order to configure the PM&C application with the new isoimagesNetBackup virtual disk the PM&C application guest needs to be shut down and restarted. Refer to PM&C 5.0 Incremental Upgrade, 909-2207-01, Appendix F. Shutdown PM&C Guest . Using the virsh utility on TVOE host of PM&C guest, shut down the PM&C guest. Query the list of guests until the PM&C guest is "shut off".
3 Procedures 3.8.23 Initialize PM&C Application using CLI Prerequisites: • PM&C has been deployed and is not initialized or fully configured. Note: The installer must be knowledgeable of the network and application requirements. The final step will configure and restart the network and the PM&C application; network access will be briefly interrupted. Note: If a procedural STEP fails to execute successfully, STOP and contact the Customer Care Center by referring to the 1.
3 Procedures Physical Blade Location: Blade Enclosure: Blade Enclosure Bay: Guest VM Location: Host IP: Guest Name: TPD IP: Rack Mount Server: IP: Name: 4. Perform a system healthcheck on PM&C: # alarmMgr –alarmStatus This command should return no output on a healthy system.
3 Procedures 2. PM&C GUI: Select the appropriate PM&C initialization profile. The "PM&C Initialization" view will be presented to the operator. Select the appropriate profile.
3 Procedures 3. PM&C GUI: Select and enable, appropriate PM&C Features, and if required add new Roles. Note: In this example the Features view was used to create a "NetBackup" role, and the NetBackup Feature was enabled. Enable the appropriate feature and role, and click "Next".
3 Procedures 4. PM&C GUI: Provision the PM&C application Networks. Note: In the example below the NetBackup network was provisioned and added. Provision the appropriate networks and click "Next".
3 Procedures 5. PM&C GUI: Provision the PM&C application Network Roles. Note: In the example below the NetBackup role was provisioned and added. Provision the appropriate network role and click "Next". 6. PM&C GUI: Provision the PM&C application Network Interfaces. Note: In the example below, the NetBackup interface was provisioned and added. Provision the appropriate interface and click "Next".
3 Procedures 7. PM&C GUI:Provision the PM&C application Routes. Note: In the following example the default route and NetBackup routes were provisioned. Provision the appropriate routes and click "Next".
3 Procedures 8. PM&C GUI: Provision the PM&C application DHCP Ranges. Provision the appropriate DHCP ranges.
3 Procedures 9. PM&C GUI: Finish the PM&C application initialization. Verify the PM&C application initialization is correct on the "Configuration Summary" view and click Finish. 10. PM&C GUI: Verify the PM&C application initialization. Navigate to the Background Task Monitoring view and verify the "Initialize PM&C" task was successful. 3.9 Configuring SAN 3.9.1 Configure SAN Storage Using PM&C Application This procedure will configure a SAN storage using the PM&C application.
3 Procedures Configure initial OA via configuration wizard and 3.8.6 Configure PM&C applicationhave been completed. 3.4.3 Configuring Advanced Settings on MSA2012fc Fibre Channel Disk Controllers or 3.4.4 Configuring Advanced Settings on P2000 Fibre Channel Disk Controllers have been completed for given SAN storage type. • 3.3.3 Configure Zones in Brocade Switches has been completed • • • • Note: When a disk fails, the system looks for a dedicated spare first.
3 Procedures From the Storage Configuration drop down menu choose SAN configuration file and press Configure Storage. Note: Concurrent execution of SAN configuration files is supported. Do not run configuration files at the same time if the xml files configure either the same bladeserver or the same MSA storage system, otherwise a failure may occur .
3 Procedures If PM&C is able to successfully parse the XML configuration file, the actual configuration process is executed. If any error is encountered, the processing is aborted, and the state is left as it was at the point of failure. For recovery suggestions, please refer to step 1: Handle failed SAN Configuration. 3.9.2 Remove SAN Volume from Blade Server Without Preserving Existing TPD Installation This procedure describes how to remove volumes from the partially installed SAN.
3 Procedures Repeat for the second switch. 5. Run IPM on the blade servers Run IPM on blade servers following 3.8.10 IPM Servers Using PM&C Application application. Note: A new IP address will be assigned to bond0 of each blade at the end of the IPM process, so the .xml files will need to be updated accordingly. 3.10 Virtualization Procedures 3.10.1 Create guest server using PM&C application This procedure provides the steps for creating a virtualized guest server on a TVOE host, using the PM&C web GUI.
3 Procedures 4. PM&C GUI: Enter guest name Fill in the Name field with something unique to the TVOE host. The name can be identical to a guest on a different host. 5. PM&C GUI: Select the TVOE Host for the new guest. Using the dropdown Host field, select the TVOE host on which to create the guest. 6.
3 Procedures Using the dropdown field to the right, select the initial powerstate for the guest. In this context, Shutdown and Destroy both behave the same, the guest will not be powered on upon creation. 7. PM&C GUI: Edit the vCPU count and Memory size. Using the arrows to the right of the fields, adjust the number of virtual CPUs and the amount of memory (in MBs) to use for the guest. These fields are also manually edittable test fields. PM&C will not prevent over-subscription of these resources. 8.
3 Procedures 10. PM&C GUI: Add extra virtual disks If the application requires extra virtual disks to be specified, repeat this step for each extra disk. Click on the Add button at the top-right corner of the Virtual Disks pane Size (MB): Click on the number to adjust the size via arrow or the keyboard. Host Pool: The default vgguests storage pool is selected. Using the dropdown box, other pools that have been configured on the TVOE can be selected. Host Vol Name: Fill in this value.
3 Procedures 12. PM&C GUI: Create the guest. Verify the guest configuration. Click on the Create button. 13. PM&C GUI: Verify guest creation started. If there was an immediate problem, an alert box will report the error, and the vaules can be corrected and retried. Otherwise, the alert box will confirm the creation of a Background Task. 14. PM&C GUI: Monitor guest create Navigate to Main Menu > Task Monitoring to monitor the progress of the "VirtAction: Create" background task.
3 Procedures When the task is complete, the text will change to green and the Progress column will indicate "100%". 3.10.2 Delete guest server using PM&C application This procedure provides the steps for deleting a virtualized guest server on a TVOE host, using the PM&C web GUI. Prerequisites: • Enclosure containing the host blade server hosting the guest has been configured using 3.8.7 Add Cabinet and Enclosure to the PM&C system inventory.
3 Procedures 3. PM&C GUI: Select TVOE hosting the guest Click on the to the left of the TVOE host that contains the guest server to delete. This will expand the tree to make the guests hosted on the selected TVOE visible. 4. PM&C GUI: Select the guest and delete The left side of this screen shows the guest servers on the TVOE host. Select the desired guest and the guest details will be displayed on the right.
3 Procedures Then press the Delete button. 5. PM&C GUI: Confirm delete Take a moment to double-check that the guest name is correct. There will be no further confirmation and the delete will be final. Click on the OK button to confirm the delete. 6. PM&C GUI: Monitor guest delete Navigate to Main Menu > Task Monitoring to monitor the progress of the "VirtAction: Delete" background task.
3 Procedures When the task is complete, the text will change to green and the Progress column will indicate "100%". 3.10.3 Create guest server from guest archive using PM&C application This procedure provides the steps for creating a virtualized guest server from a guest archive image on a TVOE host, using the PM&C web GUI. Prerequisites: • Enclosure containing the TVOE host blade server to host the guest has been configured using 3.8.7 Add Cabinet and Enclosure to the PM&C system inventory.
3 Procedures 2. PM&C GUI: Navigate to VM Management Navigate to Main Menu > VM Management. 3. PM&C GUI: Click the Create Guest button. On the Virtual Machine Management page, click the Create Guest button. 4.
3 Procedures 5. PM&C GUI: Select the desired profile, and click the Select Profile button Using the drop-down menu, select the desired ISO/Profile (It is possible there will be multiple profiles on an ISO). Verify the details, then select the Select Profile button. 6. PM&C GUI: Enter guest name The profile fills in the default name. If a different name is desired, fill in the "Name" field with something unique to the TVOE host. The name can be identical to a guest on a different host.
3 Procedures 7. PM&C GUI: Select the TVOE Host for the new guest Using the dropdown "Host" field, select the TVOE host on which to create the guest. 8. PM&C GUI: Select the desired initial power state. Using the dropdown field to the right, select the initial powerstate for the guest. In this context, Shutdown and Destroy both behave the same, the guest will not be powered on upon creation. 9. PM&C GUI: Edit the vCPU count and Memory size The profile inserted the profile's vCPUs and Memory settings.
3 Procedures The primary disk is specified by the profile. The disk image at the left shows how the disk will be populated with the archive's image. The only fields that should be modified are the Host Pool, and Host Vol Name columns. Host Pool: The desired storage pool can be selected here. It is possible that the profile did not specify a value for the storage pool. The GUI will not allow you to continue until one is selected.
3 Procedures Guest Dev Name: This is the alias that will be used inside of the TPD instance running on the guest. It will help the application identify the network. Repeat, as needed, for all vNICs 14. PM&C GUI: Create the guest Verify the guest configuration. Click on the Create button. 15. PM&C GUI: Verify guest creation started If there was an immediate problem, an alert box will report the error, and the values can be corrected and retried.
3 Procedures Navigate to Main Menu > Task Monitoring to monitor the progress of the "VirtAction: Create" background task. When the task is complete, the text will change to green and the Progress column will indicate "100%". 3.11 General TPD Based Application Procedures 3.11.1 Backup Procedure for TVOE This procedure will backup system files which can be used at a later time to restore a failed system Note: The backup image is to be stored on a customer provided medium. 1.
3 Procedures Note: If this operation is attempted on a system without a CD-ROM drive, the following message will appear: 909-2209-001 Revision G, February 2014 267
3 Procedures ® 3. TVOE Host: Build the backup ISO image. Select Build ISO file only. The following screen will display: Note: Creating the ISO image may happen so quickly that this screen may only appear for an instant.
3 Procedures After the ISO is created, platcfg will return to the Backup TekServer Menu as shown in step 2. The ISO has now been created and is located in the /var/TKLC/bkp/ directory. An example filename of a backup file that was created is: "hostname1307466752-plat-app-201104171705.iso" 4. TVOE Host: Exit platcfg Select Exit on each menu until platcfg has been exited. The SSH connection to the TVOE server will be terminated. 5.
3 Procedures 3.11.2 Configure NTP on TPD based Application This procedure will configure NTP servers for a server based on TPD. 1. Server: Login as platcfg user Login as platcfg user on the server. The plagcfg main menu will be shown. 2. Server: Navigate to Time Servers configuration page Select the following menu options sequentially: Network Configuration > NTP. The 'Time Servers' page will now be shown, which shows the configured NTP servers and peers. 3. Server: Update NTP information Select Edit.
3 Procedures Update the form to reflect the desired NTP configuration and then select OK. NTP has now been configured on the server. 4. Server: Exit platcfg. Select Exit on each menu until platcfg has been exited. 3.11.3 Add SNMP trap destination on TPD based Application This procedure will add an SNMP trap destination to a server based on TPD. All alarm information will then be sent to the NMS located at the destination. 1. Server: Login as platcfg user Login as platcfg user on the server.
3 Procedures 3. Server: Add the SNMP trap destination Select Edit and then choose Add a New NMS Server. The 'Add an NMS Server' page will be displayed.
3 Procedures Complete the form by entering in all information about the SNMP trap destination. Select OK to finalize the configuration. The 'NMS Server Action Menu' will now be displayed. Select Exit. The following dialogue will then be presented.
3 Procedures Select Yes and then wait a few seconds while the Alarm Routing Service is restarted. At that time the SNMP Configuration Menu will be presented. 4. Server: Exit platcfg Select Exit on each menu until platcfg has been exited. 3.11.4 Delete SNMP trap destination on TPD based Application This procedure will remove an SNMP trap destination on a server. 1. Server: Login as platcfg user Login as platcfg user on the server. The platcfg main menu will be shown. 2.
3 Procedures 3. Server: Remove the SNMP trap destination Select Edit and then choose Delete an Existing NMS Server. The 'NMS Server to Edit' page will be displayed as shown below.
3 Procedures Select the server to remove from the configuration and press ENTER. A confirmation dialouge will appear. Select Yes to confirm the removal of the NMS server. The 'NMS Server Action Menu' will now be displayed. Select Exit. The following dialogue will be presented.
3 Procedures Select Yes and then wait a few seconds while the Alarm Routing Service is restarted. At that time the SNMP Configuration Menu will be presented. 4. Server: Exit platcfg Select Exit on each menu until platcfg has been exited. 3.11.5 Application NetBackup Client Install/Upgrade Procedures NetBackup is a utility that allows for management of backups and recovery of remote systems. The NetBackup suite is for the purpose of supporting Disaster Recovery at the customer site.
3 Procedures • Application server platform installation has been completed. • Site survey has been performed to determine the network requirements for the application server, and interfaces have been configured. • NetBackup server is available to copy, sftp, the appropriate NetBackup Client software to the application server. • Filesystem for Netbackup client software has been created (3.11.
3 Procedures Select Edit, the Host Action Menu will be displayed.
3 Procedures Select "OK", confirm the host alias add, and exit Platform Configuration Utility 4. Application Console: Create a link for the application provided NetBackup client notify scripts to path on application server where NetBackup expects to find them. Note: Link notify scripts from appropriate path on application server for given application.
3 Procedures 2. iLO2 Web UI: The user should be presented the login screen shown below. Login to the GUI using an Administrator account name and password. 3.
3 Procedures 4. iLO 2 Web UI: 1. Select the [Administration] tab on the top navigation bar. 2. Select the [Management] menu item on the left navigation bar to display the SNMP Settings page. 5.
3 Procedures The user should be presented the SNMP/Insight Manager Settings page. 1. Select option [Disabled] for each of the 3 SNMP settings as shown to the right 2. Click [Apply Settings] to save the change. The web page will refresh but no specific indication will be given that settings have been saved. 6. iLO 2 Web UI: To verify the setting change navigate away from the SNMP/Insight Manager Settings page and then go back to it to verify the SNMP settings as shown on the right. 1.
3 Procedures 7. Complete for remaining iLO2 devices Repeat this procedure all remaining iLO 2 devices on network. 3.11.7 Changing SNMP Configuration Settings for iLO 3 and iLO4 This procedure provides instructions to change the default SNMP settings for the HP ProLiant iLO 3 devices. Perform this procedure for every iLO 3 device on the network. For instance, for every HP ProLiant G7 Blade and Rack Mount server. 1. From Workstation: Launch Internet Explorer 7.
3 Procedures 2. iLO 3/iLO 4 Web UI: The user should be presented the login screen shown below. Login to the GUI using an Administrator account name and password. 3. iLO 3/iLO 4 Web UI: The user should be presented the iLO 3/iLO 4 Overview page as shown below. 4. iLO 3/iLO 4 Web UI: 1. Expand the [Administration] menu item in the left hand navigation pane. 2. Select the [Management] sub-menu item to display the Management configuration page.
3 Procedures 5. iLO 3/iLO 4 Web UI: The user should be presented the Management configuration page as shown on the right. 1. Select setting [Disabled] for each of the 3 SNMP Alerts options as shown to the right. 2. Click [Apply] to save the change. On the iLO 3 the web page will refresh but no specific indication will be given that settings have been saved.
3 Procedures 6. iLO 3/iLO 4 Web UI: To verify the setting changes navigate away from the Management configuration page and then go page back to it to verify the SNMP settings as shown on the right. 1. Click [Sign Out] link in upper right corner of page to log out of the iLO Web UI.
3 Procedures 7. Complete for remaining iLO3/iLO 4 devices Repeat this procedure all remaining iLO 3/iLO 4 devices on network. 3.11.8 Netbackup Client Install/Upgrade with nbAutoInstall Executing this procedure will enable TPD to automatically detect when a Netbackup Client is installed and then complete TPD related tasks that are needed for effective Netbackup Client operation.
3 Procedures 2. Enable nbAutoInstall: Execute the following command: # /usr/TKLC/plat/bin/nbAutoInstall –-enable The server will now periodically check to see if a new version of Netbackup Client has been installed and will perform necessary TPD configuration accordingly. At any time, the customer may now push and install a new version of Netbackup Client. 3. Return to calling procedure if applicable. 3.11.
3 Procedures ---------------------------------13 myTPD running 20 applicationGuestName running virsh # console applicationGuestName [Output Removed] Starting ntdMgr: [ OK ] Starting atd: [ OK ] 'TPD Up' notification(s) already sent: [ OK ] upstart: Starting tpdProvd... upstart: tpdProvd started. CentOS release 6.2 (Final) Kernel 2.6.32-220.17.1.el6prerel6.0.0_80.14.0.x86_64 on an x86_64 applicationGuestName login: 3.
3 Procedures Select Yes to initialize the server and enable the NetBackup client software push. 5. Application Console Enter NetBackup password and select OK. 6. If the version of Netbackup is greater than 7.5.0.0, follow the Tekelec provided procedure for the version of NetBackup that is being pushed. 7. Application Console: Verify NetBackup Client software push is enabled.
3 Procedures Navigate to NetBackup Configuration > Verify NetBackup Client Push Verify list entries indicate "OK" for NetBackup client software environment. Select "Exit" to return to NetBackup Configuration menu. 8. NetBackup server: Push appropriate NetBackup Client software to application server Note: The NetBackup server is not an application asset. Access to the NetBackup server, and location path of the NetBackup client software is under the control of the customer.
3 Procedures Note: The input below is only used as an example. # cd /usr/openv/netbackup/client/Linux/6.5 Execute the sftp_to client NetBackup utility using the application IP address and application netbackup user; # ./sftp_to_client 10.240.17.101 netbackup Connecting to 10.240.17.101... The authenticity of host '10.240.17.101 (10.240.17.101)' can't be established. RSA key fingerprint is 9a:e6:fc:55:16:3b:94:b2:7d:9f:30:b2:3c:e6:65:a9.
3 Procedures Navigate to NetBackup Configuration > Verify NetBackup Client Installation. Verify list entries indicate "OK" for NetBackup Client software installation. Select "Exit" to return to NetBackup Configuration menu. 11. Application Console: Disable NetBackup Client software transfer to the application server. Navigate to NetBackup Configuration > Remove File Transfer User Select "Yes" to remove the NetBackup file transfer user from the application server.
3 Procedures 12. Application Console: Verify that the server has been added to the /usr/openv/netbackup/bp.conf file cat /usr/openv/netbackup/bp.conf CLIENT_NAME = 10.240.34.10 SERVER = NB71server 13. Application server iLO: Exit platform configuration utility (platcfg) 14. Return to calling procedure if applicable. 3.11.10 Create LV and Filesystem for Netbackup Client Software This procedure will carve out storage for the Netbackup Client to reside on.
3 Procedures 1. Server: Login as root user. 2. Server: Stop the netbackup services using the following two commands: # service netbackup stop # service vxpbx_exchanged stop 3. Server: Bind mount /usr/openv to a temporary mount point # mkdir /tmp/openv # mount --bind /usr/openv /tmp/openv 4. Server: Follow 3.11.10 Create LV and Filesystem for Netbackup Client Software to create the LV and filesystem. 5. Server: Move all contents of /tmp/openv to /usr/openv # mv /tmp/openv/* /usr/openv 6.
3 Procedures Note: The config files must start with "NB" and must have a suffix of ".conf". The server is now capable of installing the corresponding NetBackup Client. The server is now capable of installing the corresponding Netbackup Client. 2. Server: Create NetBackup Client config file script. Create the Netbackup Client config script file on the server using the contents that were previously determined. The config script file should be placed in the /usr/TKLC/plat/etc/netbackup/scripts directory.
3 Procedures c) Start the VM Guest by setting the Current Power State back to On and clicking the "Change to..." button. d) When the VM Guest's power state indication shows "Running", proceed to the next VM Guest on this Host. 3.12.2 TVOE Netbackup Client Configuration This procedure will setup and install Netbackup Client on a TVOE host. Note: Once the NetBackup Client is installed on TVOE, the NetBackup Master should be configured to backup the following files from the TVOE host: • /var/TKLC/bkp/*.
Appendix A Appendix A Using WinSCP Topics: • A.1 Using WinSCP.....
Appendix A Using WinSCP A.1 Using WinSCP The following is an example of how to copy a file from the management server to your PC desktop 1. Download the WinSCP Application Downlaod the WinSCP application: http://winscp.net/eng/download.php 2. Connect to the management server After starting this application, navigate to Session and enter: into the Host name, field, root into the User name field, and into the Password field. Click Login. 3.
Appendix A Using WinSCP 4. Close the WinSCP application Then close application by pressing F10 and confirm to terminate session by pressing OK.
Appendix B Appendix B P2000 MSA USB Driver Installation Topics: • B.1 P2000 MSA USB Driver Installation.....
Appendix B P2000 MSA USB Driver Installation B.1 P2000 MSA USB Driver Installation The P2000 USB Driver allows Microsoft Windows to recognize the USB Port on HP StorageWorks P2000 G3 MSA Controllers. This appendix describes how to install the driver on your laptop. Prerequisite: 3.8.9 Adding ISO Images to the PM&C Image Repository has been completed using Misc. Firmware DVD. Note: If you are unable to detect the P2000 array after installing the USB driver, power cycle the P2000 array once.
Appendix B P2000 MSA USB Driver Installation Click Install. In the next window, click I agree to proceed with the installatioin 4. Microsoft Windows Laptop: Select installation directory Then use the Browse button to select the folder where to install Click Install 5. Microsoft Windows Laptop: Verify the installation The success confirmation window concludes the installation.
Appendix B P2000 MSA USB Driver Installation 909-2209-001 Revision G, February 2014 305
Appendix C Appendix C Determining which Onboard Administrator is Active Topics: • C.1 Determining Which Onboard Administrator is Active.....
Appendix C Determining which Onboard Administrator is Active C.1 Determining Which Onboard Administrator is Active This appendix describes how to determine which Onboard Administrator is active in an enclosure with two OAs. Prerequisite: Configure initial OA settings via configuration wizard has been completed.
Appendix D Appendix D Accessing Tekelec Customer Support Site Topics: • D.1 Accessing Tekelec’s Customer Support Site.....
Appendix D Accessing Tekelec Customer Support Site D.1 Accessing Tekelec’s Customer Support Site Access to Tekelec's Customer Support site is restricted to current Tekelec customers only. This section describes how to log into the Tekelec Customer Support site and locate a document. Viewing the document requires Adobe Acrobat Reader, which can be downloaded at www.adobe.com. 1. Log into the Tekelec Customer Support site. Note: If you have not registered for this new site, click the Register Here link.
Appendix E Appendix E Disabling TFTP Topics: • E.1 Turning off TFTP.....
Appendix E Disabling TFTP E.1 Turning off TFTP 1. Turn off the service daemon. # chkconfig tftp off 2. Kill the existing process if it is still running: # ps -ef | grep tftp root 10076 root 21232 20520 # kill -9 0 12:53 ? 0 12:53 pts/0 00:00:00 in.tftpd -s 00:00:00 grep tftp 3. Reload xinetd.
