PBX ELAN won't Route Packets

[Panchanka]

G'Day,

A couple of weeks ago my OTM Server and my PBX (81C Rls 25.40b) stopped communicating. After closer inspection, I realized the PBX could not ping anything besides it default gateway (and the only reason it can ping that is because it is directly connected). The network folks have inspected it and they assure me it is not a network issue. Below is the info I gathered so far.

Any known issues about PBX not routing packets?

Thanks,

OTM server with 2 NIC’s. Source info below
Ethernet adapter Public LAN:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 172.16.123.71
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 172.16.122.4

Ethernet adapter Management LAN:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 172.16.121.71
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . :

C:\Documents and Settings\Administrator>

PBX ELAN. Destination info below
IP address 172.16.103.116
Subnet mask 255.255.255.240
Default Gateway 172.16.103.113

PBX Ethernet Info
=> prt elnk
ACTIVE ETHERNET: "PRIMARY_CORE0" "172.16.103.116"
INACTIVE ETHERNET: "SECONDARY_CORE1" "172.16.103.117"
OK

=> prt mask
SUBNET MASK: "255.255.255.240"
OK

=> prt host
ID Hostname IP Address
1 LOCAL_PPP_IF 137.135.192.4
2 REMOTE_PPP_IF 100.1.1.1
3 .255.255.0
4 PRIMARY_CORE0 172.16.103.116
5 SECONDARY_CORE1 172.16.103.117
6 GATEWAY 172.16.103.113
OK

=> prt route
ID Network Gateway
3 0.0.0.0 172.16.103.113
OK

.stat elnk

ELNK ENABLED
Ethernet (ln unit number 0):
Host: PRIMARY_CORE0
Internet address: 172.16.103.116
Broadcast address: 172.16.103.127
Ethernet address: 00:00:75:32:b0:8d
Netmask: 0xffff0000; Subnetmask: 0xfffffff0
29271 packets received; 42024 packets sent
0 input errors; 0 output errors
0 collisions
.

OTM is NOT able to reach the PBX IP
C:\Documents and Settings\Administrator>ping 172.16.103.116

Pinging 172.16.103.116 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 172.16.103.116:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

OTM is able to reach the PBX Gateway
C:\Documents and Settings\Administrator>ping 172.16.103.113

Pinging 172.16.103.113 with 32 bytes of data:

Reply from 172.16.103.113: bytes=32 time=2ms TTL=249
Reply from 172.16.103.113: bytes=32 time=2ms TTL=249
Reply from 172.16.103.113: bytes=32 time=1ms TTL=249
Reply from 172.16.103.113: bytes=32 time=1ms TTL=249

Ping statistics for 172.16.103.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

The PBX is able to reach its Gateway
ping 172.16.103.113

PING 172.16.103.113 SUCCESSFUL

The PBX is not able to reach either IP address of the OTM server

=> ping 172.16.123.71

PING 172.16.123.71 FAILED

=> ping 172.16.121.71

PING 172.16.121.71 FAILED

 

[captaingadget]

Judging by the IP addresses looks like the OTM and PBX are on different sub nets. The sub net masks are a clue here.

 

[Panchanka]

Yes they are on different subnets, they are also in different buildings. there are routers in between that are routing the traffic between subnetworks.

 

[captaingadget]

I know you say the network people have checked this out, but clearly if you can't even ping then one of the routers is not forwaring packets.

Are the ELANs in the same VLAN? Your gonna have to lean on your network people.

 

[Panchanka]

I partnered with the network guys yesterday and togther we fixed it. It was a PBX issue afterall. Here is specifically what I did to resolve it incase you come across the issue. If you "stat route" in ld 117 the ID column showed none active even if you manually put one in. you have to "enl route <route ID>" before it will show in the stat route.
=> stat route
*** Active Internet Routing Table ***
ID Network Gateway
-- 172.16.103.112 172.16.103.116
-- 127.0.0.1 127.0.0.1
-- 172.16.103.113 172.16.103.113

=> prt route
ID Network Gateway
263 0.0.0.0 172.16.103.113
OK

=> enl route 263
ROUTE: "0.0.0.0" "172.16.103.113" enabled
OK

=> stat route
*** Active Internet Routing Table ***
ID Network Gateway
263 0.0.0.0 172.16.103.113
-- 172.16.103.112 172.16.103.116
-- 127.0.0.1 127.0.0.1
-- 172.16.103.113 172.16.103.113

=> ping 172.16.101.129

PING 172.16.101.129 SUCCESSFUL

 

[captaingadget]

Well done. We learn something every day!!