Posted by Ms. Marj Bernhardt on 11 February 2009 at 15:53
The title to section 9.4 should be
Example of an Event Automation Plan (singular, please)
10.1 Paragraph 1 should be: Update Manager (capitalization)
10.1.1 should be: ensure that a check for updates (cap again)
10.15 instead of that run-on sentence how about:
Scheduling updates is achieved by running any of the Update Manager Wizards. After the creation of the task, you will be prompted to run the update now or schedule the task to run a a later date.
Posted by David Watts on 12 February 2009 at 5:32
Thanks for the feedback Marj. I'll make those changes.
Posted by Mr. Javier Ferrero on 17 February 2009 at 12:48
Please clarify where to install the SMI-S provider to manage a DS4000 storage, a note says "not to install in the same server as the IBM Director Server", where should it be installed??
Also, It doesnt explain the differences between a SMI-S Provider and a SMI-S Agent.
Another thing, please add more information on how to install an agent on ESX with or without the wizard.
Posted by Shripad Nadgowda on 19 February 2009 at 5:30
Hi Javier,1) Its is recommended that you should have separate dedicated machine to host SMI-S provider, or machine which won’t conflict with services listening on 5988/5989 ports.2) SMI-S provider and agent are typically a part of provider installation, when you install provider for DS4000 (LSI provider), SMI-S agent also gets started3) Installation of provider on Linux/AIX through command line without the wizard is added to the book content, you could see that in the published version
Posted by Mr. Damian Gerow on 15 April 2009 at 10:54
I've just finished reading the book (phew!), and there are a couple of possible mistakes:
1) At the tail end of 1.2.11, there is a reference to a previous mention of the integrated Management Module (iMM). However, I can find only one other reference to the iMM, in 2.5.11.
2) In 2.5.3, PostgreSQL is listed as a supported database for Linux systems, but all other documentation I've found states that PgSQL is no longer supported in 6.1.
Posted by Mr. Damian Gerow on 15 April 2009 at 10:57
Additionally, the Agent Manager holds a singular importance. Can two (or more) Agent Managers replicate to each other? What happens if you lose it? A note about this, even just marking the importance of regular backups, would be nice, if replication or an HA-style setup is not (currently) possible.
Posted by David Feisthammel on 16 April 2009 at 14:10
Thanks for your input, Damian. We will add a brief description of the new iMM. You are correct about support for PostgreSQL, which was withdrawn rather late in the game. We will remove that bullet from section 2.5.3.
Posted by David Feisthammel on 16 April 2009 at 14:11
Damian, regarding the Agent Manager, there is no provision for performing a backup, but this shouldn't cause a serious problem. The AM is contacted only initially by the Common Agent, and by the Server only once during the Request Access process for a given Agent. According to our developers, if the AM were to go away completely, you wouldn't notice until you tried to gain access to a new Agent or in a year after installation, once the original security certificates start to expire.
Posted by Mr. Damian Gerow on 20 April 2009 at 8:51
Would filesystem backups not suffice?
Having to run two Director instances, or re-register all agents against the new AM, is less than ideal. The latter being much more appealing than the former.
Cut off due to required shortness from before: elsewise, the redbook was *immensely* helpful, and covered everything I needed to know.
Posted by Mr. Stefan Verbist on 9 October 2009 at 4:59
Any update expected on BOFM integration with 6.1 ?
Posted by David Watts on 10 October 2009 at 8:05
Hi Stefan, Plans haven't been discussed yet, so I'm not sure what the plans are to update this book in 2010. What did you have in mind? Are there other updates you'd like to see in the book?
Posted by Timothy Gilson on 9 December 2009 at 8:49
So our HMCs listen for SSH on standard port 22 but our LPARs use non-standard port 670 for SSH. It doesn't look like we can deploy and run a working IBM Director - nor can anyone else who runs SSH on a non-standard port.
Unless I am overlooking something .....
Posted by Mr. Alfredo Cubas on 13 July 2010 at 5:52
In section 2.5.2 LDAP support /LDAP considerations in top of page 75, you write down a note about what kind of user authentication to use for Systems Director. The note says :"Note: IBM Systems Director can authenticate users either via the local operating system (including directory authentication like Active Directory or Network Information Service) or via LDAP but not both at the same time."
Network Information Service (NIS) is support in IBM Systems Director server on AIX ?
Posted by David Feisthammel on 26 July 2010 at 10:25
Mr. Cubas, AIX supports local files (i.e. /etc/passwd) and NIS authentication. IBM Systems Director supports the local OS authentication methods in AIX.
IBM Systems Director does not itself directly utilize NIS authentication like it does with LDAP (i.e. talking directly to the NIS/LDAP server). It goes through the AIX OS authentication, which itself may be configured for NIS.