Oct 29
    2010

    ASA 6.0: CMM connection properties

    Alex Garcia
    [Subscriber Members]
    Hi,

    Does anyone know how to setup ASA 6.0 to connect to a CMM 6.0 to create users? I've created a connection but I get the message inappropriate authentication.

    Alex
    Paul Kahn
    [Soros Fund Management, LLC]
    Which login are you using?
    Alex Garcia
    [Subscriber Members]
    Got it working!!

    However to set it up is not documented.

    First you need to setup the computer where ASA is installed as a trusted server within CMM.
    Then you need to create the connection between ASA and CMM trhrough port 636.
    The credentials to use, are the ones created within the trusted server in CMM
    richard lunn
    [Subscriber Members]
    Hi,

    I've been trying to get this working but not had any joy - which field of the trusted server page did you use as the login name for ASA?
    Nathan Loughlin
    [Subscriber Members]
    Can you post screen shots of your trusted server page as I have tried this but to no avail!

    Thanks
    Alan Scott
    [Fluor Corporation]
    Anyone get this working yet? Trying to import subscribers in ASA.
    richard lunn
    [Subscriber Members]
    Yes I did get this working as per aha's instructions above.
    Add your ASA ip as a trusted host and set up a user name and password which will be used when setting up the ASA connection.
    The key part for me was getting the ASA connection set up correctly - there is a option when setting up a new messaging system that allows you to specify that it is "CMM" you are connecting to. This configures the connection as an LDAP one using port 636. None of the default LDAP settings need to be changed.
    Once setup the connection just allows an import/ export - you dont get the traditional SAT style window like we used to on previous versions, but at least you can bulk add/modify.
    Bill Rogers
    [Subscriber Members]
    We have been in the process of installing 12 systems with hundreds of subscribers per location. We unfortunately did it line item by line item but I think I found the problem as I was able to get it to work today. The trusted server should be a PC ON the customer's network. At least for me, VPN would not work for our set up. We have a PC that we can RDC into for ASA. I set it up as the trusted server and the export worked fine. I would imagine the same would go for Provision but ASA should work fine for the three functions available to you: import, export, find and replace.

    Good luck!
    Alan Scott
    [Fluor Corporation]
    Yes I did get this working as per aha's instructions above.
    Add your ASA ip as a trusted host and set up a user name and password which will be used when setting up the ASA connection.
    The key part for me was getting the ASA connection set up correctly - there is a option when setting up a new messaging system that allows you to specify that it is "CMM" you are connecting to. This configures the connection as an LDAP one using port 636. None of the default LDAP settings need to be changed.
    Once setup the connection just allows an import/ export - you dont get the traditional SAT style window like we used to on previous versions, but at least you can bulk add/modify.

    THANK YOU!!! This worked. I was missing the check box in ASA to make this CMM system with LDAP. I have to say I was doubting the LDAP port 636 as even being possible as I do not see it as an allowed port under server access in the GUI.

    I think I will add one more step. I noticed that in ASA version 5.2 there is no option for selecting "CMM System with LDAP" but there is in ASA 6.0

    All Times America/New_York


    Copyright © '.date("Y").'The International Avaya User Group. All Rights Reserved

    All material, files, logos and tradarks within this site are properties of their respective organizations.


    Terms of Service - Privacy Policy - Contact