Node name of the OXE

[banfield]

Hi.
I have today installed a BiCS 2.2. I followed the installation manual and administration.
Much of the documentation seems to be “old” ore have some mistakes. I used customers DNS.
The VMware machines and the BiCS server were configured in the customer DNS with reverse name as mention in the documentation. But to my surprises the name I choose for the node of the OXE were also checked against the customers DNS. This is not mention in the documentation.
I put then up this name to in the customer DNS pointing at the IP address to the OXE as with the hostname with reverse. But then we had problem with the OXE hostname. How and why should this be configured in the DNS? I thought OXE host would be enough.
OXE hostname and node name can’t either be the same name according to the documentation.
Another thing I notice from BiCS 2.2 is that the management of the backup is removed in the wizard so have to do it with k2configuration after.

BR

Daniel

[banfield]

I found this in the documentation. "Assigning a node name. If a node name is defined, the local DNS server can send the Main Call Server role address to an application monitoring several nodes.
This node name must be different from the physical name of the two Call Servers. It is configured as an alias in the hosts file"

So I guess there is nead of an alias DNS record in the customres DNS?

BR

Daniel

[banfield]

Node name should be a normal DNS record without revers pointing at the same IP address as the OXE. This is easy figured out when you look in the k2/log/k2dnscheck.log. Why could they not just write in plain English in the documentation?