Updating the configuration after upgrading and changing from IPv4 to IPv6

Recommendation

Instead of changing a server from an IPv4 network to an IPv6 network directly, BMC recommends leaving the server in dual mode so that the IPv4 and IPv6 clients can both connect to the server.

If you must switch a server from an IPv4 network to an IPv6 network, follow the procedures in this topic.

If you have installed BMC Remedy Action Request (AR) System and BMC Atrium Core on a server with an IPv4 address and then changed to an IPv6 address, you must complete the following tasks:

Before you restart the BMC Remedy AR System server after switching to an IPv6 domain, you must ensure that the host name or fully qualified domain name (FQDN) in the configuration files is valid in the IPv6 environment. Otherwise, BMC Atrium Core components might not work as expected, for example when adding or editing configuration items (CIs) in BMC Atrium Explorer.

To verify valid domain names for IPv6 servers

For all platforms, you must verify that the domain name specified in the configuration files is valid in the IPv6 environment.

  1. On the server where BMC Atrium Core is installed, open each of the following files in a text editor:
    • Windows:
      • <BMC_AR_SYSTEM_HOME>\conf\ar.cfg
      • <BMC_AR_SYSTEM_HOME>\conf\armonitor.cfg
      • <ATRIUMCORE_HOME>\wsc\wsregistryapi\conf\registryserver.properties
    • UNIX and Linux:
      • <ARSYSTEM_HOME>/conf/ar.conf
      • /etc/arsystem/<MACHINE_NAME>/armonitor.conf
      • <ATRIUMCORE_HOME>/wsc/wsregistryapi/conf/registryserver.properties
      • <ATRIUMCORE_HOME>/cmdb/server/bin/normeng.sh
      • <ATRIUMCORE_HOME>/cmdb/server/bin/atriumplugin.sh

  2. For the plug-in aliases in ar.cfg and ar.conf, verify that the specified host name is valid on the IPv6 network. 

    For example, if arserver1.calbro.com:9999 is the specified host name, verify that it is valid in the IPv6 environment. If it is not, you might have to remove the domain name (arserver1:9999) or change it to a valid host name such as arserver1.ipv6lab.calbro.com. 

    The following code is an example of plug-in aliases with the domain names.

    Server-Plugin-Alias: ARSYS.ARF.REGISTRY ARSYS.ARF.REGISTRY arserver1.calbro.com:9999
    Server-Plugin-Alias: ARSYS.ARDBC.REGISTRY ARSYS.ARDBC.REGISTRY arserver1.calbro.com:9999
    Server-Plugin-Alias: ARSYS.ARDBC.ARREPORTENGINE ARSYS.ARDBC.ARREPORTENGINE arserver1.calbro.com:9999
    Server-Plugin-Alias: ARSYS.ARF.QUERYPARSER ARSYS.ARF.QUERYPARSER arserver1.calbro.com:9999
    Server-Plugin-Alias: ARSYS.ALRT.WEBSERVICE ARSYS.ALRT.WEBSERVICE arserver1.calbro.com:9999
    Server-Plugin-Alias: ARSYS.ARF.PARSEPARAMETERS ARSYS.ARF.PARSEPARAMETERS arserver1.calbro.com:9999
    Server-Plugin-Alias: ARSYS.ARF.PUBLISHREPORT ARSYS.ARF.PUBLISHREPORT arserver1.calbro.com:9999
    Server-Plugin-Alias: ARSYS.ARF.REPORTSCHEDULER ARSYS.ARF.REPORTSCHEDULER arserver1.calbro.com:9999
    . . .

  3. For armonitor.conf, armonitor.cfg, registryserver.properties, normeng.sh, and atriumplugin.sh, search for and verify domain names. 
    The following code is an example of server entries with the domain names:

    bmc.uddi.registryserver.url.security=http://webservices1.calbro.com:8080/uddi/services/security
    bmc.uddi.registryserver.url.inquiry=http://webservices1.calbro.com:8080/uddi/services/inquiry
    bmc.uddi.registryserver.url.publishing=http://webservices1.calbro.com:8080/uddi/services/publication
    bmc.uddi.registryserver.url.subscription=http://webservices1.calbro.com:8080/uddi/services/subscription
  4. Save the edited files.
  5. If you had a server group configuration prior to switching from an IPv4 to IPv6 network, check and update the entries in the AR System Server Group Operation Ranking form:
    1. Open the AR System Server Group Operation Ranking form in search mode:
      http://:/arsys/forms/ /GroupAR+System+Server+Group+Operation+Ranking/
    2. Perform an unqualified search to see the entries in the form.
    3. For each server, check the Server value.
    4. Verify that the domain name is valid for all entries in the IPv6 environment.
    5. If a domain name is invalid, remove the domain name or change it to a valid IPv6 domain name.
    6. Save the AR System Server Group Operation Ranking form.
  6. Restart the AR System server and the BMC Atrium Core Web Services on the Apache Tomcat server. 
    If you have a server group, restart all the AR System servers in the group.

To update the Administration configuration

This issue occurs in a setup in which the server group setting is present before switching the network from IPV4 to IPV6.

If you have not verified the domain names as described previously in the AR System Server Group Operation Ranking form, then, on restart, the BMC Remedy AR System server might not recognize upon restart the hostname (such asarserver1.calbro.com). It then sets that property in the server configuration information and adds a new set of entries for the hostname in the AR System Server Group Operation Ranking.

If that happens, you must delete the new set of entries and edit the the Server Name Alias field to reflect the correct hostname/FQDN in an IPV6 network.

  1. Log on to the BMC Remedy AR System Administration Console.
  2. Open the AR System Server Group Operation Ranking form in search mode:
    http://:/arsys/forms/ /GroupAR+System+Server+Group+Operation+Ranking/
  3. Perform an unqualified search to see the entries in the form.
  4. For each server, check the Server value.
  5. Verify that the domain name or FQDN is valid for all entries in the IPv6 environment.
  6. If a domain name is not valid, remove the domain name or change it to a valid IPv6 domain name.
  7. Save the AR System Server Group Operation Ranking form.
  8. Restart the AR System server. 
    If you have a server group, restart all the AR System servers in the group.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*