Look in /var/log/pluto especially at DCERouter.log, LaunchManager.log, and LaunchManager.process.log. Use the data there to answer the following questions:
1) Is DCERouter starting and failing, or not starting at all? (use the timestamps to determine) Provide any errors
2) Is the LaunchManager doing something that takes a particularly long time, or getting hung up on something?
3) Is LaunchManager looping trying to connect to the router forever?
If DCERouter simply isn't starting, but LaunchManager is doing its thing normally, I had a similar issue recently - the root cause was that a bunch of lock files weren't cleaned up properly when someone pulled the power cord on my core. I don't remember where they were off the top of my head - I think there were some in /var/run and /usr/pluto/lock