To: | nv-l@lists.tivoli.com |
---|---|
Subject: | Re: dns/host/win2k dns and netview -TEC |
From: | "James Shanks" <SHANKS@us.tivoli.com> |
Date: | Tue, 23 Oct 2001 12:54:10 -0400 |
This is a multipart message in MIME format. But you will not be able to use the dispsub feature of TEC integration -- the feature that launches a submap containing that node on your NetView box - unless you have consistent name resolution, and the same name in both places. James Shanks Level 3 Support Tivoli NetView for UNIX and NT Tivoli Software IBM Software Group Please note that my new id is jshanks@us.ibm.com netview@toddh.net (Todd H.) Sent by: owner-nv-l@tkg.com 10/23/2001 12:25 PM Please respond to IBM NetView Discussion To: IBM NetView Discussion <nv-l@tkg.com> cc: Subject: Re: [NV-L] dns/host/win2k dns and netview Jane Curry <jane.curry@skills-1st.co.uk> writes: > I'm not sure what the heartache is over long names. The issue comes up forus when forwarding TEC events and doing automated ticketing. The hostname chews up a large % of available screen width on a one-line problem description. If you use NetView with DNS and with the internal TEC adapter, you have no hooks to shorten that FQDN in alerts that are sent to TEC. Unless I've missed something, choices are to hack name resolution (which is ugly), hack the selection name (which sounds risky), abandon the internal tec adapter and send everything to a script that does postemsg, or do something on the TEC side (which may or may not strain an overworked TEC). -- Todd H. http://www.toddh.net/ _________________________________________________________________________ NV-L List information and Archives: http://www.tkg.com/nv-l But you will not be able to use the dispsub feature of TEC integration -- the feature that launches a submap containing that node on your NetView box - unless you have consistent name resolution, and the same name in both places. James Shanks Level 3 Support Tivoli NetView for UNIX and NT Tivoli Software IBM Software Group Please note that my new id is jshanks@us.ibm.com
Jane Curry <jane.curry@skills-1st.co.uk> writes: > I'm not sure what the heartache is over long names. The issue comes up forus when forwarding TEC events and doing automated ticketing. The hostname chews up a large % of available screen width on a one-line problem description. If you use NetView with DNS and with the internal TEC adapter, you have no hooks to shorten that FQDN in alerts that are sent to TEC. Unless I've missed something, choices are to hack name resolution (which is ugly), hack the selection name (which sounds risky), abandon the internal tec adapter and send everything to a script that does postemsg, or do something on the TEC side (which may or may not strain an overworked TEC). -- Todd H. http://www.toddh.net/ _________________________________________________________________________ NV-L List information and Archives: http://www.tkg.com/nv-l |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: dns/host/win2k dns and netview, Leslie Clark |
---|---|
Next by Date: | Re: Slides for tomorrows call/e-meeting, Mike Walsh |
Previous by Thread: | OT sort of , netview launching ciscoworks 2000 - LONG solution, Duble, Ethan |
Next by Thread: | MIB Applications on Solaris, Leslie Clark |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web