Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1913893.1
Update Date:2018-01-25
Keywords:

Solution Type  Technical Instruction Sure

Solution  1913893.1 :   How to Clear DSR Alarm id 31233 - "HA Secondary Path Down"  


Related Items
  • BNS Platform Hardware
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
  •  




In this Document
Goal
Solution
 Switch of active ethernet interface


Created from <SR 3-9385312131>

Applies to:

BNS Platform Hardware - Version DSR 3.0 and later
Information in this document applies to any platform.

Goal

What is causing Alarm id 31233 - HA Secondary Path Down with errors on eth21 seen with "ifconfig" from TVOE host?

Solution

All steps should be performed via the TVOE host iLo and during a maintenance period.

Check both TVOE hosts for errors on eth21 or eth22:

[root@TVOE-a ~]# ifconfig
eth21     Link encap:Ethernet  HWaddr 80:C1:6E:75:AD:48
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:150554058 errors:8273623 dropped:0 overruns:8273623 frame:0
          TX packets:468425849 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:26773765106 (24.9 GiB)  TX bytes:580256217954 (540.4 GiB)
          Interrupt:32 Memory:fb000000-fb7fffff

Switch of active ethernet interface

Bring down the eth interface that has the errors which will cause the interfaces to switch activity. In this example eth21 and eth22 are bonded in bond1 and eth21 has errors. Perform the steps below via the TVOE host iLo:

  1. Verify stats and active interface of the bonding:
    # cat /proc/net/bonding/bond1
  2. Restart interface
    # ifdown eth21
    # ifup eth 21
  3. Verify stats of the bond again:
    # cat /proc/net/bonding/bond1

If the alarm 31233 does not clear then stop and reboot (init 6) the TVOE host server and verify interfaces come up with step 3.

Otherwise, return eth21 to active by performing following steps:

  1. Restart eth22 to force switchover:
    # ifdown eth22
    # ifup eth22
  2. Verify stats and active interface of the bonding
    # cat /proc/net/bonding/bond1

If the alarm 31233 returns after returning eth21 to active, repeat steps to move it back to eth22 and verify alarms cleared OR if eth21 fails to go active, then reboot (init 6) the TVOE host server and verify interfaces come up with "cat".


 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback