IVD Error messages - VoIP / PBX Info Forum for Avaya / Nortel, Cisco, ShoreTel, Panasonic and other manufactuers Tech Tips Community

March 12th, 2004

This morning, a couple of users on the same digital card complainted that they M2616's were dead. I logged on to reset their ports, and got a stream of undocumented error messages. The stream doesn't end when the digital card is disabled.

Does anyone have an idea of what this message means? How important is it? "IVD 000 OUT xxxxxxxxx xxxxxxxxx xxxxxxxxx xxxxxxxxx"

The four hex fields (xxxxxxxxx) that follow that message do change, so I haven't included them here.

Regards,
Gord Hewit

RogerHutch · March 13th, 2004

Not sure what the IVD is. I am familiar with OVD. Did you try swapping or actually reseating the card?

Roger

March 13th, 2004

No, reseating the card was not necessary. An INI solved the problem.

**Fletch** · March 17th, 2004

I have seen that in the past. Messages come out with an 'odd' character in the message. IOV instead of IOD, etc.

Before you INI the next time, you may want to have your vendor jump into the back end of the PBX and look at the memory and call registers to see if you have a memory leak.

If it is a leak, an INI will clear it, but it's really just masking the problem.

March 17th, 2004

Fletch;

Thanks for the suggestion, I will have the maint. co. look into this. The problem isn't just one error message that's wrong, but the entire stream. Every message is IVD, not OVD. And the stream goes on until you INI. But your're right, it does sound like a memory leak type problem.

It happened again this morning, after I connected one specific set. I'm suspicious of the set, and will likely replace it if this ever occurs again.

Thanks,
Gord.

**Fletch** · March 17th, 2004

I have seen this specific one before, just can't remember the details on it.

March 23rd, 2004

Fletch;

The problem continued, and shows up every morning. Our M1 tech was in and had to do a power off / on sequence. The reboot did show a database problem on an unused TN.

% SYS000 000400 000000 000000 000000 CPU 0
% SYSDB RLS/ISS: 2335 LOADED FROM C: DATE/TIME: 22/3/2004 11:59:04 RECS: 161 SEQ
------
% SYSLOAD RELEASE 23.35
% SYS4311 TN 20 0 0 2
% **PROBLEMS FOUND.**

So we are now sure that we are dealing with a corrupted database. I will post a final result, if I ever get one. Today, I can't do an EDD (EDD016, "No Go, Bad Data").

Regards,
Gord Hewit

**Fletch** · March 24th, 2004

To clear the Backup problem, do an EDD CLR in LD 43. That should get you back on track.

March 29th, 2004

So the final result is a conclusion that the problem was due to database corruption. I 'fixed' the corruption by readng the SYS messages from the system boot, and adding a set to the TN that was causing the problem. As Fletch mentioned, the EDD CLR command then allowed me to do a backup. No error messsages since then.

I'm also wondering if our occasional bout of AUD335 messages were caused by the same database corruption problem.

Thanks Fletch, and thanks to everyone else who submitted possible solutions.

Regards,
Gord Hewit

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)