Hello
Pease see the below ouput of the commands on the failing and the working controller
Here are some of the options in a failing filer….
emomni0117c01> options httpd
httpd.access legacy
httpd.admin.access legacy
httpd.admin.enable on
httpd.admin.hostsequiv.enable off
httpd.admin.max_connections 512
httpd.admin.ssl.enable on
httpd.admin.top-page.authentication off
httpd.autoindex.enable off
httpd.bypass_traverse_checking off
httpd.enable off
httpd.ipv6.enable off
httpd.log.format common (value might be overwritten in takeover)
httpd.method.trace.enable off
httpd.rootdir /vol/vol0/home/http
httpd.timeout 300 (value might be overwritten in takeover)
httpd.timewait.enable off (value might be overwritten in takeover)
emomni0117c01>
emomni0117c01> options ssl
ssl.enable on
ssl.v2.enable off (same value required in local+partner)
ssl.v3.enable off (same value required in local+partner)
emomni0117c01>
emomni0117c01>
emomni0117c01> options tls
tls.enable on (same value required in local+partner)
emomni0117c01>
emomni0117c01> secureadmin show
Usage:
secureadmin setup [-f] [-q] ssh
secureadmin setup [-f] [-q] ssl
secureadmin addcert ssl [<path to CA signed cert>]
secureadmin enable all|ssh|ssh1|ssh2|ssl
secureadmin disable all|ssh|ssh1|ssh2|ssl
secureadmin status
emomni0117c01> secureadmin status
ssh2 - active
ssh1 - inactive
ssl - active
emomni0117c01>
here are the same options ina working filer….
emomni0120c01> options httpd
httpd.access legacy
httpd.admin.access legacy
httpd.admin.enable on
httpd.admin.hostsequiv.enable off
httpd.admin.max_connections 512
httpd.admin.ssl.enable on
httpd.admin.top-page.authentication off
httpd.autoindex.enable on
httpd.bypass_traverse_checking off
httpd.enable off
httpd.ipv6.enable off
httpd.log.format common (value might be overwritten in takeover)
httpd.method.trace.enable off
httpd.rootdir /vol/vol0/home/http
httpd.timeout 300 (value might be overwritten in takeover)
httpd.timewait.enable off (value might be overwritten in takeover)
emomni0120c01>
emomni0120c01> options ssl
ssl.enable on
ssl.v2.enable off (same value required in local+partner)
ssl.v3.enable off (same value required in local+partner)
emomni0120c01>
emomni0120c01> options tls
tls.enable on (same value required in local+partner)
emomni0120c01>
emomni0120c01> secureadmin status
ssh2 - active
ssh1 - inactive
ssl - active
emomni0120c01>
the only difference, between the 2 , that the customer can see is
httpd.autoindex.enable
is set to off on 117c01 ( failing) , and its set on on on 0120c01 ( working)
Also customer is able to connect to the controller using Zexplore.
I have attached more findings on the case which the customer has shared over email.