hi!
this may be an issue of having auto-discovery turned on.
do you use auto-discovery or a netmon-seedfile ?
cheers,
--
fredo
Diese Nachricht und allfällige angehängte Dokumente sind vertraulich und nur für den/die Adressaten bestimmt. Sollten Sie nicht der beabsichtigte Adressat sein, ist jede Offenlegung, Weiterleitung oder sonstige Verwendung dieser Information nicht gestattet. In diesem Fall bitten wir, den Absender zu verständigen und die Information zu vernichten. Für Übermittlungsfehler oder sonstige Irrtümer bei Übermittlung besteht keine Haftung.
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]
> Sent: Monday, December 06, 2004 12:27 AM
> To: 'nv-l@lists.us.ibm.com'
> 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
> >
>
|