> I see "san2: LCP keepalive timeout" output to the console and the below > in /var/log/messages right around when it locked up but the traces don't > seem to have anything to do with the network. > > Jun 21 06:05:05 rrlhcrtr0200 /bsd: san3: T1 YELLOW ON > Jun 21 06:05:05 rrlhcrtr0200 /bsd: san3: T1 disconnected! > Jun 21 06:05:05 rrlhcrtr0200 /bsd: san3: Link connecting... > Jun 21 06:40:56 rrlhcrtr0200 syslogd: start > > Jun 21 07:15:44 rrlhcrtr0200 /bsd: san3: T1 LB activation code received. > Jun 21 07:15:44 rrlhcrtr0200 /bsd: san3: Unknown signal (15). > Jun 21 07:15:59 rrlhcrtr0200 /bsd: san3: T1 LB deactivation code received. > Jun 21 07:16:04 rrlhcrtr0200 /bsd: san3: T1 LB deactivation code received. > Jun 21 07:16:08 rrlhcrtr0200 /bsd: san3: Unknown signal (09). > Jun 21 07:16:08 rrlhcrtr0200 /bsd: san3: Unknown signal (15). > Jun 21 07:16:15 rrlhcrtr0200 /bsd: san2: T1 LB activation code received. > Jun 21 07:16:15 rrlhcrtr0200 /bsd: san2: Unknown signal (15). > Jun 21 07:16:39 rrlhcrtr0200 /bsd: san2: T1 LB deactivation code received. > Jun 21 08:08:49 rrlhcrtr0200 syslogd: start > > Jun 21 09:26:53 rrlhcrtr0200 /bsd: san2: T1 AIS ON > Jun 21 09:26:53 rrlhcrtr0200 /bsd: san2: T1 disconnected! > Jun 21 09:26:53 rrlhcrtr0200 /bsd: san2: Link connecting... > Jun 21 09:26:54 rrlhcrtr0200 /bsd: san2: T1 RED ON > Jun 21 09:30:51 rrlhcrtr0200 syslogd: start > > Jun 21 09:39:51 rrlhcrtr0200 /bsd: san2: T1 AIS ON > Jun 21 09:39:51 rrlhcrtr0200 /bsd: san2: T1 disconnected! > Jun 21 09:39:51 rrlhcrtr0200 /bsd: san2: Link connecting... > Jun 21 09:39:52 rrlhcrtr0200 /bsd: san2: T1 RED ON > Jun 21 09:50:21 rrlhcrtr0200 syslogd: start > Jun 21 09:50:21 rrlhcrtr0200 syslogd: start
Sangoma has made it pretty clear (by ignoring problem reports from our developers) that they don't care at all. I suggest you call them, and add your voice there. Otherwise, I suggest that everyone running Sangoma projects learn from this experience...
