Bhaskara,

FYA.


Regards,
Krishnakumar Pazhore
Asia Pacific Processing Center
Citibank N.A.
Tel :  (65) - 64262474
Fax:  (65) - 64262270
--------------------------------------------------------------------------------------------------------------------------------
This e-mail is confidential and may also be privileged. If you are not the intended recipient please notify us immediately, you should not copy or use it for any purpose, nor disclose its contends to any other person.
---------------------------------------------------------------------------------------------------

 


-----Original Message-----
From: Gudimella, Udaya 
Sent: Monday, October 30, 2006 8:57 AM
To: Vathsavai, Bhaskara R; Vathsavai, Krishnam; Trivedi, Niket;
Krishnakumar, Pazhore
Cc: *GT AP APPC MRTECH-SUN OPS
Subject: FW: Clarify Case ID 3827545 ACSLS - Passowrd Change fix.
Importance: High


Hi Storage Team. 

Please help to raise a INFOMAN to check and fix this in ssunacs2 & ssuancs4 and let me know the schedule for the same. 


 Regards
Udaya Kumar Gudimella
Asia Pacific Processing Center,
5, Tampines Central 1,
#07-01, Tampines Plaza,
Singapore 529541
email:udaya.gudimella@citigroup.com
(65)6-426-2679 (Phone)
(65)6-426-2270 (Fax)
Group email:- <mailto:gtapappcmrtechsunops@imcnam.ssmb.com>

-----Original Message-----
From: Suhari, Jamin Abdullah [mailto:jamin.suhari@sun.com]
Sent: Sunday, October 15, 2006 6:18 AM
To: Gudimella, Udaya
Cc: Siah, Patrick; Reyes, Salvemarie F (Salve); Krishnakumar, Pazhore;
Trivedi, Niket; Vathsavai, Bhaskara R; Vathsavai, Krishnam
Subject: FW: Clarify Case ID 3827545
Importance: High


Hi Udaya,

Below is the feedback from ACSLS backline engineer pertaining to the ACSLS password problem in your environment. Tier3 engineer was unable to reproduce the problem as all password change scenarios were successful. 
I would appreciate if you could perform the password change again on the system with no NIS+ as per Tier3 recommendation below and if you encounter the same problem, immediately run the get_data.sh script to collect the current logs and send it to me for further investigation. 


Jamin Abdullah Suhari
Storage Consultant - Storage Group   

Sun Microsystems Malaysia Sdn Bhd.
Phone + 603 2116 1888
Mobile + 6019 326 1140
Email jamin.suhari@sun.com
 



Jamin,

I could not recreate the problem.  This is what I did:
1.  Lock informix and lib6 passwords using "passwd -l <user_id>" command.
2.  Reset acsss and acssa passwords while ACSLS is running.
3.  Run cmd_proc commands that reads the database ( query commands ) and 
the "set owner" command to test database writes.
4.  Reset acsss and acssa passwords again while ACSLS is running.
5.  Run the same commands as in step 3.
6.  Stopped ACSLS; but did not stop the database
7.  Reset acsss and acssa passwords while ACSLS is stopped. Restarted 
ACSLS successfully.
8.  Run the same commands as in step 3.
7.  Reset acsss and acssa passwords again  while ACSLS is running.
9.  Run cmd_proc commands successfully - still, no invalid password 
message in any of the logs.
10. Stopped ACSLS and the database.  Restarted ACSLS successfully.

I did not test this in a system using NIS+ passwords since you mentioned 
that the problem happens on both of the customer's systems.

I would recommend unlocking lib6 and informix passwords, as well.
1. Stop ACSLS and the database
2. Unlock lib6 and informix passwords.
3. Turn off password aging. 
4.  Reset all 4 ACSLS users' passwords.
5. Start ACSLS.
6.  If everything comes up successfully,  enable password aging again.

Let me know if you have any questions.

Regards,
Salve 

-- 
Salve F. Reyes
Technical Support Engineer
Backline VERITAS/ACSLS
Storage Group Services
salve.reyes@sun.com
303.661.6716  office
Sun Microsystems