Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2222295.1
Update Date:2017-06-12
Keywords:

Solution Type  Problem Resolution Sure

Solution  2222295.1 :   Diameter Signaling Router (DSR) - The "Named" Service Is Not Starting on NOAM Server  


Related Items
  • Oracle Communications Diameter Signaling Router (DSR)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-13838445041>

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 4.0 and later
Information in this document applies to any platform.

Symptoms

The "named" service is not starting on the NOAM server. When trying a manual restart of the service, the start sequence is rejecting the following errors:

The "named" service is not starting on NOAM server and the start sequence is
rejecting the following errors:

[root@dsr-no-a savelogs]# service named start

Starting named:

Error in named configuration:

rdb.platform.cgbu.us.oracle.com:33: ignoring out-of-zone data
(1.1.1.1.in-addr.arpa)

rdb.platform.cgbu.us.oracle.com:34: ignoring out-of-zone data
(2.2.2.2.in-addr.arpa)

rdb.platform.cgbu.us.oracle.com:35: ignoring out-of-zone data
(2.2.2.3.in-addr.arpa)

dns_rdata_fromtext: rdb.platform.cgbu.us.oracle.com:35: near
'fra-da-mp-1-xsi1_fra.platform.cgbu.us.oracle.com.': bad name (check-names)

rdb.platform.cgbu.us.oracle.com:36: ignoring out-of-zone data
(2.2.2.5.in-addr.arpa)

dns_rdata_fromtext: rdb.platform.cgbu.us.oracle.com:36: near
'fra-da-mp-1-xsi2_fra.platform.cgbu.us.oracle.com.': bad name (check-names)

rdb.platform.cgbu.us.oracle.com:37: ignoring out-of-zone data
(1.1.1.2.in-addr.arpa)

dns_rdata_fromtext: rdb.platform.cgbu.us.oracle.com:37: near
'fra-da-mp-1-xsi3_fra.platform.cgbu.us.oracle.com.': bad name (check-names)

rdb.platform.cgbu.us.oracle.com:38: ignoring out-of-zone data
(2.2.2.4.in-addr.arpa)

dns_rdata_fromtext: rdb.platform.cgbu.us.oracle.com:38: near
'fra-da-mp-1-xsi4_fra.platform.cgbu.us.oracle.com.': bad name (check-names)

rdb.platform.cgbu.us.oracle.com:39: ignoring out-of-zone data
(10.1.1.1.in-addr.arpa)

 

Cause

The "named" service is not starting due to the following highlighted FQDNs (fra-da-mp-1-xsi1_fra, fra-da-mp-1-xsi2_fra...) which are not respecting the FQDN standard naming format. In fact,
these names are containing "_" character while the standards forbid the use of this character (except in the beginning of the FQDN name which is not the case here).
These FQDNs names are a concatenation between the network names and the servers names. The concatenated names are filled in a couple of files that are used in the "named" service configuration (such as
/var/named/db.platform.cgbu.us.oracle.com & /var/named/rdb.platform.cgbu.us.oracle.com files).
When checking the different network names defined in the NOAM GUI, it was discovered that the "_" character was used in most of the XSI networks' names and this explains why the "named" service is complaining about the above FQDNs (fra-da-mp-1-xsi1_fra, fra-da-mp-1-xsi2_fra...).
 

Solution

Bug 25351500 has been created to handle this issue. This bug is resolved in DSR 8.1 release.

As a workaround the removal of the "_" character from the network names on the "Main Menu -> Configuration -> Network" menu of the NOAM GUI resolves the issue.

References

<BUG:25351500> - THE "NAMED" SERVICE NOT STARTING DUE TO WRONG NAME FORMAT OF DEFINED "NETWORKS"

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback