AD ACE Script

Hi,
Powershell formatting... I have an incredible headache.  Anyways, what I'm trying to do seems easy enough, but I've just spent hours on trying to format it correctly.
We have a ton of mail enabled groups that are broken because of Exchange 2010 now (thanks for that) because our dept. used ACLs/ACEs with the Write Members property.  That worked fine on Exchange 2003 & Outlook, but no more.
I now have to parse our AD, find any and all users & groups that have that specific property and pipe it to something usable.  It's the "something usable" I just can't get working.
Here's the script:
Import-Module ActiveDirectory
$MailEnabledGroups = Get-Group -OrganizationalUnit "whateverOU" -Filter 'WindowsEmailAddress -ne $null'
$MailEnabledGroups | Foreach-Object {
Set-Location AD:
Get-Acl $_.DistinguishedName | select -exp Access | ?{$_.ObjectType -match 'bf9679c0-0de6-11d0-a285-00aa003049e2' -and $_.ActiveDirectoryRights -match 'WriteProperty' -and $_.IdentityReference -notmatch 'Exchange Windows Permissions'}
So this gives me correctly all the users or groups that have that exact property, but I'm just trying to extract the group displayname & the identityreference of the account.
I've tried with Select, Format-Table... I just don't have the expertise in PS to get this right at all.  something like | ft displayname,identityreference sorta gives me the info, but it puts the displayname of the group as a header, and if I use -hidetableheaders,
then I lose completely the group name I need to keep.  Then there's Select that just won't ever show me the group correctly or just jumbles all identityreference names in 1 big column without knowing which group they in the ACE of.
Once I get that, it's just a matter of piping group + accounts back in the set-distributiongroup and use -managedby to target the accounts I find with get-acl.
I'm aware there's tools out there that work a whole lot better than get-acl, but I do not have authorization to install/use non standard modules on our servers...
Hell, at this point, I'll even take VBS ot a batch file :P if it can get what I need, but I've been trying to use Powershell a lot more... getting information isn't a bit problem, it's the formatting of how to spit out the information that is a massive headache
for me still
It's probably some silly combination or format-table commands or whatever, but I definitely can't put my finger on it... any help on this would be greatly appreciated.
Thank you.

Hi Dechy_007,
I‘m writing to check if the suggestions were helpful, if you have any questions, please feel
free to let me know.
If you have any feedback on our support, please click here.
Best Regards,
Anna
TechNet Community Support

Similar Messages

  • ACE - configuring script probes (tclsh)

    Hey guys
    I'm looking for exampels about writing script probes for the ACE module.
    In the cisco's ACE configuration guide i already found one, but i'd be happy to have a few more. Does anybody knows where i can get some other examples?
    cheers
    patrick

    Tach auch and Hello!
    If you check the software section for the ACE Module you will find some ace scripts you can download.
    http://www.cisco.com/cgi-bin/Software/Tablebuild/doftp.pl?ftpfile=cisco/crypto/3DES/lan/catalyst/6500/ace/ace_scripts.tgz&app=Tablebuild&status=showC2A
    Viel Erfolg
    Roble

  • PS Bridge: how to load files to PS in a specific layer sequence?

    Hello. Have massive graphic files and trying to call up various arrangements of them quickly.
    I just discovered History Snapshot, which is awesome, but wondering if it is possible in Bridge
    to control the layer sequence order when loading files to Photoshop.
    Menu Path= Tools_Photoshop_Load Files into Photoshop Layers
    Thanks in advance for your suggestions.

    There are several ace script writers here, but go ask on the Scripting forum
    Photoshop Scripting
    Be sure to give exact details of your requirements, along with the operating system, and Photoshop version you are using.

  • Request - Perl script that can parse an ACE config from a VIP

    Has anyone ever written a Perl script that can take the VIP from an ACE config and parse it out into the component parts of the config, ACLs, NATs, Class-map, policy-map, etc. ?
    This seems like something someone must have written already.
    Thanks in advance!

    Any reason you dont want to use XML instead of doing just PERL ?  Its lot easier to do with XML scripts as ACE has a XML interface to query whatever is needed. So that said, you can use a perl to interface ACE via XML. Here's a simple Perl that uses LibCurl:
    #!/usr/bin/perl
    use WWW::Curl::Easy;
    my $numArgs = $#ARGV + 1;
    if ($numArgs<4)
    die("Usage: shusers.pl ip_address username password command\n");
    my $ip = @ARGV[0];
    my $uname = @ARGV[1];
    my $pwd = @ARGV[2];
    my $cmd = @ARGV[3];
    my $curl = new WWW::Curl::Easy;
    my $posturl = "http://$ip/bin/xml_agent/";
    my $xml_cmd = "xml_cmd=<$cmd/>";
    $curl->setopt(CURLOPT_HEADER, 0);
    $curl->setopt(CURLOPT_FRESH_CONNECT, 1);
    $curl->setopt(CURLOPT_URL, $posturl);
    $curl->setopt(CURLOPT_RETURNTRANSFER,1);
    $curl->setopt(CURLOPT_USERPWD,"$uname:$pwd");
    $curl->setopt(CURLOPT_POST,1);
    $curl->setopt(CURLOPT_POSTFIELDS, $xml_cmd);
    $curl->perform;
    my $info = $curl->getinfo(CURLINFO_RESPONSE_CODE);
    print $info;
    Hope this helps.
    Cheers
    V.K

  • Ace 4710 3.2.4 and script

    Hi all,
    i've got a problem with script...
    from debug command i receive msg
    '(ctx:1) TCLPROBE(hm_tcl_exit_proc): File open failed'
    same script works on ACE module....why cannot read script ACE4710?
    tnx
    Dan

    Hi Gilles,
    AceFemaster/FE# show probe script_ver_pippo_CS01_80 detail
    probe : script_ver
    type : SCRIPTED
    state : ACTIVE
    description :
    port : 0 address : 0.0.0.0 addr type : -
    interval : 15 pass intvl : 30 pass count : 2
    fail count: 5 recv timeout: 10
    script filename : script_ver.tcl
    ------------------ probe results ------------------
    associations ip-address port porttype probes failed passed health
    ------------ ---------------+-----+--------+--------+--------+--------+------
    real : pippo_CS01[80]
    serverfarm: S_pippo_80
    1.1.1.1 80 REAL 2 2 0 FAILED
    Socket state : RESET
    No. Passed states : 0 No. Failed states : 1
    No. Probes skipped : 0 Last status code : 30006
    No. Out of Sockets : 0 No. Internal error: 0
    Last disconnect err : Internal error: Script error
    Last probe time : Tue Nov 17 15:07:35 2009
    Last fail time : Tue Nov 17 15:07:20 2009
    Last active time : Never
    in debug i can see a empty string as exit message...
    2009 Nov 17 15:09:05.761594 scripted_hm: (ctx:1) TCLWT (scripted_hm_run_probe_msg): Received MTS_RUN_MSG
    2009 Nov 17 15:09:05.761656 scripted_hm: (ctx:1)tcl_wt_create_qnode: temp_qnode 0x81137b8 em_msg 0xb689e054
    2009 Nov 17 15:09:05.761695 scripted_hm: (ctx:1) TCL_UTIL(hm_tcl_associate_script_buf) - ENTER em_msg = 0xb689e054
    2009 Nov 17 15:09:05.761725 scripted_hm: (ctx:1) TCL_UTIL (hm_tcl_associate_script_buf) : Associating script-buf with script_ver.tcl em_msg = 0xb689e054
    2009 Nov 17 15:09:05.761755 scripted_hm: (ctx:1) TCL_UTIL(hm_tcl_find_script_buf) - ENTER
    2009 Nov 17 15:09:05.761785 scripted_hm: (ctx:1) TCL_UTIL(hm_tcl_find_script_buf) - Found script buf
    2009 Nov 17 15:09:05.761814 scripted_hm: (ctx:1)TCL_UTIL(hm_tcl_associate_script_buf) - EXIT
    2009 Nov 17 15:09:05.761844 scripted_hm: (ctx:1) TCLWT(tcl_wt_create_qnode): Created qnode 81137b8
    2009 Nov 17 15:09:05.761454 scripted_hm: (ctx:1)hm_tcl_run: pid 24428 return_fd 13 ZÕô·h^UØ·(Jî·
    2009 Nov 17 15:09:05.762007 scripted_hm: (ctx:1) TCL_UTIL(hm_tcl_set_env_vars): arg list = "GET /pls/portal30/ecare.monitoring HTTP/1.0" html 0 172.18.255.172 80 OK
    2009 Nov 17 15:09:05.762041 scripted_hm: (ctx:1) TCL_UTIL(hm_tcl_get_argcount) - ENTER, argv("GET /pls/portal30/ecare.monitoring HTTP/1.0" html 0 172.18.255.172 80 OK)
    2009 Nov 17 15:09:05.762090 scripted_hm: (ctx:1)hm_tcl_run: About to run the TCL interpreter
    2009 Nov 17 15:09:05.762387 scripted_hm: (ctx:1)Tcl_Itasca_SocketObjCmd: g_num_socket 1
    2009 Nov 17 15:09:05.763381 scripted_hm: (ctx:1)tclret 1
    2009 Nov 17 15:09:05.763524 scripted_hm: (ctx:1) TCLPROBE(hm_tcl_exit_proc): File open failed
    2009 Nov 17 15:09:05.765827 scripted_hm: (ctx:1)TCL-WT(tcl_wt_process_interp_return) - ENTER
    2009 Nov 17 15:09:05.765870 scripted_hm: (ctx:1) TCLWT(tcl_wt_process_interp_return): received error from scripted probe!
    2009 Nov 17 15:09:05.765903 scripted_hm: (ctx:1) TCLWT(tclwt_send_em_msg): ENTER
    2009 Nov 17 15:09:05.765932 scripted_hm: (ctx:1) TCL-WT(tclwt_send_em_msg): exit msg = empty string
    2009 Nov 17 15:09:05.764984 scripted_hm: (ctx:1) TCLWT(tclwt_send_em_msg): EXIT without Error
    2009 Nov 17 15:09:05.765015 scripted_hm: (ctx:1)TCL-WT(tcl_wt_process_interp_return) - EXIT
    for network trace i'm trying to obtain it.
    tnx a lot
    Dan

  • ACE TCL Script Probe for Websphere MQ

    Have anyone written a TCL script to probe MQ from the ACE?  Our app guys are saying that a Layer 4 probe (TCP port check) is generating errors in the QManager logs because there is no data exchange, just TCP connection setup, then tear-down.
    Thought I would check here to see if anyone has written a TCL Script for this before or has any other suggestions.
    Thanks!                  

    Hi,
    What do you need to check exactly on the server?  will be an specific uri?
    Cesar R
    ANS Team

  • ACE# sh script code - Error: Called API is invalid or non-existant

    What is this ??
    ACE# dir disk0:
       2846 Jun 14 2010 15:40:33 NORDICID_PROBE
    ACE# sh script code NORDICID_PROBE
    Error: Called API is invalid or non-existant
    Hardware is ACE-4710-K9 and software A3(2.7)
    The probe itself is functioning ok according to show probe detail.
    However show script script_name probe_name -counters all remain at zero for some reason. This wasn't the case on the previously use ACE software.
    To my recollection the command show script code has worked successfully before on the same ACE software. Not 100% sure though, but it definitely worked on the previous software we ran on the ACE.

    Hi Timo,
    You could be hitting CSCtu33866 (see
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtu33866 for more details)
    If you are really hitting this bug, a reboot should fix the issue.
    I hope this helps
    Daniel

  • Looking for ACE Probe TCL script specific for LDAPS

    Hello Everyone,
    I have searched the forum, and i am having difficulty finding an example of how to modify the LDAP TCL probe from port 389 to secure LDAP port 636.
    Could someone kindly point me or provide me the modified TCL script if you happen to have it.
    During my search I also found a config that someone had provided, which contained the following probe:
    probe tcp LDAPS_Probe
      port 636
    probe tcp LDAP_Probe
      port 389
    I was trying to figure out if this a modified TCL script for LDAP or modifed TCP TCL script specific for port 636.
    This is how I applied the script for LDAP port 389.
    script file 1 LDAP_PROBE
    probe scripted LDAP_PROBE_389
    interval 5
    passdetect interval 30
    receive 5
    script LDAP_PROBE
    serverfarm host SF-LDAP-389
    description SF LDAP Port 389
    predictor leastconns
    probe LDAP_PROBE_389
    rserver LDAP-RS1-389
    inservice
    I will be more than glad to provide you any additional information that you need.
    As always thanks for your input.
    Raman Azizian
    SAIC/NISN Network services

    normally you would engage a TCL developer or ciso advanced services to develop a custom script for anything other than what Cisco provides in canned scripts. If you are comfortable with tcl you can do it yourself. Here is an example of the LDAP script modified to include initiation via ssl.  default port is 389 when you implement you would specify 636.
    #!name = LDAP_PROBE
    # Description:
    #    LDAP_PROBE opens a TCP connection to an LDAP server, sends a bind request. and
    #    determines whether the bind request succeeds.  LDAP_PROBE then closes the
    #    connection with a TCP RST.
    #    If a port is specified in the "probe scripted" configuration, the script probes
    #     each suspect on that port. If no port is specified, the default LDAP port 389
    #     is used.
    # Success:
    #   The script succeeds if the server returns a bind response indicating success
    #    (status code 0x0a0100) to the bind request.
    #   The script closes the TCP connection with a RST following a successful attempt.
    # Failure:
    #   The script fails due to timeout if the response is not returned.  This
    #    includes a failure to receive ARP resolution, a failure to create a TCP connection
    #    to the port, or a failure to return a response to the LDAP bind request.
    #   The script also fails if the server bind response does not indicate success.
    #    This specific error returns the 30002 error code.
    #   The script closes any attempted TCP connection, successful or not, with a RST.
    #  PLEASE NOTE:  This script expects the server LDAP bind response to specify length
    #   in ASN.1 short definite form.  Responses using other length forms (e.g., long
    #   definite length form) will require script modification to achieve success.
    # SCRIPT version: 1.0       April 1, 2008
    # Parameters:
    #   [DEBUG]
    #      username - user login name
    #      password - password
    #      DEBUG        - optional key word 'DEBUG'. default is off
    #         Do not enable this flag while multiple probe suspects are configured for this
    #         script.
    # Example config :
    #   probe scripted USE_LDAP_PROBE
    #         script LDAP_PROBE
    #   Values configured in the "probe scripted" configuration populate the
    #   scriptprobe_env array.  These may be accessed or manipulated if desired.
    # Documentation:
    #    A detailed discussion of the use of scripts on the ACE is included in
    #       "Using Toolkit Command Language (TCL) Scripts with the ACE"
    #    in the "Load-Balancing Configuration Guide" section of the ACE documentation set.
    # Copyright (c) 2005-2008 by Cisco Systems, Inc.
    # debug procedure
    # set the EXIT_MSG environment variable to help debug
    # also print the debug message when debug flag is on
    proc ace_debug { msg } {
        global debug ip port EXIT_MSG
        set EXIT_MSG $msg
        if { [ info exists ip ] && [ info exists port ] } {
         set EXIT_MSG "[ info script ]:$ip:$port: $EXIT_MSG "
        if { [ info exists debug ] && $debug } {
         puts $EXIT_MSG
    # main
    # parse cmd line args and initialize variables
    ## set debug value
    set debug 0
    if { [ regsub -nocase "DEBUG" $argv "" argv] } {
        set debug 1
    ace_debug "initializing variable"
    set EXIT_MSG "Error config:  script LDAP_PROBE \[DEBUG\]"
    set ip $scriptprobe_env(realIP)
    set port $scriptprobe_env(realPort)
    # if port is zero the use well known ldap port 389
    if { $port == 0 } {
        set port 389
    # PROBE START
    # open connection
    ace_debug "opening socket"
    set sock [  socket -sslversion all -sslcipher RSA_WITH_RC4_128_MD5 $ip $port ]
    fconfigure $sock -buffering line -translation binary
    # send a standard anonymous bind request
    ace_debug "sending ldap bind request"
    puts -nonewline $sock [ binary format "H*" 300c020101600702010304008000 ]
    flush $sock
    #  read string back from server
    ace_debug "receiving ldap bind result"
    set line [read $sock 14]
    binary scan $line H* res
    binary scan $line @7H6 code
    ace_debug "received $res with code $code"
    #  close connection
    ace_debug "closing socket"
    close $sock
    #  make probe fail by exit with 30002 if ldap reply code != success code  0x0a0100
    if {  $code != "0a0100" } {
        ace_debug " probe failed : expect response code \'0a0100\' but received \'$code\'"
        exit 30002
    ## make probe success by exit with 30001
    ace_debug "probe success"
    exit 30001

  • ACE probe TCL script database

    Hello everyone, okay?
    I was thinking of a possibility to use my ACE to monitor a database, in this case a MySQL database Today I use a TCP probe, monitoring the port, but I would go one step further and try to make a connection in the DATABASE.
    I would like to see the possibility of a guideline in creating a TCL script to make a simple connection to a database.
    The idea is to try to make a connection in a database, run a query / select on any table just to validate its functionality and not just checking if the port is responding.
    I do not know how complex it is or what would be my pre -requisites required, but any help would be welcome.
    I thought about using an HTTP probe to make this validation and use a web page making the connection to the database, but it ended up creating another layer and if there is any problem in web service, the database would be affected indirectly.
    Thank you. All suggestions are welcome.

    Hi Plinio,
    I cannot see any support for testing authentication, SQL queries or connections to a database that is supported directly in TCL at this time.
    Here is the TCL guide that expalains the supported commands ( there is a HTTP example probe at the bottom )
    http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA4_2_0/configuration/slb/guide/script.html
    Beyond a TCL TCP probe to the port to test the listener is running, I believe your suggestion of a HTTP TCL script is probably the most accurate way to check the integrity of the database. You could write code to set a certain response to all types of failure scenarios and on the ACE you could then use a HTTP TCL script to parse the response from the web server to identify exactly what has failed in your database and act accordingly.
    cheers,
    Chris

  • ACE - removing script from ACE memory

    Hi,
    I played with scripted probes and now I can't remove script from ACE memory... because I have no 'script file NN SCRIPT_NAME' in my running config, therefore I can't remove script from memory with 'no script file NN'.
    When I try delete file from disk0: and upload modified file (with the same file name), 'sh file disk0:SCRIPT_NAME' shows correct file content, but 'sh script code SCRIPT_NAME' is wrong (because script is loaded in memory).
    How it's possible to unload script from memory if no 'script file NN script_name' in running config exists?
    martin

    Martin,
    this is a bug.
    The 'no script file ' should be enough to remove the script from memory.
    I checked the code and this is something that can easily be fixed.
    I will submit a new ddts.
    Thanks for pointing this issue to us.
    Gilles.

  • TCL scripted probes on ACE

    Hi,
    I have two questions about TCP scripts on ACE :
    1. TCP source code
    How can I browse the TCL source code of predefined probe scripts on the ACE (for instance HTTPCONTENT_PROBE) '
    2. Script parameters
    How do I retrieve in the TCL script the parameters passed to the script in the command < script script_name [script_arguments] >  ?
    Thank you,
    Yves

    Yves,
    you can download all the scripts from the download software page.
    http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=A2%283.2%29&mdfid=280557289&sftType=Application+Control+Software+Scripts&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+ACE+Application+Control+Engine+Module&treeMdfId=268437639&treeName=Application+Networking+Services&modifmdfid=null&imname=&hybrid=Y&imst=N&lr=Y
    # Copyright (c) 2005-2008 by Cisco Systems, Inc.
    # debug procedure
    # set the EXIT_MSG environment variable to help debug
    # also print the debug message when debug flag is on
    proc set_exit_msg { msg } {
        global debug ip port EXIT_MSG
        set EXIT_MSG $msg
        if { [ info exists ip ] && [ info exists port ] } {
            set EXIT_MSG "[ info script ]:$ip:$port: $EXIT_MSG "
        if { [ info exists debug ] && $debug } {
            puts $EXIT_MSG
    # main
    # Parse cmd line args and initialize variables
    set_exit_msg "initializing variable"
    if { $argc <  2 } {
        set_exit_msg "[ info script ] parameters :
        exit 30002
    set ip $scriptprobe_env(realIP)
    set port $scriptprobe_env(realPort)
    # If port is zero then use well known HTTP port 80
    if { $port == 0} {
        set port 80
    set requestHeader [ lindex $argv 0 ]
    set expectFileType [ lindex $argv 1 ]
    set debug [ lindex $argv 2 ]
    if { $debug == "" } {
        set debug 0
    # Open connection
    set_exit_msg "opening socket"
    set sock [ socket $ip $port ]
    # Send HTTP request to server
    set_exit_msg "sending request : $requestHeader"
    puts -nonewline $sock "$requestHeader\n\n"
    flush $sock
    # Read string back from server
    set_exit_msg "receiving response"
    set lines [ read $sock ]
    # Close connection
    set_exit_msg "closing socket"
    close $sock
    # Parse the HTTP response
    # All the following conditions cause probe failure, returning exit code 30002
    # Unable to recognize the HTTP response
    if { ![ regexp -nocase "^HTTP/1\.\[0-9\] (\[0-9\]\[0-9\]\[0-9\])" $lines match s
    tatuscode ] } {
        set_exit_msg "probe fail : can't find status code"
        exit 30002
    # HTTP response is not 200 OK
    if { $statuscode != "200" } {
        set_exit_msg "probe fail : status code is $statuscode"
        exit 30002
    # Unable to find Content-type header
    if { ![ regexp  -nocase  "Content-Type *:(.*)\n" $lines match foundContentType]
        set_exit_msg "probe fail : can't find \'Content-Type\' header"
        exit 30002
    # Content-type value does not contain the requested string
    if { ![ regexp "$expectFileType" $foundContentType]  } {
        set_exit_msg "probe fail : expect content-type \'$expectFileType\', but got
    \'$foundContentType\'"
        exit 30002
    # Indicate probe success with exit code 30001
    set_exit_msg "probe success"
    exit 30001

  • ACE TCL script debug.

    Hi all,
    I would like to write custom TCL script in ACE. I would like to write some info for debugging to the console with "puts $VAR ", but nothing is shown.
    What could be the problem ? I have debug hm all on.
    Regards,
    szicsu

    Look into an existing script and reuse the same debug function
    proc ace_debug { msg } {
    global debug ip port EXIT_MSG
    set EXIT_MSG $msg
    if { [ info exists ip ] && [ info exists port ] } {
    set EXIT_MSG "[ info script ]:$ip:$port: $EXIT_MSG "
    if { [ info exists debug ] && $debug } {
    puts $EXIT_MSG
    Gilles.

  • Script on ACE to do a packet capture during probe failure

    Hi All,
    I'm working on troubleshooting Intermittent application access. probe was getting failed intermittently.
    Is it possible to run any script on ACE which will do the packet capture only if the probe failed to an application?
    Regards,
    Thiyagu

    Thiyagu,
    The ACE was not designed to run captures( at least not at high level as a NAM for example) then the traces which we can take in the ACE does not capture neither probe traffic nor management traffc only load balancing traffic.
    TAC does not support customized scripts.
    If you need to check how the probes are behaving then you may need to run a simultaneous capture on the client PC and the server itself or if you have an ACE module then you can run a 10giga capture.
    Jorge

  • ACE - LDAP TCL Script

    Hi,
    we are using the TCL LDAP_Script as a probe scripted for LDAP server farm. The default script the Cisco provided is sending only an anonymous binding to the LDAP servers, we are trying to modify this script to sned a credential binding with username and password. Anyone done something like that before!
    Your contribution is appreciated.
    Hadi

    Hi Habeel,
    I've answered this question before. If you search the forum for "ldap healtcheck script" - and yes the typo is real then you'll see what I did.
    The text is here:
    The easiest way is to capture a packet with the authentication credentials and then replace the hex bind string in the example.
    The alternative is to handcode the BER coded ASN.1 data string - which while more fun is time consuming. The remainder of the script can stay the same.
    I've done this on an ACE module. You have to be aware that 300c02010160 in the example script string is a sort of "header" that holds the request id (1). This will be different in your packet capture.
    If you look at the decomposition of the example you'll be able to see how it is put together and what you need to change.
    0x30 The start of a universal constructed sequence
    0x0c The length of the sequence minus the tag and length bytes = 12 bytes
    0x02 Next field is an integer
    0x01 The length of the next field (1 byte)
    0x01 Value (this is the message ID)
    0x60 Application, number 0, use RFC2251 to decode. This is a Bind Request
    0x07 Length of data to follow.
    0x02 Integer
    0x01 Length 1
    0x03 3 - this is the LDAP version.
    0x04 String
    0x00 Length 0
    0x80 Simple Authentication
    0x00 Length 0
    Just keep the id the same in the unbind.
    The string I use is:
    302d02010160280201030418636e3d41636550726f78792c6f3d556e69766572736974798009ffffffffffffffffff
    where I've replaced the 9 character password with 9*x'ff'.
    The username for binding is AceProxy. If you want to use the same script then create that username and set the password in the string above (in hex). If for example you set the password to Example12 then you need to set the 9*x'ff' to '4578616d706c653132' - which is the hex representation of the ASCII.
    Note that if you use fewer or more than 9 characters then you'll need to change other values in the string because they refer to lengths.
    HTH
    Cathy

  • ACE TCL Script to retrieve Cookie

    I am in need to to do a post instead of a Get with a probe. So I have configured a TCL script to perform this. The issue I have is that I also need to parse the Cookie instead of the http1. response. Any ideas? Or does anyone have a variable indetifiers for TCL scripting that Cisco uses?
    Thank you,
    Tim

    HI Thulin,
    Health probe scripts have access to many configured items through a predefined TCL array. The most common use of this array is to find the current real server IP addresses of the suspect during any particular launch of the script.
    Whenever the ACE executes a script probe, a special array called scriptprobe_env is passed to the script. This array holds important parameters that may be used by the script.
    Member name Content
    realIP
    Suspect IP address
    realPort
    Suspect IP port
    intervalTimeout
    Configured probe interval in seconds
    openTimeout
    Configured socket open timeout for this probe (tbd)
    recvTimeout
    Configured socket receive timeout for this probe
    failedTimeout
    Configure failed timeout
    retries
    Configured retry count
    healthStatus
    Current suspect health status
    contextID
    The ID for the context running this script
    failedRetries
    Consecutive successful retries on a failed server before marking it as passed
    isRouted
    Boolean to determine if this IP address is a routed address
    pid
    Process identifier of the TCL process
    runID
    Pointer to the event structure (em_event_t)
    Kindly refer to the following url to get more info regarding your tcl variables:
    http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/v3.00_A1/configuration/slb/guide/script.html#wp1082112
    http://www.cisco.com/univercd/cc/td/doc/solution/dc_ap11i.pdf
    http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/mod_icn/ace/ace_301/slbgd/script.pdf
    Regards,
    Sachin Garg

Maybe you are looking for

  • AR Aging Report by Code Combination

    We are on 11.5.10. Our AR invoice has several lines and each line could be against a specific Div/ CC (code combination). Given that we do not have a centralized collection department, we are looking for a aging report by Div/ CC, so that the report

  • Tuxedo errors LIB_GWT_CAT:1561 and LIBGWT_CAT156

    Hi Folks, I see the tuxedo gateway domain issued the following errors: 080812.usrncwa1!GWTDOMAIN.26600.4.0: LIBGWT_CAT:1561: ERROR: Network send error, drop message! 080812.usrncwa1!GWTDOMAIN.26600.4.0: LIBGWT_CAT:1041: ERROR: Unrecoverable error occ

  • Yesterday morning when I logged on Firefox updated and then started. Since that update everytime I log onto my G-Mail account Firefox crashes

    This event only started yesterday morning after an automatic update by Firefox. It has never happened before. Each time I open G-Mail Firefox crashes. I have downloaded Firefox twice since but it still happens I thought about removing Firefox altoget

  • Updating without internet

    I bought an iMac on Ebay, it came equipped with OSX 10:35. I tried to install Animation Master but got the message "requires 10:46 or higher" I boughtOSX10:4. The iMac is not connected to the Internet and cannot be without difficulty on my part.Is th

  • V CAST Apps

    I cannot load the V CAST Apps to my phone.  It says Loading......... then i get ERROR: unable to complete request. I have sent an app to my phone through the verizon website, tried loading it, and still get the same error.  Anyone know how i install