[cisco-voip] Why Do Route Lists Unregister?

[Justin Steinberg]

Route lists are assigned to a CM group.

Are your RL assigned to a CM group that has both pub and sub?  If not,
perhaps that can cause some trouble when your cluster lost connectivity.

Justin

On 2/16/07, Keith Klevenski <keith.klevenski at rig.net> wrote:
>
>  Hi all,
>
>
>
> I asked this question recently, but I never got a solid answer.
>
>
>
> A few minutes ago we had an issue between our two core 6500's and sw1 was
> not accessible, but sw2 was (an rspan gone bad).  Each switch has a 6608
> with several PRIs off each one in each switch.  The publisher is off sw1 and
> the subscriber is off sw2.  After the rspan was removed from sw1 (console
> access via Envoy) traffic starting flowing normally again.  Several minutes
> later I was informed that no outbound calls could be made.  I looked around
> and noticed that all route lists were unregistered and of course no calls
> were going out.  I reset all the route lists and they registered and calls
> started going out normally again.
>
>
>
> So the question again is why would route lists unregister and stay
> unregistered until they were all reset?  All of our route lists were
> unregistered, even route lists that only contain one ICT or one gateway.  It
> seems related to CCM losing connectivity to the gateways in the route lists,
> but why they would stay unregistered until a reset eludes me…
>
>
>
> Any input appreciated as always!
>
> Keith
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070216/b424c3e1/attachment.html