nv-l
[Top] [All Lists]

Re: sec:unclas : [nv-l] sec:unclas Netview & Nortel

To: nv-l@lists.us.ibm.com
Subject: Re: sec:unclas : [nv-l] sec:unclas Netview & Nortel
From: James Shanks <jshanks@us.ibm.com>
Date: Mon, 6 Dec 2004 11:29:28 -0500
Delivery-date: Mon, 06 Dec 2004 16:29:54 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Sensitivity:
There is no need for anything to be continually deleted and recreated. 
Have you talked to Support about why this is happening?
Whatever the reason it can be stopped.  But first you have to understand 
why it is happening, and then change the configuration to avoid it.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group



"Jermyn, Michael MR" <Michael.Jermyn@defence.gov.au> 
Sent by: owner-nv-l@lists.us.ibm.com
12/05/2004 06:27 PM
Please respond to
nv-l


To

"'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com>
cc





Subject
sec:unclas : [nv-l] sec:unclas  Netview & Nortel






Fredo,
the issue is that the Nortel and Cabletron kit get deleted and created 
from
the NV map very regularly. This I believe will cause big problems when we
integrate NV into the TEC and trouble tickets start getting generating and
our configuration board will go crazy with all these devices continually
being deleted and discovered.
 
Do you also have these issues?
 
Regards
 

Mick Jermyn 
Network Management Administrator 
Defence Network Operations Centre 
HMAS Harman 
Canberra ACT 

Ph: 02 6127 8277 
Fax: 02 6127 8239 

IMPORTANT: This e-mail remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the 
Crimes
Act 1914.  If you have received the message in error, you are requested to
immediately contact the sender by e-mail or telephone and then erase the
message. 

 

-----Original Message-----
From: REIBENSCHUH Alfred [mailto:alfred.reibenschuh@it-austria.com]
Sent: Friday, 3 December 2004 23:11
To: 'nv-l@lists.us.ibm.com'
Subject: RE: [nv-l] sec:unclas Netview & Nortel



hi! 

we have also those nortel passport 8k and cabletron layer3 switches. 

your best route would be to modify oid_to_type, since both devices 
ARE layer3 switches and oid_to_type should reflect that, especially 
if you're running ITSA. 


cheers, 

-- 
fredo 

This message and any attached files are confidential and intended solely 
for
the addressee(s). Any publication, transmission or other use of the
information by a person or entity other than the intended addressee is
prohibited. If you receive this in error please contact the sender and
delete the material. The sender does not accept liability for any errors 
or
omissions as a result of the transmission.


> -----Original Message----- 
> From: Jermyn, Michael MR [ mailto:Michael.Jermyn@defence.gov.au
<mailto:Michael.Jermyn@defence.gov.au> ] 
> Sent: Friday, December 03, 2004 2:17 AM 
> To: 'nv-l@lists.us.ibm.com'; nv-l@lists.tivoli.com 
> Subject: [nv-l] sec:unclas Netview & Nortel 
> 
> 
> All, 
> we are having a few issues regarding Netview and modelling of 
> Nortel equip, 
> especially the Passport 8600 series. 
> These devices can operate as either a layer2 switch only, 
> and/or perform a 
> routeing function. 
> NV seems to be confused on how to show these devices and is 
> displaying them 
> all as routers even though they are only performing a layer 2 
> function in 
> the network (a small percentage also perform a routing 
> function, therefore 
> we cannot make a blanket change in oid_to_type). 
> These devices are then either removed from the map and re-discovered 
> daily/weekly(intermittently) etc, or duplicated on the map. 
> Has anyone some ideas on how I can resolve this? 
> 
> PS we are having similar issues with Cabletron equip. 
> 
> Mick Jermyn 
> 





<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web