CP 1.07 ping failure from LD 117

[StinkTech]

Ping fails CP to switch and switch to CP. I can ping my admin pc (137.135.128.222) from the CP and vice-versa. No communications from the CP to the switch. All services on the CP (I200) in the services monitor show running except Multimedia Volume 2 and 3. Major Alarm in the event log EventID 7026 Desc: The following boot-start or system-start driver(s) failed to load: tandqic-SESFT

CP IP: 137.135.128.100/24
Switch IP: 137.135.128.253/24

Ran configuration on CP and verified 137.135.128.253 was the IP configured for the switch.

stat host
*** Active Internet Host Table ***
ID Hostname IP Address
-- localhost 127.0.0.1
-- PRIMARY_ENET 137.135.128.253
1 SECONDARY_ENET 137.135.128.254
2 LOCAL_PPP_IF 137.135.192.4
3 REMOTE_PPP_IF 100.1.1.1

prt host

Cabinet # 0
ID Hostname IP Address
1 SECONDARY_ENET 137.135.128.254
2 LOCAL_PPP_IF 137.135.192.4
3 REMOTE_PPP_IF 100.1.1.1


No database file exists for cab#1


No database file exists for cab#2


No database file exists for cab#3


No database file exists for cab#4

prt elnk
ACTIVE ETHERNET: "PRIMARY_ENET" "137.135.128.253"
INACTIVE ETHERNET: "SECONDARY_ENET" "137.135.128.254"
OK

=> prt mask
SUBNET MASK: "255.255.255.0"
OK

ping 137.135.128.253

PING 137.135.128.253 SUCCESSFUL

ping 137.135.128.100

PING 137.135.128.100 FAILED (CP)

LD 137
.stat elnk

ELNK ENABLED
Ethernet (qu unit number 0):
Host: PRIMARY_ENET
Internet address: 137.135.128.253
Broadcast address: 137.135.128.255
Ethernet address: 00:00:75:45:4f:df
Netmask: 0xffff0000; Subnetmask: 0xffffff00
0 packets received; 16 packets sent
0 input errors; 16 output errors
0 collisions

LD 48
.stat elan

SERVER TASK: ENABLED
ELAN #: 16 DES: ELAN
APPL_IP_ID: 0 .0 .0 .0 LYR7: DOWN DSBL


ADAN AML 9
CARD 10
PORT 1
DES
BPS 4800
CLOK EXT
IADR 003
RADR 001
T1 10
T2 002
T3 040
N1 128
N2 08
K 7
RXMT 05
CRC 10
ORUR 005
ABOR 005
ENL NO
ADAN ELAN 16
CTYP ELAN
DES ELAN
N1 512

EQ prt
TYPE vas

VAS
VSID 09
DLOP
AML 09
SECU NO
INTL 0001
MCNT 9999
CONF DIR
VSID 16
DLOP
ELAN 16
SECU NO
INTL 0001
MCNT 9999

Thanks in advance...
StinkTech

 

[tnphoneman]

Are the ELAN cables in the same ethernet switch? If not try that first. There is nothing wrong with the hardware if you can ping. If they are in the same switch try a different port.

Signature===========================================

http://www.greatwhitetechnologies.com

Aastra Authorized Reseller

 

[StinkTech]

This is an I200 doesn't it communicate with the switch via the backplane?

Thanks
StinkTech

 

[tnphoneman]

No not for call information. It requires an elan connection for the communications between the call server and callpilot. This is like an AML link was to meridian mail.

Signature===========================================

http://www.greatwhitetechnologies.com

Aastra Authorized Reseller

 

[StinkTech]

The manuals state the I200 connects to the ELAN via the CPE backplane...Are am I taking the statement (interfaces with the network loops through the IPE) wrong. They are referring to the voice channels not the ELAN?

Page 60 from CallPilot Planning and Engineering Guide

The IPE platform occupies two slots in the Meridian 1 IPE shelf and interfaces with the network loops through the IPE backplane. From the Meridian 1 switch perspective, the IPE platform appears logically equivalent to an XDLC. The IPE (200i) platform contains one embedded DSP. When two MPC-8 cards are inserted into the IPE platform's faceplate, 24 DS0 channels are supported.

 

[telebub]

Yes, that statement refers to its TNs, not the ELAN. The PBX should have a transceiver for its ELAN connectivity plugged into the ELAN switch. The CallPilot should also have an ELAN connection plugged into the ELAN switch.

War Eagle!
Lions Baseball '09!

 

[StinkTech]

Thanks...I'll get a transceiver for the switch. Thanks for all the help.

Thanks,
StinkTech