Asset ID: |
1-72-2183772.1 |
Update Date: | 2016-09-21 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2183772.1
:
Alarm 32513 - Device Interface Warning
Related Items |
- Oracle Communications Policy Management
|
Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec Policy
|
Alarm generated when bonded interface is active on its non-primary interface. clear with 'ifenslave -c' command
In this Document
Created from <SR 3-13207182351>
Applies to:
Oracle Communications Policy Management - Version POLICY 9.1.7 to POLICY 12.1.2 [Release POLICY 9.0 to POLICY 12.0]
Information in this document applies to any platform.
Symptoms
The Policy Management system has active alarm 32513 - Device Interface Warning
Changes
This may be triggered by a change in link state of one of the interfaces in the bond.
Cause
The bonds on the policy server are running in active / backup mode and will failover to the backup link in the event of a link failure. Syscheck is sensitive to the status of The bond, and will generate an alarm when the link is not using its designated "Primary Slave" interface.
To check the status of the bond, use the command
# cat /proc/net/bonding/bond where x is the bond number
In the case below, bond1, has a designated "Primary Slave" of eth02, but the "Currently Active Slave" is eth12
EXAMPLE
[root@linux denlab-mper]# cat proc/net/bonding/bond1
Ethernet Channel Bonding Driver: v3.4.0-1 (October 7, 2008)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth02 (primary_reselect failure)
Currently Active Slave: eth12
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth02
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: ac:16:2d:77:ff:39
Slave Interface: eth12
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: ac:16:2d:80:d5:02
------------------------------------
Solution
To set the bonded interface back to using its designated "Primary Slave" use the linux command 'ifenslave'
# ifenslave {-c|--change-active} bond0 eth0
there is help available, but in this case the exact command is
# ifenslave -c bond1 eth02
after the command if you cat /proc/net/bonding/bond1 you will find that the "Primary Slave" and "Currently Active Slave" are the same:
[root@linux denlab-mper]# cat proc/net/bonding/bond1
Ethernet Channel Bonding Driver: v3.4.0-1 (October 7, 2008)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth02 (primary_reselect failure)
Currently Active Slave: eth02
MII Status: up
MII Polling Interval (ms): 100
Attachments
This solution has no attachment