Thanks for relaying this information. I see you're an OpsMgr 2007 shop
as well, and we currently sync OpsMgr alerts with TEC using the Engyro
connector Microsoft purchased. It's not a great connector, but I
digress. We're looking to replace NV as well, except we're not looking
to replace TEC with it--we want OpsMgr to be the core event manager
seeing as they are releasing an integrated help desk platform in about
18 months. When we said this to IBM during the ITNM presentation, they
did a good job of holding back the snickers. We realize this is going to
make it very tough to find a NM product that will correlate root cause
network/node events w/o requiring an OMNIbus type of product.
This brings me to SMARTS, which we also eval'd in the fall. Because
SMARTS has its own Codebook correlation, it seems the perfect solution
because no OMNIbus type of platform is required. Before netview.rls, we
owned the old Tivoli Manager for Network Connectivity, and it did a
decent job. The eval did not go well, likely due to looking at the new
version that was just released about a week earlier. The promised OpsMgr
integration was not as advertised (SMARTS topology crushed the OpsMgr
RMS whenever started), so we wonder what the officially bundled
SMARTS/OpsMgr solution will look like.
For the record, I would love nothing better than ITNM and OMNIbus.
Unfortunately it costs a small fortune, and doesn't fit in with our
Microsoft-centric strategy.
-----Original Message-----
From: Sean Lawrence [mailto:Sean.Lawrence@cantire.com]
Sent: Friday, April 25, 2008 8:46 AM
To: Tivoli NetView Discussions
Subject: [NV-L] ITNM,Omnibu,TBSM,TADDM POC impressions
Well this was a side by side comparison with EMC Smarts and EMC
Application Discovery Manager
Our Network guys were quite impressed with ITNM, I didn't get to touch
it much. I mostly spent my time with TADDM and TBSM.
Pros:
1. The integrated views in TBSM were very configurable
2. Displaying outages based on business service or application is really
powerful
3. Omnibus looks way easier to do complex rules writing
4. TADDM allows the most granular credentials configuration I have seen.
You could literally have a different set of credentials for every box
and every app on that box. (Which unfortunately we might need here :(
5. Fast, we set of the Microsoft SCOM integration with OmniBus. When the
connection foirst comes up SCOM send everything in it's database do
sync. This regularly kills TEC in production. Omnibus just laughed at
it.
Cons:
1. The integration is not as tight as I had hoped, there still seems to
be a lot of triggered or manually launched imports from TADDM.
2. I did not see the out of the box root cause correlation that I was
expecting; everyone's products seem to be really strong for network and
basic node state correlation but do not include application level
correlation
3. Complicated, it is a huge suite and is going to be a ton of work to
implement properly.
The EMC stuff was not fully integrated like the sales guy state. The
correlation engine is impressive but only handles network and basic node
state correlation.
The biggest surprise is you cannot modify the correlation rules nor add
anything to them (Except for mapping your alerts to a handful of really
basic generic states). There was no capability to write your own rules
or to do escalation notification logic which we currently do in TEC.
No monitoring capability except SNMP. Adding new MIBS values to poll was
a pain.
You basically use the EMC stuff as is. If it doesn't do what you need
out of the box then it's not the product for your shop.
Their discovery engine expects everything to be running on standard
ports, to change this is an advanced task and requires extensive
changes. They rely heavily on network sniffing for discovery. We would
need to have every subnet, VLAN spanned in order to piece the
environment together. Our network guys said the number of spanned ports
required would be crazy and we would have to have these appliances all
over the place.
We were told that the EMC Application Discovery Manager was an appliance
but it's just a pre installed/configured Linux machine that I would be
stuck administering and patching. Linux is not a supported OS here, the
box was not built by out UNIX admins to there standards so it would be
my responsibility.
Sean
-----Original Message-----
From: nv-l-bounces@lists.ca.ibm.com
[mailto:nv-l-bounces@lists.ca.ibm.com] On Behalf Of Jane Curry
Sent: April 24, 2008 2:42 PM
To: Tivoli NetView Discussions
Subject: Re: [NV-L] My Default map is locked
Hi Sean,
Would you care to share your technical thoughts on ITNM,TADDM,Omnibus &
TBSM (budget aside for the moment)???
Cheers,
Jane
Sean Lawrence wrote:
>
> Just finished a 2 week POC with ITNM,TADDM,Omnibus,TBSM. I am awaiting
> on the cheque writers to make a decision.
>
>
>
>
------------------------------------------------------------------------
>
> *From:* nv-l-bounces@lists.ca.ibm.com
> [mailto:nv-l-bounces@lists.ca.ibm.com] *On Behalf Of *Leslie Clark
> *Sent:* April 24, 2008 1:10 PM
> *To:* Tivoli NetView Discussions
> *Subject:* RE: [NV-L] My Default map is locked
>
>
>
>
> So Sean, does this migration mean that you are not upgrading to ITNM
> just yet? :)
>
> Cordially,
>
> Leslie A. Clark
> IT Services Specialist, Network Mgmt
> Information Technology Services Americas
> IBM Global Services
> (248) 552-4968 Voicemail, Fax, Pager
>
>
> *"Sean Lawrence" <Sean.Lawrence@cantire.com>*
> Sent by: nv-l-bounces@lists.ca.ibm.com
>
> 04/24/2008 12:34 PM
>
> Please respond to
> Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
>
>
>
> To
>
>
>
> "Tivoli NetView Discussions" <nv-l@lists.ca.ibm.com>
>
> cc
>
>
>
>
>
> Subject
>
>
>
> RE: [NV-L] My Default map is locked
>
>
>
>
>
>
>
>
>
>
>
>
> Never mind, finally found it in the docs. Control and Mouse 3
>
>
>
>
>
------------------------------------------------------------------------
>
>
> *From:* nv-l-bounces@lists.ca.ibm.com
> [mailto:nv-l-bounces@lists.ca.ibm.com] *On Behalf Of *Sean Lawrence*
> Sent:* April 24, 2008 11:59 AM*
> To:* Tivoli NetView Discussions*
> Subject:* RE: [NV-L] My Default map is locked
>
> I had a map.lock Deleted it and all is well.
>
> I do have a total newb question though. How do I reposition a symbol?
> I have set the automatic layout for my map to off for current and sub
> maps. How do I actually move the symbol?
>
>
>
>
>
------------------------------------------------------------------------
>
>
> *From:* nv-l-bounces@lists.ca.ibm.com
> [mailto:nv-l-bounces@lists.ca.ibm.com] *On Behalf Of *Leslie Clark*
> Sent:* April 24, 2008 10:30 AM*
> To:* Tivoli NetView Discussions*
> Subject:* Re: [NV-L] My Default map is locked
>
>
> Yes, I think there is a file called map.lock down under
> usr/OV/databases/openview/mapdb somewhere. But if that is there, I'd
> be kind of worried about how that migration took place, and what else
> might be wrong. Did they just restore a system backup onto a new
> machine? Did the ip address change? Do you have a good database backup
> taken using nvhotbackup, or tar while it was quiesced? You may need
> to do a '/usr/OV/service/reset_ci' and a 'mapadmin -u'.
>
> Cordially,
>
> Leslie A. Clark
> IT Services Specialist, Network Mgmt
> Information Technology Services Americas
> IBM Global Services
> (248) 552-4968 Voicemail, Fax, Pager
>
> *"Sean Lawrence" <Sean.Lawrence@cantire.com>*
> Sent by: nv-l-bounces@lists.ca.ibm.com
>
> 04/24/2008 10:04 AM
>
>
>
> Please respond to
> Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
>
>
>
>
>
> To
>
>
>
> "Tivoli NetView Discussions" <nv-l@lists.ca.ibm.com>
>
> cc
>
>
>
>
>
> Subject
>
>
>
> [NV-L] My Default map is locked
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Our AIX admins just migrated our Netvirew server from a P5 lpar to a
> P6 machine.
>
> Now I am getting errors that my default map is open for writing by
> another user. Is there a lock file somewhere that needs to be
> removed?_______________________________________________
> NV-L mailing list
> NV-L@lists.ca.ibm.com
> Unsubscribe:NV-L-leave@lists.ca.ibm.com
> http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited
> to internal IBM'ers
only)_______________________________________________
> NV-L mailing list
> NV-L@lists.ca.ibm.com
> Unsubscribe:NV-L-leave@lists.ca.ibm.com
> http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited
> to internal IBM'ers only)
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> NV-L mailing list
> NV-L@lists.ca.ibm.com
> Unsubscribe:NV-L-leave@lists.ca.ibm.com
> http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited
to internal IBM'ers only)
>
--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK.
Registered in England & Wales, Company No. 3458854.
Tel: +44 (0)1628 782565
Copyright (c) 2008 Jane Curry <jane.curry@skills-1st.co.uk>. All rights
reserved.
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message.
Any disclosure, copying, or distribution of this message, or the taking of any
action based on it, is strictly prohibited. [v.E.1]
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|