Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

why cleaning IP resource always takes 1 second

Created: 08 Apr 2013 • Updated: 09 Apr 2013 | 4 comments
This issue has been solved. See solution.
Hello
 
I use SF 6.0.1 on Suse 11, I found that cleaning IP resource always takes 1 seconds. I checked CLEAN script of IP, it seem execution is quick,so I want to know is there any additional steps take more time during cleaning IP resource.
 
Here is engine_A.log:
 
2013/04/08 01:12:02 VCS WARNING V-16-10031-4604 (abc-db2) IP:OracleIpRes:online:Address 2001:1b70:0200:1026:0000:0000:0131:0132 already exists: Res OracleIpRes will not go online.
2013/04/08 01:12:03 VCS ERROR V-16-2-13066 (abc-db2) Agent is calling clean for resource(OracleIpRes) because the resource is  not up even after online completed.
2013/04/08 01:12:04 VCS INFO V-16-2-13716 (abc-db2) Resource(OracleIpRes): Output of the completed operation (clean) 
==============================================
RTNETLINK answers: Cannot assign requested address
==============================================
 
2013/04/08 01:12:04 VCS INFO V-16-2-13068 (abc-db2) Resource(OracleIpRes) - clean completed successfully.
Operating Systems:

Comments 4 CommentsJump to latest comment

kongzzzz's picture

New findings, not only IP resource, cleaning the other resources also takes 1 seconds, is it a regular pattern that VCS reports clean completed in next second and continue next actions?

Paresh Bafna's picture

Hi kongzzzz,

State of any resource changes only after monitor reports state change.

After online/offline/clean generally monitor is scheduled immediately. Once monitor report state change then only resource state is updated.

In your case of IP resource,

2013/04/08 01:12:02 VCS WARNING V-16-10031-4604 (abc-db2) IP:OracleIpRes:online:Address 2001:1b70:0200:1026:0000:0000:0131:0132 already exists: Res OracleIpRes will not go online.

>> Online failed to bring IP online.

>> Monitor was invoked after online completed to check state of the resource.

2013/04/08 01:12:03 VCS ERROR V-16-2-13066 (abc-db2) Agent is calling clean for resource(OracleIpRes) because the resource is not up even after online completed.

>> Monitor correctly detected that IP is not online and reported resource offline.

>> Resrouce was expected to be online after online. However, it was detected offline, so clean was called.

2013/04/08 01:12:04 VCS INFO V-16-2-13716 (abc-db2) Resource(OracleIpRes): Output of the completed operation (clean)
==============================================
RTNETLINK answers: Cannot assign requested address
==============================================
2013/04/08 01:12:04 VCS INFO V-16-2-13068 (abc-db2) Resource(OracleIpRes) - clean completed successfully.

There is no added delay like sleep introduced by VCS, it only time taken by online + monitor or clean + monitor that may come up to one sec.

Hope this answers your query!

Thanks and Regards,

Paresh Bafna

Thanks and Regards,
Paresh Bafna

SOLUTION
mikebounds's picture

I guess you are only testing clean for one scenerio - IP already exists - there are 3 main reasons why clean can be called:

  1. IP cannnot be onlined
  2. IP is online and then goes offline outside of VCS control
  3. VCS tries to offline IP, but it doesn't offline, so clean is called to forcably offline it.

Clean time could vary for each of these and in particular for reason 3 and for each of these 3 reasons there are different reasons that could cause each of them, so clean time could vary for say different events causing reason 1.  Also there are extenal factors such as the system is busy which could effect how long the clean runs.

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below