nv-l
[Top] [All Lists]

[nv-l] Switch management and port status monitoring

To: nv-l@lists.us.ibm.com
Subject: [nv-l] Switch management and port status monitoring
From: James Markham <markhaja@us.ibm.com>
Date: Wed, 30 Jun 2004 07:30:36 -0400
Delivery-date: Wed, 30 Jun 2004 12:45:01 +0100
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

I am trying to wrap up the survey to feed the compiled information to our development team by Friday of this week. We've received valuable information from those who have already responded, but I would like to gather as many responses as possible before turning it in.

If you have the time, please respond to the survey, either to the list, or directly to my email. It shouldn't take more than a few minutes to complete.

Thank you.

Jim Markham
Tivoli Systems
IBM Software Group
Email: markhaja@us.ibm.com
T/L 687-1405, (919)224-1405


================================================================

We have put together a short survey of questions regarding switch management/layer 2 support to better understand how customers might use port status monitoring. Participation is voluntary. Your responses will be very helpful in determining future design direction.
  1. How many switches do you have in your network environment?
  2. If you could, how many switches would you like to monitor?
  3. If you could do port status monitoring on your switches, How would you like to specify the switches to monitor? For example, by hostname, IP address, OID, wildcards, others?
  1. If you could prioritize a particular mechanism for specifying switches,
  1. What method would be the most important to you?
  2. What method would be the least important?
  3. Are there particular combinations that are most important in your environment?
  4. Briefly describe the approach you would use to select the switches you would like to monitor.  For example, would you monitor all switches and exclude those that don't require monitoring, or would you be very selective at including specific switches?  
  5. What types of ports would you want to monitor on a switch? For example:
  •  All ports
  • Trunk ports
  • Ports connected to another switch or router
  • Ports assigned to specific VLANs
  • Combinations of the above. What combinations are most important to you?
  • Would you monitor for different information if it was a core vs. access switch, or core vs. cascaded? If so, what would be the different things you would want to monitor?
  • What other type of information is important to monitor about a switch?
  • How do you work with VLANs today?
  1. What type of information would you like to see regarding VLANs?
  2. Would you want to monitor different information for a switch if you were monitoring it for one of your customers, rather than a switch within your own company's infrastructure? If so, what would you do differently?
  3. What tools do you currently use to monitor your switches? What valuable information do they provide?
  4. How do you currently diagnose problems with your switches? What tool helps the most, and how does it help?
<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web