I have 4 OXE systems connected in network through ABCF on NPRAE. Earlier I was able to access any of these systems directly through telnet + tunnel IP ommand and also from OMNIVISTA. But now I can not access any of these system through their tunnel IP. It is possible to access the system directly through Stastic IP of the system via E0 or E1 port on CBRMA. I have also checked in netadmin- security, but trusted host option is not configures, which means it is open.
Suggesion is highly appreciated.
OXE in Network on 2MBPS links not accessible
-
Gedeon
Re: OXE in Network on 2MBPS links not accessible
Check IP/X25 configuration in netadmin for all nodes.
By default, the subnet is 172.30.NETWORK.NODE (with 253 for NETWORK and NODE 0).
And the subnet mask must be 255.255.0.0
If telnet is possible from a CPU to another CPU, you can have problem with an external connexion (from PC connected to eth0 on a CPU). In this case, you must created static routes on OXE with CPU as routeur, or if your ABC network is not connected on client LAN (I suppose that is not the case), you can use RIP protocol to create dynamic routing rules (see netadmin, choice
.
G.
By default, the subnet is 172.30.NETWORK.NODE (with 253 for NETWORK and NODE 0).
And the subnet mask must be 255.255.0.0
If telnet is possible from a CPU to another CPU, you can have problem with an external connexion (from PC connected to eth0 on a CPU). In this case, you must created static routes on OXE with CPU as routeur, or if your ABC network is not connected on client LAN (I suppose that is not the case), you can use RIP protocol to create dynamic routing rules (see netadmin, choice
.G.
-
AJESH
Re: OXE in Network on 2MBPS links not accessible
Dear Gedeon,
Thanks for your reply.
I am attaching a pictorial view of the network for your reference and further suggestions.
For your info, RIP is already activated in all CPU's.
Thanks for your reply.
I am attaching a pictorial view of the network for your reference and further suggestions.
For your info, RIP is already activated in all CPU's.
You do not have the required permissions to view the files attached to this post.
-
AJESH
Re: OXE in Network on 2MBPS links not accessible
Dear Gedeon,
After seeing the attachment, would you like to suggest some solution please.
After seeing the attachment, would you like to suggest some solution please.
Re: OXE in Network on 2MBPS links not accessible
In this configuration you need:
PC - decleare GW - 179.29.4.3 (Node 4).
Node 1 - 3 - decleare static route for host 179.29.4.60 with GW 172.30.1.4
PC - decleare GW - 179.29.4.3 (Node 4).
Node 1 - 3 - decleare static route for host 179.29.4.60 with GW 172.30.1.4
-
AJESH
Re: OXE in Network on 2MBPS links not accessible
Dear Vad,
Thanks for the solution.
I would update the ip addessing according to your suggession and revert back.
Thanks for the solution.
I would update the ip addessing according to your suggession and revert back.
-
Gedeon
Re: OXE in Network on 2MBPS links not accessible
Sorry, not connected for a moment.
VAD's solution is the good solution IMHO.
In IP/X25, you can also have a specific case if you network ling is managed with static routage (on ABC-Link configuration).
In this case, (for dynamic links) the IP/X25 tunnel is not permanently up. And the Tunnel can't established the link.
You can modify this state with Applications rights in X25 to authoeize Tunnel to open the link. But, if your link is on B channel, the cost of communication must be more expansive.
G.
VAD's solution is the good solution IMHO.
In IP/X25, you can also have a specific case if you network ling is managed with static routage (on ABC-Link configuration).
In this case, (for dynamic links) the IP/X25 tunnel is not permanently up. And the Tunnel can't established the link.
You can modify this state with Applications rights in X25 to authoeize Tunnel to open the link. But, if your link is on B channel, the cost of communication must be more expansive.
G.
