can you click red x mark under stage and see the complete logs and also have you verified rscd logs what the errors are ?
The error is the one i mentioned above. Here is the screen shot:
And there is nothing in the rscd.log as well:
03/19/15 12:34:00.756 INFO1 rscd - 10.40.26.98 3776 BladeLogicRSCD@MIVMMSISB
1->gsmith@MIVMMSISB1:PrivilegeMapped (BLAdmins:BLAdmin): CM: > [Deploy] Job 'emp
y_blpackage' is executing a dry run
03/19/15 12:35:46.653 WARN rscd - MIVMMSISB1 3172 SYSTEM (Not_available): (
Not_available): Main: Wait Timeout. Starting AgentHouseKeeping.
can the ars talk to the afs ?
Ahh...i have never checked this!
May be this might be the issue. I will check and see how it goes.
1 of 1 people found this helpful
you can Check all this ports if they are open:
Port Protocol From To Notes 1080 TCP AppServ. Socks Proxy 5282 HTTP(TCP) Adv.Rep Adv.FileServ 7717 TCP FileServ. Adv. FileServ Marimba publishing 7717 TCP Trans. Admin Adv. FileServ local Traffic 7717 TCP Proxy Administrator Adv.Rep local Traffic 7717 TCP Certificate Man. BMCCM Tuner local Traffic 8080 HTTP(TCP) Adv.Rep Adv.Rep local Traffic 4750 RSCD (TCP) AppServ. RSCD Agent
may be you need the not in bmc doc documented ports
8081 TCP FileServ Adv.Rep 8081 TCP Adv.Rep FileServ
Bill you were right, the ARS was not able to communicate with AFS. We have opened a request with network team to get the ports opened. Once this is resolved we should be ok i guess.