IBM Director 5.10 Configuration Manager Editor

1. IBM Director 5.10Configuration Manager Editor James Tims Systems Management Software Development

2. Configuration Manager Editor - What is it? A replacement for the Deployment Wizard Two identical applications that allows you to configure either BladeCenters or Servers containing a Service Processor BladeCenter Configuration Manager Server Configuration Manager

3. Configuration Manager Editor - Features Uses a profile based approach to configuration Provides individual Components to configure specific hardware Allows selection of Components to be included in a Profile Allows you to enter data into each Component Allows you to save the Profile as an executable task Allows you to save the Profile as XML Supports our CLI interface Supports Detect & Deploy

4. Profile - Defined A collection of Components that can be executed as a Director task

5. Profile as a Director Task This screen shows a profile TestP saved as a Director task

6. Component (Plug-in) - Defined A component is a small application written by IBM or by a third party that performs one specific hardware configuration task

7. Launching Configuration Manager Editor BladeCenter Configuration Manager • Double click the task • Drag and drop on a target BladeCenter • Right click on a Profile and select Edit Server Configuration Manager • As above – except drag and drop on server with supported service processor

8. Launching The Task

9. Getting Started There are three ways to Start working with Profiles Create a new profile Open an existing profile Import an XML file representing a profile

10. Create A New Profile Step One: Select a profile type

11. Select Components Select the components you wish to include in the profile

12. Profile Tree – Showing Components A tree is built representing the profile

13. Editor – Component Screens Selecting a component shows its screen

14. Editor – File Menu

15. Editor Actions Menu

16. Setting Detect & Deploy – Chassis level Detect & Deploy can be set at two levels

17. Setting Detect & Deploy – Component level Detect & Deploy can be set at two levels

18. Component Functions Component properties

19. Component Properties Modifying these properties change the location of the Component In the Profile

20. Export To XML

21. IBM Director 5.10Configuration Manager CLI Matthew Edmonds Systems Management Software Development

22. Configuration Manager CLI commands mkcmprof – creates Configuration Manager profiles from XML files rmcmprof – deletes Configuration Manager profiles lscmcfg – lists configuration information… either the current configuration of a device if targeted on a managed object, or the configuration data stored in a profile if targeted on a profile task.

23. mkcmprof usage dircli mkcmprof [-h | -? | --help] [-L language] dircli mkcmprof [-L language] [-v] -x xmlfile_list

24. rmcmprof usage dircli rmcmprof [-h | -? | --help] [-L language] dircli rmcmprof [-L language] [-v] -T task_list

25. lscmcfg usage dircli lscmcfg [-h | -? | --help] [-L language] dircli lscmcfg [-L language] [-v] [-d delimiter] -T task_list dircli lscmcfg [-L language] [-v] [-d delimiter] [-t objectType] {-a | -f file | -N group_list | -n object_list | -w selectString} -x xmlfile_list

26. IBM Director 5.10Configuration Manager Components Chet Patel Systems Management Software Development

27. Configuration Manager Components • IP Address Pool • Switch Module Protocol Configuration • Switch Module VLAN Configuration • Management Module Login Profile • Management Module Network Configuration • Remote Deployment Manager Configuration • Service Processor Login Profile • Service Processor Network Configuration

28. IP Address Pool • configure a pool of static IP addresses • other components can be assign these IP Addresses to their respective hardware configurations • gateway and IP addresses should all be on the same subnet • can specify single or range of IP addresses

29. IP Address Pool

30. Switch Module Protocol Configuration • configure the login information and network protocols of the switch • some switch modules (depending on the vendor) allow new user accounts • allows the user to reset the login information to factory defaults • IP address for the switch can be obtained from the IP Address Pool • Configurable Network protocols: HTTP, Telnet and SNMPv1 • SNMPv1 agent configuration requires a community name - IP addresses for SNMP traps are optional • HTTP, Telnet and External Ports can be enabled or disabled

31. Switch Module Protocol Configuration

32. Switch Module VLAN Configuration • configure VLAN’s (Virtual Local Area Networks) for a switch module • authentication information is required. • VLAN Configuration - define the name, id, interface number, type and status of the VLAN • Egress Configuration - associate a port to a VLAN - select an egress state for the port (no egress, tagged and untagged). • VLAN Port Configuration - associate a port to a VLAN ID - select the frame types for the port (accept all, accept tagged, accept none, etc.) - GVRP when enabled, dynamically adds VLANs to port egress lists across a domain - Ingress filtering mechanism discards any frame whose VLAN classification is not on the egress list of the port

33. Switch Module VLAN Configuration

34. Management Module Login Profile • configure account information for the MM (management module) • create new user accounts with supervisor or read-only access

35. Management Module Login Profile

36. Management Module Network Configuration • configure the network protocols of the MM (management module) • configure DHCP and SNMP for your management module • DHCP - enabled or disabled - if DHCP fails, try static configuration • A static IP address for the MM can be obtained via the IP Address Pool (this option is available when DHCP is disabled or set to “If DHCP fails, try static configuration) • SNMPv1 agent configuration (community name is required) • SNMPv3 agent configuration - User ID, profile name are required fields - Authentication protocols configuration (MD5, SHA) - Privacy protocols configuration (DES) • SNMP Traps, contact and location are optional

37. Management Module Network Configuration

38. Remote Deployment Manager Configuration • deploy applications on individual blades in a BladeCenter chassis • RDM (Remote Deployment Manager) must be installed on the server (RDM 4.20 supports Director 5.10) • RDM tasks must be defined by the user • select a blade and an RDM task for deployment

39. Remote Deployment Manager Configuration

40. Service Processor Login Profile • configure account information for the SP (service processor) • create new user accounts with supervisor or read-only access

41. Service Processor Login Profile

42. Service Processor Network Configuration • configure the network protocols of the SP (service processor) • configure DHCP and SNMP for your SP • DHCP - enabled or disabled - if DHCP fails, try static configuration • A static IP address for the SP can be obtained via the IP Address Pool (this option is available when DHCP is disabled or set to “If DHCP fails, try static configuration) • SNMPv1 agent configuration (community name is required) • SNMP traps are optional • SNMP contact and location are optional

43. Service Processor Network Configuration

44. IBM Director 5.10Configuration Manager Profile Execution, Events & Trouble Shooting Bahram Sanaei Systems Management Software Development

45. Agenda Topics to be covered are: • Applies Profiles • Profile Execution Result • Detect and Deploy • Event Handling • Trouble Shooting

46. Applies Profiles • After you have created a profile, you can either: • run it in Editor window by selecting OptionRun • launch it later by dragging the profile onto a Blade center chassis or Server Processor, or • Through the CLI command • use the preexisting Director CLI “lstask” command to get profile task information such as task object id or task string id • use the preexisting Director CLI “runtask” command to execute a profile • The profile can be execute immediately or it can be scheduled to execute later.

47. Applies Profiles (Dragging the profile onto a chassis )

48. Profile Execution Result • Various failure / success states associated with individual profile execution.

49. Profile Execution Result (Execution History)

50. Understanding Detect and Deploy • Detect and Deploy has a different meaning depending on whether it applies to a BladeCenter chassis, Server chassis, blades or switches • BladeCenter Chassis • A director server can have one Detect and Deploy profile for chasses. If you have defined a profile as the Detect and Deploy profile for chasses, it will be applied whenever a new chassis is added to the server. • Server Chassis • A director server can have one Detect and Deploy profile for server processors. If you have defined a profile as the Detect and Deploy profile for server processors, it will be applied whenever a new server processor is added to the server. • Blades • Each chassis can have a different Detect and Deploy profile for each blade slot, and is applied whenever a blade is inserted and it can not boot from the hard drive. (e.g. If a new unbootable blade is inserted into slot 11 on chassis 3, deploy RHES 3 on it) • Switches • Each chassis can have a different Detect and Deploy profile for each switch type. (e.g. If a Cisco switch is inserted into chassis 3, apply this profile to it)