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-72-2359249.1
Update Date:2018-02-14
Keywords:

Solution Type  Problem Resolution Sure

Solution  2359249.1 :   Diameter Signaling Router (DSR): Event_Number "10054 - Device Deployment Failed" For All Interfaces On IPFEs After Major Upgrade From 7.x to 8.x  


Related Items
  • Oracle Communications Diameter Signaling Router (DSR)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
  •  




In this Document
Symptoms
Changes
Cause
Solution


Created from <SR 3-16813363731>

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.0 and later
Tekelec

Symptoms

After Major upgrade from 7.x to 8.x, Customer started observing Alarm "10054 Device deployment failed" for all interfaces on IPFEs.

sev  ht    timeStamp                 event                    instance           errInfo
-*     0   05:09:00.620  Device deployment failed     eth0    editInterface call failed.
-*     0   05:09:01.051  Device deployment failed     eth1    editInterface call failed.
-*     0   05:09:01.472  Device deployment failed     eth2    editInterface call failed.
-*     0   05:09:01.745  Device deployment failed     eth3    editInterface call failed.
-*     0   05:09:02.122  Device deployment failed     eth4    editInterface call failed.

 

Changes

 Upgrade from DSR 7.x to DSR 8.x

Cause

This alarm will be raised automatically once the upgrade is done from 7.x to 8.x because the upgrade loader adds the flag "combinedChannels=max" in NetworkDeviceOption table. Due to this change, apwSoapServer tries to apply
the changed setting to the vNIC which fails and raises this alarm (i.e. 10054).

Solution

 To fix this issue, please follow the below steps:-

              STEP-1: Use the SSH command (on UNIX systems – or putty if running on Windows) to log into the active NOAM server:
              PROMPT> ssh admusr@<server address>
              password: <enter password>
              Answer yes if you are asked to confirm the identity of the server.

              STEP-2: Run following command:
              PROMPT> iset -fValue='' NetworkDeviceOption where "Keyword like 'ethtoolOpts'"

              STEP-3: Wait for 5 mins

              STEP-4: Run following command:
              PROMPT> iset -fValue='rx=4078' NetworkDeviceOption where "Keyword like 'ethtoolOpts'"

              STEP-5: Wait for 5 minutes and then verify that alarm is cleared

 


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