Author: "CATALINA MARTINEZ" <CATALINA.MARTINEZ AT tlc.state.tx DOT us>
Date: Tue, 16 Oct 2001 09:53:40 -0500
This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. Hello, I am runnin
That is a feature. Names are not removed when resolution stops working. However, you will find that functions such as 'Monitor..MIB Values...System Information' will no longer work because the comman
Author: "CATALINA MARTINEZ" <CATALINA.MARTINEZ AT tlc.state.tx DOT us>
Date: Fri, 19 Oct 2001 08:14:53 -0500
This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. Thanks Leslie. One
Yes, would rediscover those nodes whose names no longer resolve. And the fully qualified name will be used for the Selection Name, but the map will show the name only up to the first dot. Is that not
Author: "CATALINA MARTINEZ" <CATALINA.MARTINEZ AT tlc.state.tx DOT us>
Date: Fri, 19 Oct 2001 09:47:11 -0500
This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. Yes, the names are
Author: "James Shanks" <SHANKS AT us.tivoli DOT com>
Date: Fri, 19 Oct 2001 11:36:00 -0400
This is a multipart message in MIME format. Not really. The trap origin in the trap window will show whatever name your name resolution provides. To have only shortnames, you'd have to have a separat
Ah. No. Those are provided by name resolution. So they will match the node's Selection Name. Which is a good thing. That way you can go from the event to the node with 'Options...Highlight Node on Ma
This issue of "Any way to shorten the FQDN when netview reports alerts, or are ya stuck with what your resolver gives ya?" came up in our recent NetView class that Scott and I attended. As leslie men
Author: Jane Curry <jane.curry AT skills-1st.co DOT uk>
Date: Tue, 23 Oct 2001 07:59:27 +0100
I'm not sure what the heartache is over long names. NetView is sensible enough to put short names in labels on the topology GUI (even though it discovers FQDN and uses these for the Selection Name fi
Author: "Barr, Scott" <Scott_Barr AT csgsystems DOT com>
Date: Tue, 23 Oct 2001 07:52:38 -0500
If selection name is the issue - we wrote a script in Administrators class that we added to the xnmtrap config for "Node Added" trap. When discovery occurs the script is called and strips the selecti
Author: "James Shanks" <SHANKS AT us.tivoli DOT com>
Date: Tue, 23 Oct 2001 09:17:31 -0400
This is a multipart message in MIME format. I am not certain about this, but you could have problems later if you follow this procedure. I am thinking specifically about events issues, such as "highl
Author: "Barr, Scott" <Scott_Barr AT csgsystems DOT com>
Date: Tue, 23 Oct 2001 08:22:50 -0500
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. Okay by popular demand here it is (as an attachment and also as
I agree. I am generally game to try just about anything, but I would not be brave enough to manipulate Selection Name, or any other 'name' type field in Netview's database using nvdbimport. I always
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
Most places where I have been just truncate it on the T/EC side. Cordially, Leslie A. Clark IBM Global Services - Systems Mgmt & Networking Detroit netview@toddh. net (Todd H.) To: IBM NetView Discus
Author: "Stephen Hochstetler" <shochste AT us.ibm DOT com>
Date: Tue, 23 Oct 2001 12:31:30 -0500
Todd, You mentioned that you are taking NV events, forwarding those to TEC...then getting automatic tickets. The problem with long names is the space taken in the one line problem descriptions. NV --
This does sound like the best solution...now to sell it to the TEC guys. :-) As in many larger environments, a different group handles TEC rules and ticketing. Their requirement for NV events current