Skip to main content

HP OA & VC SSL & LDAP setup

Acronym-y title translation:  HP Onboard Administrator and Virtual Connect SSL and LDAP setup.  Although if you had to ask, you probably don't need to read the rest of this post.

I was tasked with scripting the setup of SSL and LDAP authentication for the OA and VC modules in our blade enclosures.  This mostly just contains the settings you need, I will post up the script when done.

DNS/NTP

Ensure DNS server settings are correct for the enclosure IP config.

Set up appropriate DNS records for the following:
* Active OA module IP
* Standby OA module IP
* VC Domain IP
* Active VC module IP
* Standby VC module IP

Ensure NTP is sync'd to your AD environment - AD auth won't work if there is a time discrepancy of more than a few minutes.

OA LDAP Settings

Directory Settings
Directory Server Address: DCname.domain.local
Directory Server SSL Port: 636
Search Context 1: OU=Users,OU=parentOU,DC=domain,DC=local
Search Context 2: @domain.local

(Check 'Use NT Account Name Mapping')

Note that the documentation states you can just use 'domain.local' for the Directory Server Address...I tried this and got failures pinging the Directory Server, so just left as the 'main' DC FQDN.

Further, DO NOT un-check 'Enable Local Users' before you test and 100% validate AD authentication is working.  Srsly.

Directory Groups
Must be set to the exact display name of the group you're using to control access.

VC LDAP Settings

LDAP Server
LDAP Server Address: DCname.domain.local
LDAP Server SSL Port: 636

Search Context 1: OU=parentOU,DC=domain,DC=local
Search Context 2: @domain.local
(Check 'Use NT Account Name Mapping')

LDAP Groups
Must be set to the exact display name of the group you're using to control access.


Certificates

OA LDAP Certificate
Start->MMC->Add/remove snap-in->Certificates (Computer Account)->Personal->Certificates

Export DC certs (in base-64 format) - one for each critical site (for example one for the HQ DC, one for the DC...DC).  Upload them into OA one at a time.

OA Module Certificates & CSR
1. Under Active Onboard Administrator/Certificate Administration/Cert Request, get the CSR text, dump into .txt file. (Generate a CSR, note that the CN is the DNS name you want to use for the OA module)
2. On your enterprise CA, copy the text file somewhere convenient and run this command and then copy out the generated .cer file back to your PC.
certreq -submit -attrib "CertificateTemplate:WebServer" encl01onad1.txt
3. Under Active Onboard Administrator/Certificate Administration/Cert Upload, paste in the contents of the .cer file (ensure no trailing lines).

OA SIM Certificate
We use SIM, so to enable SSL for SIM you need the SIM server's certificate, get it the same way you got the DC certs.

Testing

Test with IE first.  If that works, move on to Firefox.  You might need to import the Root CA's cert to Firefox.


Script

Coming....













Comments

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:


You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get going...so here's a config and brain dump...

Why?
You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

How?
ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…