Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
4 replies Latest Post - ‏2013-08-01T14:48:41Z by gcorneau
marknolan
marknolan
8 Posts
ACCEPTED ANSWER

Pinned topic smcli command to remove individual protocols?

‏2013-07-24T09:32:55Z |

Hi,

I was wondering if it is possible to remove a particular protocol from a system using the smcli command?

I have numerous servers that I would like to edit on the command line and remove CIM and CAS protocols and doing it through the GUI is a pain. I have spent ages looking for a solution to this, but have been unsuccessful so far.

i.e.
 

smcli lssys -l -i  %%.%%.%%.%%

.

.

ComputerName: null
BuildNumber: null

Protocols: { 'CIM', 'SSH', 'CAS'} <----- Remove CAS and CIM to leave the SSH protocol i.e.      Protocols: { 'SSH'}

URL: null
ManagementSoftware: { 'IBM-IBM Director Core Services-v6.3.3' }

 

 

Thanks,

Mark

Updated on 2013-07-24T09:33:41Z at 2013-07-24T09:33:41Z by marknolan
  • --Craig
    --Craig
    16 Posts
    ACCEPTED ANSWER

    Re: smcli command to remove individual protocols?

    ‏2013-07-25T20:38:16Z  in response to marknolan

    I'm not sure of the motivations for removing the CIM and CAS RSAPs, but most likely it will not accomplish what you are wanting to do.  CAS is the highest-order protocol and the one you generally want to be using.  Even if you did remove those protocols, any time the Agent is restarted, or you performed any type of discovery on the Server that included an Agent Manager discovery, the RSAPs would reappear.

     

    Perhaps if you provided details on why you want to remove the CIM and CAS protocols, I could provide a better reply.

    • marknolan
      marknolan
      8 Posts
      ACCEPTED ANSWER

      Re: smcli command to remove individual protocols?

      ‏2013-07-30T07:49:28Z  in response to --Craig

      Hi Craig,

      Thanks very much for the reply. Sorry for my late reply, but I've been out of the office.

      We have a mix of Wintel, AIX and ESXi servers. The intention is to use Systems Director to monitor the hardware and BMC Patrol to monitor all other aspects, such as processes, disk space, CPU etc.

      I thought that the best way for this would be just to use the SSH protocol to achieve this.

      Also, when I have discovered the CAS and CIM protocols on an AIX system, I have never been able to get the access to work. SSH always works, but the other 2 protocols just say no access.

      Thanks for any pointers or advice...

      Cheers,

      Mark

      Updated on 2013-07-30T07:50:05Z at 2013-07-30T07:50:05Z by marknolan
      • marknolan
        marknolan
        8 Posts
        ACCEPTED ANSWER

        Re: smcli command to remove individual protocols?

        ‏2013-08-01T12:26:01Z  in response to marknolan

        Has anyone any comments on this?

      • gcorneau
        gcorneau
        234 Posts
        ACCEPTED ANSWER

        Re: smcli command to remove individual protocols?

        ‏2013-08-01T14:48:41Z  in response to marknolan

        The easiest way to clear up other protocols on AIX operating system endpoints is:

        1. Remove the OS representation from IBM Systems Director
        2. On that AIX endpoint, you need to either shutdown the Common Agent Services or remove the Director Common Agent altogether.
          1. stopping the CAS (and underlying Platform Agent pieces) involves:
            stopsrc -s cas_agent
            stopsrc -s platform_agent
            stopsrc -s cimsys
            slp_srvreg -k

            Now this is only temporary, the daemons will start again upon a system reboot.
          2. Removing the Common Agent requires
            Stopping the agent processes as above
            Use SMIT or commandline to uninstall DirectorCommonAgent, DirectorPlatformAgent
        3. Once you're no longer running the CAS services on the AIX endpoint, re-discover and it should only pick
          up the SSH protocol

        Another option would be to use a customized discovery method that only looks for the SSH protocol.

        FYI, most AIX (Power Systems) hardware monitoring comes out-of-band via the Hardware Management Console, if the Power Systems server is managed by an HMC.  If the server isn't managed by an HMC or IVM, then you'll want the Common Agent for hardware monitoring.

        There are many reasons for inability to get CAS protocol access: duplicate keys, previously managed CAS security keys, firewalls blocking required ports, etc.  If you have a support contract, IBM support can help you figure this out.