- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Communication Problems between Database Servers
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 02:58 AM
11-24-2004 02:58 AM
Re: Communication Problems between Database Servers
I believe the ROUTE_GATEWAY[0]="200.200.120.254"
is maybe not quite good so check that
it should be the same on both servers since you are on the same lan
If lan1 is the config you want then copy the whole block:
ROUTE_DESTINATION[0]=default
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]=""
ROUTE_COUNT[0]=""
ROUTE_ARGS[0]=""
Just after the lan1 configuration and replace [0] by[1] and give the good route
Then you should be OK
Good luck
Victor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 03:01 AM
11-24-2004 03:01 AM
Re: Communication Problems between Database Servers
attached are both in a zip...netconf_production is production 200.200.120.3 and netconf_test is test 200.200.120.8
going to lunch..awaiting much needed help...thanks a lot all!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 03:02 AM
11-24-2004 03:02 AM
Re: Communication Problems between Database Servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 03:07 AM
11-24-2004 03:07 AM
Re: Communication Problems between Database Servers
I want to be very clear. On production I have to replace
ROUTE_DESTINATION[0]="default"
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]="200.200.120.254"
ROUTE_COUNT[0]="1"
ROUTE_ARGS[0]=""
with
what?
I'm not understanding...I'm like SO NEW at this UNIX stuff, furthermore the networking stuff....please help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 03:14 AM
11-24-2004 03:14 AM
Re: Communication Problems between Database Servers
And the route by ?
Since it was not configured on inland3 I believe it took the default:
200.200.120.1
Im looking at your 2 netconf files...
All the best
Victor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 03:20 AM
11-24-2004 03:20 AM
Re: Communication Problems between Database Servers
INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=200.200.120.8
SUBNET_MASK[0]=255.255.255.0
BROADCAST_ADDRESS[0]=200.200.120.255
INTERFACE_STATE[0]=down
DHCP_ENABLE[0]=0
I would comment out:
#INTERFACE_NAME[0]=lan0
#IP_ADDRESS[0]=200.200.120.8
#SUBNET_MASK[0]=255.255.255.0
#BROADCAST_ADDRESS[0]=200.200.120.255
#INTERFACE_STATE[0]=down
#DHCP_ENABLE[0]=0
And in the prod netconf
ROUTE_GATEWAY[0]="200.200.120.254" to:
ROUTE_GATEWAY[0]=""
All the best
Victor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 03:22 AM
11-24-2004 03:22 AM
Re: Communication Problems between Database Servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 03:29 AM
11-24-2004 03:29 AM
Re: Communication Problems between Database Servers
ROUTE_DESTINATION[1]="default"
ROUTE_MASK[1]=""
ROUTE_GATEWAY[1]="200.200.120.1"
ROUTE_COUNT[1]="1"
ROUTE_ARGS[1]=""
But check with your network guys what is the default gateway on you 200.200.120 network as the value I give is only what I think...
All the best
Victor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:00 AM
11-24-2004 04:00 AM
Re: Communication Problems between Database Servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:10 AM
11-24-2004 04:10 AM
Re: Communication Problems between Database Servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:14 AM
11-24-2004 04:14 AM
Re: Communication Problems between Database Servers
Well for sure not having the same default gateway on both sides didnt help, so since the production was correct (gateway) maybe by rebooting inland3 (test) now you did the coreections could help us see more clear and hopefully solve this issue, what do you think?
Check again you dont have strange char or dos2ux your files if so before.
What have you chosen - Keep lan1 up both sides?
Victor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:23 AM
11-24-2004 04:23 AM
Re: Communication Problems between Database Servers
Ok rebooted test (200.200.120.8) and I can now ping 200.200.120.8 from itself and I can also ping 200.200.120.3 (production) from test. I CANNOT however ping hostname INLAND3 (test) from itself...
On production I can ping 200.200.120.3 from itself and also I can ping inland8 hostname. I cannot however ping INLAND3 hostname from production. I can only ping the ip (200.200.120.8)
However when I do a uname -a on TEST (200.200.120.8) it says INLAND3 etc...
How come INLAND3 is not being recongnized on the network as hostname, can only see "IP address"??
please help...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:26 AM
11-24-2004 04:26 AM
Re: Communication Problems between Database Servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:28 AM
11-24-2004 04:28 AM
Re: Communication Problems between Database Servers
*** Warning - the local domain is not
*** Either hostname should be a domain
*** the domain should be specified in
*** or the shell variable LOCALDOMAIN
Name Server: inland7.irdbb.com
Address: 200.200.120.7
Trying DNS
Name: inland8
Address: 200.200.120.8
root:INLAND3>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:30 AM
11-24-2004 04:30 AM
Re: Communication Problems between Database Servers
ping -a 200.200.120.8
it reached the address but was showing as Inland3 and not INLAND3
Do I need to make this change in UNIX and then reboot again, if so where? Which file(s)? Only hosts?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:31 AM
11-24-2004 04:31 AM
Re: Communication Problems between Database Servers
From any server do nslookup INLAND3 then nslookup 200.200.120.3
Do they match?
What do you have in your /etc/hosts, beacuse if I remember right in nsswitch.conf you have files first
While you look at them I will try to think a bit...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:34 AM
11-24-2004 04:34 AM
Re: Communication Problems between Database Servers
what does netstat -rn show now on inland3?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:51 AM
11-24-2004 04:51 AM
Re: Communication Problems between Database Servers
Yes the output from the nslookup command match. I ran it on inland8 (200.200.120.3)
It does not matter that the hostname is INLAND3 as opposed to Inland3, just that I don't want to have to change it anywhere else now...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 04:59 AM
11-24-2004 04:59 AM
Re: Communication Problems between Database Servers
Trying DNS
Name: inland8
Address: 200.200.120.8
That is wrong, because inland8 is 200.200.120.3
Where can I change this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2004 06:09 AM
11-24-2004 06:09 AM
Re: Communication Problems between Database Servers
Its support/dispatch week for me ( you remember the phone?...) and its not easy to not get mixed up...
I had to leave my desk a moment...
The DNS is difficult to correct unless you are responsible of it...
So tell them to correct
What you can do is check that on both systems you have in nsswitch.conf:
hosts: files [NOTFOUND=CONTINUE] dns
dont add more for now so save the files you have: cp -p nsswitch.conf nsswitch.conf.last
meaning you will use /etc/hosts FIRST
AND in /etc/hosts put:
Hey didnt I ask you for you hosts file?...
For inland3:
127.0.0.1 localhost loopback
200.200.120.8 INLAND3 inland3 inland3.
for inland8:
127.0.0.1 localhost loopback
200.200.120.3 INLAND8 inland8 inland8.
Adrian I just realized werent the names given in relation with the IP?
ilnalnd3 should be 200.200.120.3 and inland8 200.200.120.8?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2004 12:25 AM
11-25-2004 12:25 AM
Re: Communication Problems between Database Servers
so production is hostname inland8 but ip is 200.200.120.3
test is hostname INLAND3 but ip is 200.200.120.8
i made change in hosts file. I cannot ping HOSTNAME only ip though...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2004 12:36 AM
11-25-2004 12:36 AM
Re: Communication Problems between Database Servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2004 12:36 AM
11-25-2004 12:36 AM
Re: Communication Problems between Database Servers
I would try to reinitialize the box name and IP
TO do this, use set_parms (do a man of set_parms before so you know what you will be asked)
Then reboot
And see if this changes anything
Give a try?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2004 12:38 AM
11-25-2004 12:38 AM
Re: Communication Problems between Database Servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2004 12:39 AM
11-25-2004 12:39 AM
Re: Communication Problems between Database Servers
domain .etatge.ch
nameserver
nameserver