ADSM-L

Re: [ADSM-L] Operation Center Blues!!

2015-10-08 15:22:15
Subject: Re: [ADSM-L] Operation Center Blues!!
From: Vikas Arora <vikaroin AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 8 Oct 2015 11:58:24 +0200
Hi Robert,

Thanks for your reply.

1. I understand inorder to upgrade my OC to v7.1.3, hub server must be
first upgraded to v7.1.3 >> in that case we will need to wait a little
while.

2. Please see the commands output.

tsm: TSM197LM>sh monservers
List of monitored server sessions:
  TSM226:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM201D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM105:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSMNLAMS101:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM232D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM209D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM203D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM229D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM202D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM205:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM206D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM207D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM227:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM106D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM215:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM211:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM228:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM101:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM104D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM231D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM21:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM103D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM192LM:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM102D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM230D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM204D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM191LM:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM210D:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM294LM:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM291LM:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM293LM:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM296LM:
    admin IBM-OC-TSM197LM, running, rc=0.
  TSM292LM:
    admin IBM-OC-TSM197LM, running, rc=0.
PUSHSTATUS is ON.
List of known servers:
  ERR_TAPES:
    last collection 2015-10-08 11:45:58.742750
    deltaSec=       0, buildGrids=True
  TSM102D:
    last collection 2015-10-07 06:11:24.956812
    deltaSec=       0, buildGrids=True
  TSM103D:
    last collection 2015-10-06 19:09:41.844010
    deltaSec=       0, buildGrids=True
  TSM104D:
    last collection 2015-10-06 11:53:36.380075
    deltaSec=       0, buildGrids=True
  TSM204D:
    last collection 2015-10-07 04:43:01.985216
    deltaSec=       0, buildGrids=True
  TSM197LM:
    last collection 2015-10-08 11:45:58.742750
    deltaSec=       0, buildGrids=True
  TSM231D:
    last collection 2015-10-06 12:07:17.936507
    deltaSec=       0, buildGrids=True
  TSM230D:
    last collection 2015-10-07 06:14:22.935757
    deltaSec=       0, buildGrids=True
  TSM210D:
    last collection 2015-10-08 01:51:48.960110
    deltaSec=       0, buildGrids=True
  TSM296LM:
    last collection 2015-10-08 11:03:19.105700
    deltaSec=      -3, buildGrids=True
  TSM291LM:
    last collection 2015-10-08 08:32:40.000000
    deltaSec=       0, buildGrids=False
  TSM292LM:
    last collection 2015-10-08 09:46:08.000000
    deltaSec=       0, buildGrids=False
  TSM293LM:
    last collection 2015-10-08 10:49:38.169843
    deltaSec=       0, buildGrids=True
  TSM294LM:
    last collection 2015-10-08 06:49:36.000000
    deltaSec=       0, buildGrids=False
  TSM191LM:
    last collection 2015-10-07 16:30:26.000000
    deltaSec=      -3, buildGrids=False
  TSM192LM:
    last collection 2015-10-06 19:25:09.000000
    deltaSec=      -3, buildGrids=False
  TSM21:
    last collection 2015-10-06 16:56:49.000000
    deltaSec=      -3, buildGrids=False
  TSMNLAMS101:
    last collection 2015-10-06 22:48:58.603769
    deltaSec=       0, buildGrids=True
  TSM211:
    last collection 2015-10-06 10:39:12.306804
    deltaSec=       0, buildGrids=True
  TSM227:
    last collection 2015-10-06 08:01:17.824342
    deltaSec=       0, buildGrids=True
  TSM205:
    last collection 2015-10-06 05:47:18.473625
    deltaSec=       0, buildGrids=True
  TSM101:
    last collection 2015-10-06 10:52:35.880121
    deltaSec=       0, buildGrids=True
  TSM228:
    last collection 2015-10-06 10:42:10.143192
    deltaSec=       0, buildGrids=True
more...   (<ENTER> to continue, 'C' to cancel)


tsm: TSM197LM>

tsm: TSM197LM>q monitorsettings

                                Monitor Status: On
             Status Refresh Interval (Minutes): 5
                      Status Retention (Hours): 48
                        Monitor Message Alerts: On
               Alert Update Interval (Minutes): 10
                                Alert to Email: Off
          Send Alert Summary to Administrators:
                      Alert from Email Address:
                               Alert SMTP Host:
                               Alert SMTP Port: 25
               Alert Active Duration (Minutes): 480
             Alert Inactive Duration (Minutes): 480
               Alert Closed Duration (Minutes): 60
                              Monitoring Admin: IBM-OC-TSM197LM
                               Monitored Group: IBM-OC-TSM197LM
                             Monitored Servers: TSM101 TSM102D TSM103D
TSM104D TSM105 TSM106D TSM191LM TSM192LM TSM201D TSM202D TSM203D TSM204D
TSM205 TSM206D TSM207D TSM209D TSM21 TSM210D TSM211 TSM215 TSM226 TSM227
TSM228 TSM229D
                                                 TSM230D TSM231D TSM232D
TSM291LM TSM292LM TSM293LM TSM294LM TSM296LM TSMNLAMS101
             At-Risk Interval for Applications: 24
    Skipped files as At-Risk for Applications?: Yes
         At-Risk Interval for Virtual Machines: 22
Skipped files as At-Risk for Virtual Machines?: Yes
                  At-Risk Interval for Systems: 24
         Skipped files as At-Risk for Systems?: Yes


HUB SERVER

tsm: TSM201D>q monitorsettings

                                Monitor Status: On
             Status Refresh Interval (Minutes): 5
                      Status Retention (Hours): 48
                        Monitor Message Alerts: On
               Alert Update Interval (Minutes): 10
                                Alert to Email: Off
          Send Alert Summary to Administrators:
                      Alert from Email Address:
                               Alert SMTP Host:
                               Alert SMTP Port: 25
               Alert Active Duration (Minutes): 480
             Alert Inactive Duration (Minutes): 480
               Alert Closed Duration (Minutes): 60
                              Monitoring Admin:
                               Monitored Group:
                             Monitored Servers:
             At-Risk Interval for Applications: 24
    Skipped files as At-Risk for Applications?: Yes
         At-Risk Interval for Virtual Machines: 22
Skipped files as At-Risk for Virtual Machines?: Yes
                  At-Risk Interval for Systems: 24
         Skipped files as At-Risk for Systems?: Yes



I also tried restarting OC, making a ping server commands from hub and
spoke to force communication, but not a fast reaction.

from the above outputs, all looks green. But for some reasons server status
updates are not so fast ( even in hours)

We will upgrade eventually to v7.1.3 in next months.

thanks








Grüße
Vikas Arora

*e Mail* : vikaroin AT gmail DOT com

On 7 October 2015 at 22:41, Robert Jose <rjose AT us.ibm DOT com> wrote:

> Hi Vikas
> I am sorry you are having trouble with Operations Center. Let me see if I
> can help. The first thing is that although 7.1.0 is a great version, we
> have made a lot of updates and improvements in our latest OC (version
> 7.1.3).
>
> Second, can you run query monitorsettings on both the hub and the spoke?
> We want to make sure that the monitor settings is set to On and that the
> spoke is in the monitored servers value on the hub (seen in the
> monitorsettings or by running show monservers on the hub).
>
> If the monitor setting is off on the spoke, you can run this command on the
> spoke to turn it on:  set statusmonitor on
>
> Now, the other issue is that the Notification Listener could have crashed
> (713 will restart the listener). You can usually tell if the notification
> listener has crashed because the last refresh value in the bottom right of
> the grid will be in the hours. The only way to get the notification
> listener started in 7.1.0 is to restart the OC.
>
> I hope this helps
>
> Rob Jose
> TSM OC UI Developer / L3 Support
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/07/2015
> 12:55:33 AM:
>
> > From: Vikas Arora <vikaroin AT GMAIL DOT COM>
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Date: 10/07/2015 12:57 AM
> > Subject: [ADSM-L] Operation Center Blues!!
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> > Hello All,
> >
> > I recently installed Operation Center version 7.1.0.100 to see the good
> > stuff it has to offer, But I see that server status are not frequently
> > updated.
> >
> > For example.
> >
> > TSM DB backup was done for spoke server TSM201D at  06:41 am today
> morning,
> > but as of 09:37 Am, I still see in OPeration center that last DB backup
> was
> > 12 hours ago.  Any Ideas why.
> >
> > Although when I choose that server I can see under completed tasks, that
> > last DB was 3 hours ago.
> >
> >
> >
> > Spoke server is at v6.3.4
> >
> > I have ADMINCOMMITTIMEOUT 7200
> >              ADMINIDLETIMEOUT        20
> >               PUSHSTATUS  YES
> >
> > Please see the snapshots below, was unable to send them here.
> >
> >
> >
>
> https://drive.google.com/file/d/0BwDDdmz6R7PteDZUWDVURkdpUm8/view?usp=sharing
>
> >
> >
>
> https://drive.google.com/file/d/0BwDDdmz6R7PtOGdmLTljdVJibG8/view?usp=sharing
>
> >
> >
> > thanks
> >
> >
> >
> >
> >
> >
> > Grüße
> > Vikas Arora
> >
> > *e Mail* : vikaroin AT gmail DOT com
> >
>