|
Kevin,
You have a couple of misconceptions here.
1. The TME transport mechanism requires that you have the Tivoli Framework installed on your NetView Machine and NetView installed as a Tivoli application as opposed to the now more usual method of installation using NetView's instalnv. After the Tivoli acquisition in 1996, NetView became Tivoli app, just like TEC, and had to be installed using the Tivoli Framework. It still can be. But most customers have since opted for a stand-alone install with TEC on another separate machine. Framework installs are a rarity these days.
If you have done the Framework install, then you can choose the TME method, which uses the Framework's oserv daemon to send the event. If not, then you have to use the now more prevalent TCP/IP connection method.
2. A FATAL error is not what you think it is. Every time you stop nvserverd or stop just the adapter with nvtecia -stop, the last thing the code in nvserverd does is generate an event for the TEC server that it is going down. By convention with other TEC adapters, this event is given a FATAL status for the TEC console. That tells the operators they have lost connection to NetView. When nvserverd is brought up or you restart the adapter with nvtecia -reload, nvserverd generate a matching event with the severity of HARMLESS and this causes them both to be removed from the TEC console once it gets there.
This log looks completely normal for an nvserverd shutdown and restart.
James Shanks
Tivoli Network Availability Management Level Three
Network Availability Management
Tivoli Software, IBM Corp
1-919-224-1642 | T/L 687-1642 | ITN 26871642
 "Sperry, Kevin" <Kevin.Sperry@us.ngrid.com>
"Sperry, Kevin" <Kevin.Sperry@us.ngrid.com>
Sent by: nv-l-bounces@lists.ca.ibm.com
04/21/2009 01:38 PM
Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com> |
|
|
Hello again,
1. Using UNIX with NetView 7.1.5. Is it recommended to use the "TME transport mechanism" for sending alerts to TEC?
2. We are currently forwarding events in out test environment and have seen this fatal error 2 or 3 times over the pasty 3 weeks. Any idea why?
04/21/09 11:42:21 TEC_ITS_BASE;source=nvserverd;origin=148.183.79.176;hostname=148.183.79.176;adapter_host=148.183.79.176
;date="04/21/09 11:42:21";status=OPEN;severity=FATAL;msg="nvserverd is ending";END
^A
04/21/09 11:42:21 Shutdown Event sent
04/21/09 11:42:21 nvcorrd session closed
04/21/09 11:42:23 TEC handle destroyed
04/21/09 11:42:23 Close of TEC API completed.
04/21/09 11:44:53 fallbackClass = TEC_ITS_BASE
04/21/09 11:44:53 ServerLocation = nguip85h
04/21/09 11:44:53 Java Options = -Xusealtsigs
04/21/09 11:46:36 NvserverdPrimeTecEvents =
04/21/09 11:46:36 NvserverdSendSeverityTecEvents =
04/21/09 11:46:36 TecRuleName = TEC_ITS.rs
04/21/09 11:46:37 TecConnServer::openSession( ) with nvcorrd:
04/21/09 11:46:37 fRuleName = TEC_ITS.rs, CorrelationType = 1, priming_flag = 1, TivoliTEC = 1
04/21/09 11:46:37 TEC_ITS_BASE;source=nvserverd;origin=148.183.79.176;hostname=148.183.79.176;adapter_host=148.183.79.176
;date="04/21/09 11:46:37";status=CLOSED;severity=HARMLESS;msg="nvserverd has connected using rule TEC_ITS.rs";END
Thank you,
Kevin Sperry
IT Analyst, Data Center Monitoring Control
nationalgrid
7437 Henry Clay Blvd. Bldg#3
Liverpool, NY 13088
Phone: (315) 460-2688 Internal: 829-2688
Kevin.Sperry@us.ngrid.com
********************************************************************************
This e-mail and any files transmitted with it, are confidential to National Grid and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please reply to this message and let the sender know._______________________________________________
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)
| 