[cisco-voip] RIS problem

[pwalenta at wi.rr.com]

As I was uploading log files for the TAC I noticed that the times were a
bit off.

Turns out the publisher was in the Arizona time zone, and the subscriber
was in Central.  Once corrected and rebooted, RIS functioned normally.

Yikes.

----- Original Message -----
From: pwalenta at wi.rr.com
Date: Friday, January 19, 2007 9:55 am
Subject: Re: [cisco-voip] RIS problem
To: Wes Sisk <wsisk at cisco.com>
Cc: cisco-voip at puck.nether.net

> Already tried the restart service/reboot systems to no avail.
> 
> mmfspy shows no phones registered no other devices registered.
> 
> Opening TAC case shortly.  
> 
> I'm hoping this is a cosmetic problem and not something serious ;-)
> 
> ----- Original Message -----
> From: Wes Sisk <wsisk at cisco.com>
> Date: Friday, January 19, 2007 9:16 am
> Subject: Re: [cisco-voip] RIS problem
> To: pwalenta at wi.rr.com
> Cc: cisco-voip at puck.nether.net
> 
> > no hits in topic.  you're up a creek.
> > 
> > poke around a bit more -
> > does 'mmfspy' from the cmd prompt show correct status?  if not, 
> > then CM 
> > is not populating shared memory correctly => restart ccm.
> > if mmfspy shows correct status, but RIS does not, it will take 
> some 
> > digging.  I guess you've tried the normal restart RIS?  Crank RIS 
> > traces 
> > to detailed, restart, capture traces, upload to TAC case.
> > 
> > /Wes
> > 
> > pwalenta at wi.rr.com wrote:
> > > I've got a cluster that was upgraded from 4.1 to 4.2.3sr1.
> > >
> > > Everything works fine except that RIS doesn't report any 
> > registered devices.
> > >
> > > Unity is there and works, phones are there, vg224 and voice 
> > gateways are
> > > all there and work.
> > >
> > > The only clue as to something being wrong (outside of no 
> registered> > devices being reported) is this in the RIS trace file:
> > >
> > > 01/19/2007 08:38:19.427 RIS|GENisUp: check:
> > > 
> >
> Global\CCM_GENstatusFile_15|<CLID::StandAloneCluster><NID::172.16.22.12>>
> 01/19/2007 08:38:19.427 RIS|GENisUp: OpenFileMapping
> > > failed.|<CLID::StandAloneCluster><NID::172.16.22.12>
> > >
> > > Anyone seen this before?
> > > _______________________________________________
> > > cisco-voip mailing list
> > > cisco-voip at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > >   
> > 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>