So, I was having a problem on a server that had more than 1 NIC but eDirectory was attached to only one of the IPs. When I’d run dxcmd, it would continually attach to the NIC that didn’t have eDirectory bound. For the life of me, I couldn’t find documentation on how to specify the IP address for dxcmd and any of the standard windows help switches ( /?, etc) were not working (of coarse I didn’t try the *nix switches as this was a Windows installation). Finally, by accident, I got the help list with all the switches! YAY! Here they are:
If no actions are specified interactive mode is used. Configuration: -user <user name> -host <name or IP address> -password <user password> -port <port number> -cert <X.509 DER certificate filename> -dnform <slash|qualified-slash|dot|qualified-dot|ldap> (force dn form) -version <n.n[.n[.n]]> (force engine version for testing) -nossl (use clear socket for LDAP) -keystore <keystore path and filename> (for LDAP SSL) -storepass <keystore password> (for LDAP SSL) -q (quiet mode) -v (verbose mode) -s (write result to stdout) -? (show this message) -help (show this message) Actions: -start <driver dn> -stop <driver dn> -getstate <driver dn> -getstartoption <driver dn> -setstartoption <driver dn> <disabled|manual|auto> <resync|noresync> -getcachelimit <driver dn> -setcachelimit <driver dn> <0 or positive integer> -migrateapp <driver dn> <filename> -setshimpassword <driver dn> <password> -clearshimpassword <driver dn> -setremoteloaderpassword <driver dn> <password> -clearremoteloaderpassword <driver dn> -sendcommand <driver dn> <input filename> <output filename> -sendevent <driver dn> <input filename> <output filename> -queueevent <driver dn> <input filename> -setlogevents <dn> <integer ...> -clearlogevents <dn> -setdriverset <driver set dn> -cleardriverset -getversion -initdriverobject <dn> -setnamedpassword <driver, driverset or job dn> <name> <password> [description] -clearnamedpassword <driver, driverset or job dn> <name> -clearallnamedpasswords <driver or job dn> -getdriverstats <driver dn> <output filename> -resetdriverstats <driver dn> -startjob <job dn> -abortjob <job dn> -getjobrunningstate <job dn> -getjobenabledstate <job dn> -getjobnextruntime <job dn> -updatejob <job dn> -getcachetransactions <driver dn> <position token> <transaction count> <output filename>
More articles on my Website.
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.