C 
Mit freundlichen Grüßen/With kind Regards 

Danny Buthge 
Senior 2nd Line Supporter IP/MPLS and Security 
-- 
Cisco Unified Computing Technology Support Specialist 

JETZT NEU: icyteas - simply intelligent ICT - powered by BCC 

BCC Business Communication Company GmbH 
Heinrich-Nordhoff-Straße 69, 38440 Wolfsburg Tel. +49 5361 2777-361, Fax -388 

mailto:[email protected] www.bcc.de 

Registergericht: Braunschweig HRB 4460 
Geschäftsführung: Dipl.-Ing. (FH) Josef Glöckl-Frohnholzer
 

Von: Porter, Craig [mailto:[email protected]] 
Gesendet: Friday, August 09, 2013 02:33 PM
An: spectrum <[email protected]> 
Betreff: RE: [spectrum] MaintMode Scheduler errors 
 


I’ve had similar problems with Spectrum schedules too. I’m located in the UK , 
ahead of our primary OC and Spectroservers which are all located on the US east 
coast. Everybody in our organisation who uses Spectrum except me is located in 
the US east coast time zone. Everybody can set maintenance schedules except me.

 

I’ve tried setting the times using the Spectroserver time zone, the managed 
server’s time zone, and my own time zone, but nothing works. Once I even 
started a screen share session with a colleague in the US to confirm that I was 
following exactly the same procedure as she was. Nobody in the US has any 
problem but maintenance schedules just don’t work for me no matter what I do.

 

We’re running 9.2 H03.

 

Craig Porter, Enterprise Systems Management - Availability & Performance 
Monitoring
Marsh & McLennan Companies
Global Technology Infrastructure (MGTI) | Centralized Operations
Sackville House 1.6, 143-149 Fenchurch Street, London EC3M 6BN, Great Britain
+44 (0)20 7178 4827 | Mobile +44 (0)7585 803 093 | [email protected] 
<mailto:[email protected]>  
www.mmc.com

 

From: F J Rutcho [mailto:[email protected]] 
Sent: 09 August 2013 13:21
To: spectrum
Subject: RE: [spectrum] MaintMode Scheduler errors

 

I'm surprised no one else has experienced this issue.  The only workaround I 
can determine is for our Australia analyst sets the time on their local PC to 
match the time on the SpectroSERVER.  I was hoping there was a better solution 
out there.
 

________________________________

From: [email protected]
To: [email protected]
Subject: [spectrum] MaintMode Scheduler errors
Date: Sun, 4 Aug 2013 21:50:48 -0400

I imagine someone has seen this and knows the answer.
 
Spectrum Version = 9.2 HF09
Windows 2008
Single SpectroSERVER, Single OneClick server, Single Reporting server.
 
We have Operation Centers [OC] in various countries around the world.
 
For this example, we'll identify 3 areas, North America, Europe, Australia.
OCs are located in each zone.  SpectroSERVER located in Europe.
 
When MaintMode is scheduled on a model (using SS Time) ahead of the OC Current 
time (e.g. NA or EU), there isn't an issue, however if the Australia OC Analyst 
tries to schedule MaintMode on a model in (India), that generates an error 
indicating you can't schedule a model for maintenance before your current time. 
 
 
In this case, India is forward of the SpectroSERVER time, however behind the 
Australia time.
 
Anyone know the workaround?  
 
Please advise.
 
Kindly,
 

Fred
 
 

*       --To unsubscribe from spectrum, send email to [email protected] with the 
body: unsubscribe spectrum [email protected] 

*       --To unsubscribe from spectrum, send email to [email protected] with the 
body: unsubscribe spectrum [email protected] 

Marsh Ltd Registered in England Number: 1507274
Registered office 1 Tower Place West, Tower Place, London, EC3R 5BU

Marsh Ltd is authorised and regulated by the Financial Conduct Authority

This message and any attachments are confidential. If you have received this
message in error please delete it from your system. If you require any
assistance please notify the sender. Thank you.

*       --To unsubscribe from spectrum, send email to [email protected] with the 
body: unsubscribe spectrum [email protected] 


---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to