Home » Infrastructure » Unix » Telnet 192.168.253.98 5000 gives connection refused
| Telnet 192.168.253.98 5000 gives connection refused [message #629937] |
Wed, 17 December 2014 21:31  |
 |
alibobo
Messages: 1
Registered: December 2014
Location: Vietnam
|
Junior Member |
|
|
Hi,
I am handling one customer issue that really difficult for me. Could anyone take a look at below description and help me to find out what reason is? Thanks in advance.
the official ip address of the OMC Splat is 10.13.0.61:
==============================================================================================================================
# grep omc_splat /etc/hosts
1. 10.13.0.61 omcnor1 omcnor1.localdomain omc_splat omc_4gl omc_pm loghost
==============================================================================================================================
But there are other ip addresses associated to this server because there are some external entities that should be connected to this server:
==============================================================================================================================
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.13.0.61 netmask ff000000 broadcast 10.255.255.255
ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 172.50.53.61 netmask ffffff00 broadcast 172.50.53.255
ce0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.253.98 netmask fffffff8 broadcast 192.168.253.103
ce0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.12.61 netmask ffffff00 broadcast 192.168.12.255
ce0:4: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.12.62 netmask ffffff00 broadcast 192.168.12.255
==============================================================================================================================
One of those entities is the Customer Optimization Department Server (CODS) that use the ip address 192.168.253.98.
The CODS entity every day collect PM data and send it as normal text files using ip address 192.168.253.98 and after they upload the files to their database.
They everyday use the ip address 192.168.253.98 and they can ping it from their server.
Now, the CODS entity has changed their platform and need to automatically connected to our PM database using ip address 192.168.253.98 and port 5000.
The problem now is that:
• If we want to use telnet with port 5000 we should absolutely use one of the omc_splat ip addresses or its associated host names:
10.13.0.61, omcnor1, omcnor1.localdomain, omc_splat, omc_4gl, omc_pm or loghost
=======================================================================================================================
omcsud2{metrica} #: telnet omcnor1 5000
Trying 10.13.0.61...
Connected to omcnor1.
=======================================================================================================================
• But CODS can only connect to omc_splat using ip adress 192.168.253.98!
=======================================================================================================================
13:30:38-mycom@MycomProduction01:~$ telnet 192.168.253.98 5000
Trying 192.168.253.98...
telnet: connect to address 192.168.253.98: Connection refused
=======================================================================================================================
• Port 5000omc_splat10.13.0.61omcnor1, omcnor1.localdomain, omc_splat, omc_4gl, omc_pm or loghost)
=======================================================================================================================
omcnor1:omcadmin > grep 5000 /etc/services
inf7_OMC_serv 5000/tcp # OMC database Informix DSA instance
omcnor1:omcadmin > cat /usr/informix/etc/sqlhosts
demo_on onipcshm on_hostname on_servername
demo_se seipcpip se_hostname sqlexec
omcnor1:omcadmin > cat /usr/informix/etc/sqlhosts_OMC
omc_sys1 onipcshm omc_splat 60k_OMC_shm
omc_sys ontlitcp omc_splat inf7_OMC_serv
omc_mib ontlitcp omc_splat inf7_MIB_serv
mcOMC010013000061 ontlitcp omcnor1 mcOMC
omcnor1:omcadmin > grep -i dbserver /usr/informix/etc/onconfig_OMC
DBSERVERNAME omc_sys1 # Name of default database server
DBSERVERALIASES omc_sys,mcOMC010013000061 # List of alternate dbservernames
omcnor1:omcadmin > cat /usr/omc/current/config/sqlhosts
omc_sys1 onipcshm omc_sys Inf7_serv1
omc_sys ontlitcp omc_sys Inf7_serv
omcnor1:omcadmin > cat /usr/omc/current/config/SF4800_etc_services_SPLAT
inf7_OMC_serv 5000/tcp # OMC database Informix DSA instance
inf7_MIB_serv 5010/tcp # MIB database Informix DSA instance
mcOMC 5030/tcp # Multiple Connect - OMC PR138598
mcMIB 5040/tcp # Multiple Connect - MIB PR138598
=======================================================================================================================
What's required now is:
• Enable telnet5000192.168.253.98, but the OMC functionalities use the ip address 10.13.0.61, omc_splat and omcnor1.
Or:
• Create new port(s) (Ex: 9088/9089) associated to 192.168.235.98 to be used by CODS;
I have already prepare one procedure and I need to confirm the impact on the OMC functionalities and if there is any missing thing:
=======================================================================================================================
# Add the following entries to /etc/services:
MT_sqlexec_OMC 9088/tcp # OMC database Informix DSA instance For CODS
MT_sqlexec-ssl_OMC 9089/tcp # OMC database Informix DSA instance For CODS
# Add the following entries to /usr/informix/etc/sqlhosts_OMC, /usr/omc/current/config/SF4800_etc_services_SPLAT:
mt_sqlexec_1 ontlitcp 192.168.253.98 MT_sqlexec_OMC
mt_sqlexec_2 ontlitcp 192.168.253.98 MT_sqlexec-ssl_OMC
# change in /usr/informix/etc/onconfig_OMC:
DBSERVERALIASES omc_sys,mcOMC010013000061 # List of alternate dbservernames
# By
DBSERVERALIASES omc_sys,mcOMC010013000061,mt_sqlexec_1,mt_sqlexec_2 # List of alternate dbservernames
# But i don't know what's the impact of the add of those ports on the sqlexec process that is running on the splat:
omcnor1:omcadmin > cat /usr/informix/etc/sqlhosts
demo_on onipcshm on_hostname on_servername
demo_se seipcpip se_hostname sqlexec
# Because the port 9088 usally is associated to sqlexec service and 9089 to sqlexec-ssl service.
=======================================================================================================================
-
Attachment: LOG.txt
(Size: 28.00KB, Downloaded 3882 times)
|
|
|
|
|
|
|
|
| |
  |
Goto Forum:
Current Time: Thu Nov 21 07:28:49 CST 2024
|
] 
Blog
Search
Help
Members
Register
Login
Home
