Forum Discussion

Len_53802's avatar
Len_53802
Icon for Nimbostratus rankNimbostratus
Jan 29, 2010

LocalLBPoolMember.get_session_enabled_state exception

I cannot seem to locate any information on the exception being returned from the follwing call. I would appreciate it if someone could point me in the right direction. 

    
    LocalLBPoolMemberMemberSessionState[][] session_states =    
                m_interfaces.LocalLBPoolMember.get_session_enabled_state(new string[] { "POOL-BO" });

System.Web.Services.Protocols.SoapHeaderException: Exception caught in LocalLB::urn:iControl:LocalLB/PoolMember::get_session_enabled_state()

Exception: Common.OperationFailed

primary_error_code : 16908394 (0x0102006A)

secondary_error_code : 0

error_string : 0102006a:3: IP Address one is invalid, must be a route-domain address.

I assume the pool I'm using shouldn't have any issues because the following call returns all the members of the pool just fine. 

    
    CommonIPPortDefinition[][] members = m_interfaces.LocalLBPool.get_member(new string[] { "POOL-BO" });

dev
devops
iControl

3 Replies

Sort By
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Feb 02, 2010
    It looks to me like you are doing everything correctly. The error indicates that you have route domains configured. Is this the case? I'm checking with the dev team as to a possible reason for this error but it will likely end up requiring you to issue a ticket with product support as this is looking like a bug with the implementation of that method with your given configuration.

     

     

    I'll keep you posted with what I find from the dev team.

     

     

    -Joe

     

  • Len_53802's avatar
    Len_53802
    Icon for Nimbostratus rankNimbostratus
    Feb 03, 2010
    We do have route domains configured and I did open a ticket for this. It would appear that iControl for 10.0.1 doesn't handle this properly and that an update to 10.1 should resolve the issue.
  • Michael_Voight_'s avatar
    Michael_Voight_
    Historic F5 Account
    Mar 31, 2010
    Was a case opened for the message? I have a similar issue with an EM connecting to an LTM in 10.0.1.

     

    I suspect it might be related to a pool member not being on the same subnet as an LTM self IP and not being in a route domain

     

    pool scpc-pool {

     

    members {

     

    192.168.217.58:7080 {}

     

    192.168.217.59:7080 {}

     

    }

     

    }