CMS Ethernet inteface problem

[Smovk]

I`m new to Sun.
We have Sun Sollaris 10 on netra 210 runing CMS 14.1 with two interfaces, one is connected to Avaya PBX (link is fixed to 10Mbps HalfDuplex, because this C-Lan hardware on Avaya PBX is old card and it does not support any other speed) and second interface is connected to LAN.
Till couple of days ago everything was working fine and without any errors in log files. Couple of days ago someone accidentally turned power off for all our equipment.
When system had rebooted, interface bge0 (connected to Avaya directly) on Sun is getting down and back up every few hour.

this is what we have in /var/adm/messages
Nov 24 00:20:04 0842TFI050 bge: [ID 801593 kern.notice] NOTICE: bge0: link down
Nov 24 00:20:24 0842TFI050 bge: [ID 801593 kern.notice] NOTICE: bge0: link up 10
Mbps Half-Duplex
Nov 24 01:20:15 0842TFI050 bge: [ID 801593 kern.notice] NOTICE: bge0: link down
Nov 24 01:20:35 0842TFI050 bge: [ID 801593 kern.notice] NOTICE: bge0: link up 10
Mbps Half-Duplex
Nov 24 02:49:25 0842TFI050 bge: [ID 801593 kern.notice] NOTICE: bge0: link down
Nov 24 02:49:45 0842TFI050 bge: [ID 801593 kern.notice] NOTICE: bge0: link up 10
Mbps Half-Duplex

can you help, I do not know what is wrong. I change cables, and also equipment on Avaya PBX, and every time is the same result

 

[4merAvaya]

I would try doing a graceful shutdown & reboot on the CMS. Use the command 'shutdown -y -g0 -i6'. This will log everyone out and kill the PBX link so it has to be done off-hours.

The addresses used by the NICs are defined in the /etc/hosts file. The rest of the IP files are located in the /etc/inet directory.

Kevin

 

[Smovk]

I made shutdown procedure, but interface is still going down and back up every few hours, interface speed is fix to 10 Mbps halfduplex.

 

[billybobdan]

Just a thought.

As it sounds like you have the CMS directly connected to the Clan via a cross over cable, Have you checked the alarm log history in the PABX. The clan may be restarting. The link is down for 20 secs each time. This about the same amount of time a clan takes to restart.

 

[Smovk]

CMS is now connected directly to C-Lan,but this error has occurred even if it was connected to hub or switch and then to C-Lan.

 

[Smovk]

During this weekend I changed hardware on PBX so that it is capable 100Mbps Fullduplex. When I fixed 100 Mbps FD on PBX site and on Sun using command:
ndd -set /dev/bge0 adv_100fdx_cap 1
ndd -set /dev/bge0 adv_100hdx_cap 0
ndd -set /dev/bge0 adv_10fdx_cap 0
ndd -set /dev/bge0 adv_10hdx_cap 0
ndd -set /dev/bge0 adv_autoneg_cap 0
then I did not had any Ethernet connection between.
When I set Sun server back to autonegotiation and PBX site to 100Mbps FullDuplex, Sun server connected to 100Mbps Half Duplex. When I set both site to autonegotiation, both sites were connected with 100 Mbps FullDuplex.

This two boxes are directly connected with cable without any switch between.

Ethernet link is now stable even if it is autonegotiated to 100Mbps FullDuplex, but in CMS I can still find out from time to time that data collection session is down and back up. Error code in CMS is still 1400, but in Sun log
/var/adm/messages there is no more errors.

Any idea why is this happening?

 

[kpearlt3]

Can you post any errors you are getting on the PBX side of the configuration?

 

[Smovk]

I change the switch between PBX and CMS, so SUN server(CMS) and C-LAN are now connected with forced 100Mbps Fulduplex.
Now Ethernet link is stable, on C-Lan I do not have any errors (everything is empty for active errors and for cleard errors - I used display error command in SAT), there is no error in Solaris error log /var/adm/messages for interface bge0 going down and back up. In CMS error log under maintenance menu I still have error code 1400 SPI session errorata collection session is down.

I found error in spi_err_1 log (in attached file). In attached file are file spi_err_1 and /var/adm/messages. I could not found any errors in /var/adm/messages for the time when error occurred in spi_err_1 log.

Can some one help wit this?

 

[multibus2]

Wed Dec 2 17:02:54 [12] SESS bad sequence, 82 received, 81 expected" means as it says the CMS was told to expect 81 application packets of data but 82 were received. Note: these are not TCP packets rather they are CMS application packets.

I would check the firmware on the CLAN and make sure it is current. Also as this is a crossover cable connection between the CMS and the CLAN, both the CMS NIC and CLAN should be left in auto-negotiate mode. If they are connected via a ethernet switch then this rule does not apply.