Node name of the OXE
Posted: 21 Sep 2010 15:04
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
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