Re: [TME10}[ITM] omnibus SitForwarder
Rafa <[email protected]>
| Newsgroups | gmane.comp.sysutils.tivoli.general,gmane.comp.sysutils.tivoli.tme10 |
|---|---|
| Message-ID | <[email protected]> |
Hi Yoga, Is your OMNIBUS running under PA ? that is mandatory if you want enable bi-directional (from Omnibus to ITM) Also, if you execute the test.sh script under /op/IBM/SitForwarder/bin , what is the result? .. Connect SUF to your HUB TEMS? About the connector in TEP, Do you have configured the TEPS the Omnibus connector tab with right user ? Best regards Rafael Cerro Jimenez [email protected] On Friday, 23 November 2012 at 14:05, Yoganarasimha Iyengar wrote: > Hi, > This is issue related to SitForwarder ( NC 731FP05 on RHEL 6, Hub and TEP all on separate box) > > 1. I have setup ITM and Netcool event integration for bi-directional per steps outlined in IBM manual. > On HUB enabled EIF integration and on TEP forwarding situation to EIF. > > 2. Inbound alerts reaching NC and can view them on NC Event console. > > 3. The problem is, alerts updated on NC Event console not reaching TEP. I don't see any situation file under persistence directory except running . > Also files under /tmp/itmsynch/logs don't give much info though I have setup the log for verbose. > > 4. Another issue I notice is in TEP, Omniconnector(common event console) status is always non-operational. Not sure both issues inter related . Hub and TEP are on separate RHEL box. > > 5. So far I have tried giving hostname and also IP in Omniconnector config but no luck > > Thanks > > Yoga Iyengar > Desk: (301)-977-7884 Ext. 199 > Email: [email protected] (mailto:[email protected]) > 10480 Little Patuxent Parkway, Suite 1100 > Columbia, MD 21044 > > > _______________________________________________ > TME10 mailing list > [email protected] (mailto:[email protected]) > Unsubscribe:[email protected] (mailto:[email protected]) > > _______________________________________________ TME10 mailing list [email protected] Unsubscribe:[email protected]