Re: [NV-L] sec:unclas Switch Analyzer

[Leslie Clark <lclark@us.ibm.com>]

I've seen that recommendation in the
documentation.  I saw the behavior you describe at one customer site,
and they did make the adjustment on a test section of the network, to 15
minutes, and did controlled testing of the discovery, and it did not help.
It did not seem to hurt, either, but I am not qualified to say that means
anything for your network. Also, this was a mainly cisco network. On closer
inspection, the problem required a code fix. It was provided in the efix
for APAR IY67325, which goes on after V1.3.1.  So make sure you have
that fix applied. It made a big difference. It will show up in /usr/OV/service/V131.

The reason I suspect the ageout might
not be the problem is that rediscovery ought not to be happening continuously,
only at startup or at status change time, driven by Netview's polling frequency.
If Netview is polling every 5 minutes, I would think that would keep the
devices in the forwarding table, so it seems like a 5-minute ageout ought
to be ok. There is probably a big hole in that logic. 

Cordially,

Leslie A. Clark
IT Services Specialist, Network Mgmt
Information Technology Services Americas
IBM Global Services
(248) 552-4968 Voicemail, Fax, Pager

"Jermyn, Michael PO" <Michael.Jermyn@defence.gov.au>
Sent by: nv-l-bounces@lists.ca.ibm.com

07/20/2006 03:10 AM

Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>

To	"Tivoli NetView Discussions" <nv-l@lists.ca.ibm.com>
cc
Subject	[NV-L] sec:unclas   Switch Analyzer

Leslie,
have a few queries re ITSL2 and
cisco and nortel devices.
I believe that ITSL2 requires
your kit to support RFC1493, and "maps" the L2 connections with
the MAC Fwding table of the device.
Our devices have the 'default'
configuration of 5mins as the timeout for the Mac Fwd table for cisco and
nortel kit. We are seeing the L2 connections appearing and disappearing
continually on the network as the table ages out.
Is this normal behaviour and and
how can we overcome it?
One suggestion has been to open
out the Mac Fwding table timeout to somewhere between 15 mins and 3 hrs.
Our network people are uneasy about reconfiguring the timeout of every
device on our network to see if this works.
 
Any ideas/suggestions?
 
Regards,

Mick Jermyn
Network Management Systems Administrator
DNOC-1B-118
HMAS Harman Canberra ACT 2600
Phone: (02) 6127 8277
Fax: (02) 6127 8239
Email: michael.jermyn@defence.gov.au
Contractor to Defence
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 this e-mail in error, you are requested to contact the sender and delete all copies.

 
-----Original Message-----
From: nv-l-bounces@lists.ca.ibm.com [mailto:nv-l-bounces@lists.ca.ibm.com]On Behalf Of Leslie Clark
Sent: Tuesday, 18 July 2006 1:57
To: Tivoli NetView Discussions
Subject: Re: [NV-L] Switch Analyzer and 3Com4228G


As I understand it, multiple vlans are implemented  in SNMP by Cisco equipment by means if community-string indexing. ITSA supports this. If that device implements multiple vlans the same way, then it should work. If it does it in some other proprietary way, then you will only see stuff for the default vlan.

Cordially,

Leslie A. Clark
IT Services Specialist, Network Mgmt
Information Technology Services Americas
IBM Global Services
Detroit

James Shanks/Raleigh/IBM@IBMUS
Sent by: nv-l-bounces@lists.ca.ibm.com

07/17/2006 11:32 AM

Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>

To	Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
cc
Subject	Re: [NV-L] Switch Analyzer and 3Com4228G

Are you sure you have the correct community string in snmpconf?
Can you get it to respond to an snmpwalk of the bridge MIB?  If this
fails
     snmpwalk <IP address of switch> dot1dBridge
but this works
     snmpwalk -c <community>  <IP address of switch>
dot1dBridge
then you need to update your SNMP options.


You could also try loading \usr\ov\snmp_mibs\rfc1493-bridge.mib  (loadmib)
and then querying the device using the MIB browser (browser) for things
under .iso.org.dod.internet.mgmt.mib-2.dot1dBridge (.1.3.6.1.2.1.17)


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


                    
                     
                     
         
            "Baturin Dmitry"  
                     
                     
            <DBaturin@BCC.RU>  
                     
                    
            Sent by:      
                     
                     
To 
            nv-l-bounces@list    
    <nv-l@lists.ca.ibm.com>        
    
            s.ca.ibm.com      
                     
                  cc 
                    
                     
                     
         
                    
                     
                     
 Subject 
            07/17/2006 06:51    
     [NV-L] Switch Analyzer and        
 
            AM        
               3Com4228G  
                     
  
                    
                     
                     
         
                    
                     
                     
         
            Please respond to    
                     
                  
             Tivoli NetView    
                     
                    
               Discussions    
                     
                     
            <nv-l@lists.ca.ib    
                     
                  
                 m.com>  
                     
                     
    
                    
                     
                     
         
                    
                     
                     
         




Hello ALL!
I have a small question about Tivoli Switch Analyzer 1.3:
We are using Tivoli Switch Analyzer 1.3 and Windows 7.1.4 on Windows 2003
server.
We can’t discover VLAN information from 3Com4228G switches, but have
successful VLAN discovery from Cisco switches.
Can Tivoli Switch Analyzer 1.3 discover VLAN info from 3Com4228G?

Thank you.
Dmitry Baturin
_______________________________________________
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)
_______________________________________________
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)