IP MEDPRO Error???? 2

[Naperguy1]

Port Mtce Alt Err Aux First Last Err Err Rt/ Al Ac
Name Name Type Data Occur Occur Cnt Rt Hr St

01B10 IPMEDPRO 3841 4283 02/15/12:46 02/28/ 255 0 1 a y
01B10 IPMEDPRO 3585 1 02/15/12:46 02/28/ 255 0 5 a y

The first error I looked into and it states it is not service affecting and no action is required. The second error (3585) I cannot find. The code is under DS1 MOs, but nothing for the IPMedPro. Anybody else experience this or is it nothing needing correcting? Thank you in advance.

Setup: S8700 (Multi-connect), Multivantage, CM 1.3

Naperguy1

 

[trobbo]

Hi There,

Have you checked the firmware version on the medpro?Depending on the HW version of the card 3 or 11 there have been several problems with medpro's in the past

 

[Naperguy1]

I did not check that. I will look into it. I know it is behind a few versions, though. Thanks, trobbo. Y'know, sometimes we all need a swift kick to look in another direction. Thanks.

Naperguy1

 

[manfmmd]

This is from: Maintenance Alarms for Avaya Communication Manager 2.2, Media Gateways and Servers....page 1352

Error Type 3585:

Aux Data = 1: The NIC parameters on the board do not match those in administration. Software is trying to negotiate the settings on the circuit pack to match the administered
settings. See the repair procedures for test #1511.

Aux Data = 2: The board is reporting different options than what is administered. Software tried to correct the options, but the board did not take the option update. See the repair procedures for test #1511.

Test #1511 (pg. 1354)

3585 FAIL

Aux Data = 1.

The board is reporting that it is running half duplex with
auto-negotiate . Communication Manager is trying to negotiate the settings on the circuit pack to match the administered settings and, under the above condition, it is logging a fault. It could be argued that this is a false alarm, especially if the link is operating correctly with no observable degradation of service. This capability (Test 1511) started with release R011i.03 1.531.0.

Note: Do not immediately replace the board for this fault. There is a mismatch between what is programmed in the board and administration on Communication Manager. CAT-3 wiring does not support 100Mbps data rates. Wiring between the backplane and router must be CAT-5 Follow these steps to attempt to resolve the problem.


1. Change the ethernet options. Set the speed to 100Mbps with full duplex. Set Auto (negotiate) to n. This should match the settings of the connected router. If the router does not have the same capabilities, you may have to adjust accordingly. The important thing is to make the media processor (TN2302) and the connected router match.

Command steps to accomplish changes to Communication Manager
administration.
a) Enter get ethernet-options location to determine current
settings, both administered and actual.
b) Enter change ip-interface location (Enable Ethernet Port
field to n) to turn off the interface. Submit the command to disable the interface.
c) Enter change ip-interface location change the Ethernet
Options fields as required. Submit the form.
d) Enter change ip-interface location (Enable Ethernet
Port field to y) to turn on the interface. Submit the command. to enable the interface.
e) Enter get ethernet-options location to verify that Ethernet options are the same in administration and on the board.

2. If service is normal and the alarm is causing concern, disable the test and escalate the problem.

 

[manfmmd]

For those that do not have the material yet:

Maintenance Alarms for Avaya Communication Manager 2.2, Media Gateways and Servers:

http://support.avaya.com/elmodocs2/comm_mgr/r2_2/pdfs/03_300190_3.pdf