Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Signaling Server can't find Call Server

Status
Not open for further replies.

Arriero

Technical User
Oct 25, 2009
30
CL
Hello,

I am having issues communicating the Sig Server to the Call Server.

- Ping from SS ELAN to Call Server ELAN does not respond
- Ping from my laptop (on ELAN) to SS ELAN is successful
- Ping from my laptop (on ELAN) to CS ELAN is successful

When I look at the route table on my Signaling Server I get the following information:

oam> routeShow

ROUTE NET TABLE
destination gateway flags Refcnt Use Interface
----------------------------------------------------------------------------
0.0.0.0 192.168.1.1 33619971 1 0 fei1
47.1.1.0 47.1.1.20 33554689 5 0 fei0
192.168.1.0 192.168.1.5 33554689 4 0 fei1
----------------------------------------------------------------------------

ROUTE HOST TABLE
destination gateway flags Refcnt Use Interface
----------------------------------------------------------------------------
10.2.16.233 192.168.1.1 33685511 1 3 fei1
127.0.0.1 127.0.0.1 35651589 1 2 lo0
----------------------------------------------------------------------------

My ELAN is 47.1.1.0/24 and TLAN is 192.168.1.0/24
SS ELAN is 47.1.1.20 and SS TLAN is 192.168.1.5

System is CS1000M-MG R5.5

Any ideas on why do I have this 10.2.16.233 address in my SS route host table?

Thanks
 
the 10.2.16.233 may be your laptop.

Make sure you have a default route in your Call Server.

In LD 117 you should have something like

Code:
ld 117
OAM000

=> prt rout
Call Server 
 ID  Network          Gateway   
  1  0.0.0.0          172.21.102.254   
  2  172.21.102.0     172.21.102.11

In this example, my CallServer is 172.21.102.11, my default gateway is 172.21.102.254. and I use a 24-bit mask (255.255.255.0)

So anything not in 172.21.102.0 will be sent to the default gateway, and anything in 172.21.102.0 will be sent out through the E-LAN interface.
 
Hmmm... There all on the same subnet... so route does not matter. If what your telling us is correct I would look at a possible bad Ethernet Switch port/s. It should not be behaving as you stated above.

Bryan J Miles
Systems Engineer
Service Communications, Inc.
 
Can you ping the SS E-LAN from the Call Server? I didn't see if you had tried this from the original post.

It definitely sounds like it could be network related as you can ping both e-lan interfaces from a third device.

Anyway, here are the route tables from 2 of my leader signaling servers for comparison - maybe it will be helpful:



SITE A CS1000e (rls 5.0) HP COTS sig server (rebooted 1.5 hours ago)

ROUTE NET TABLE
destination gateway flags Refcnt Use Interface
----------------------------------------------------------------------------
0.0.0.0 172.20.13.254 33619971 4 528 bcm1 <--- Unclassed routing to T-LAN default gateway
172.20.13.0 172.20.13.13 33554689 11 0 bcm1 <--- T-LAN subnet via T-LAN interface
172.20.13.0 172.20.13.253 257 0 0 bcm1 <--- T-LAN subnet via node-IP (not sure why this is here)
172.21.13.0 172.21.13.13 33554689 4 0 bcm0 <--- E-LAN subnet via local E-LAN interface
----------------------------------------------------------------------------

ROUTE HOST TABLE
destination gateway flags Refcnt Use Interface
----------------------------------------------------------------------------
10.1.10.79 172.20.13.254 33947655 0 254 bcm1 <--- NetIQ SNMP monitoring
10.102.31.16 172.20.13.254 33685511 1 361 bcm1 <--- My Laptop
127.0.0.1 127.0.0.1 35651589 2 17 lo0 <--- loopback
172.20.5.10 172.21.13.254 33554439 1 91 bcm0 <--- NetIQ Performance Agent at remote office via E-LAN default gateway
172.20.13.253 172.20.13.253 35651589 0 1 lo0 <--- Local office Node-IP via Local office Node-IP (not sure why this is here either)
----------------------------------------------------------------------------


SITE B CS1000e (rls 5.5) ISP1100 sig server in service for several months

ROUTE NET TABLE
destination gateway flags Refcnt Use Interface
----------------------------------------------------------------------------
0.0.0.0 172.20.4.254 33619971 8 309429 fei1 <--- Unclassed routing via T-LAN default gateway
172.20.4.0 172.20.4.13 33554689 55 0 fei1 <--- local T-LAN subnet via T-LAN interface
172.20.4.0 172.20.4.253 257 0 0 fei1 <--- local T-LAN subnet via node-IP
172.21.4.0 172.21.4.13 33554689 3 0 fei0 <--- local E-LAN subnet via E-LAN interface
----------------------------------------------------------------------------

ROUTE HOST TABLE
destination gateway flags Refcnt Use Interface
----------------------------------------------------------------------------
10.1.10.79 172.20.4.254 33947655 0 309287 fei1 <--- NetIQ SNMP monitoring
10.102.31.16 172.20.4.254 33685511 1 309460 fei1 <--- Me again.
127.0.0.1 127.0.0.1 35651589 2 17 lo0 <--- loopback
172.20.5.10 172.21.4.254 33554439 1 32647 fei0 <--- NetIQ performance agent at remote office via E-LAN default gateway
172.20.8.253 172.20.4.254 33685511 1 308627 fei1 <--- remote office Node-IP via T-LAN gateway
172.20.102.14 172.20.4.254 33685511 1 52525 fei1 <--- remote office sig server via T-LAN default gateway
172.20.102.16 172.20.4.254 33685511 1 78916 fei1 <--- Primary NRS via T-LAN interface
172.20.102.253 172.20.4.254 33685511 2 24031 fei1 <--- Remote office Node-IP via T-LAN default gateway
172.20.112.253 172.20.4.254 33685511 2 13079 fei1 <--- Remote office Node-IP via T-LAN default gateway
----------------------------------------------------------------------------

I can ping all devices from every other device.
 
Allenmac, thanks for your feedback. The Call Server IP info looks as follows:

>ld 117
OAM000

=> prt host
ID Hostname IP Address
1 CS_PRIM 47.1.1.11
2 CS_SEC 47.1.1.12

=> stat host
*** Active Internet Host Table ***
ID Hostname IP Address
-- localhost 127.0.0.1
1 CS_PRIM 47.1.1.11
2 CS_SEC 47.1.1.12

=>
AUD000
prt rout
ID Network Gateway
2 0.0.0.0 47.1.1.1
OK

=> stat rout

*** Active Route Net Table ***
ID Network Gateway
-- 0.0.0.2 47.1.1.11
-- 35.35.40.0 35.35.40.1
-- 35.35.40.128 35.35.40.129
-- 35.35.41.0 35.35.41.1
-- 35.35.41.128 35.35.41.129
-- 127.0.0.0 127.2.0.2

*** Active Route Host Table ***
ID Network Gateway
-- 127.0.0.1 127.0.0.1

I connected my laptop on 47.1.1.190 and from there I can ping SS-ELAN and CS-ELAN, however CS-ELAN doesn't see SS-ELAN and vice versa... that is what puzzles me.

I am still intrigued with the 10.2.16.233 address... don't have a clue where it may come from.
 
On your active route table, the first entry is 0.0.0.2 - shouldn't that be 0.0.0.0?

It looks like you need to enable rout 2 - in LD 117 the command is: enl rout 2.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top