OneView Usability Enhancements in 4.3

Enterasys’ focus on usability and polish have continued in their 4.3 release of Netsight. Most significantly, the focus on OneView and incorporating NAC as Identity and Access is a very encouraging step toward a unified, refined application that is useful both for a Netsight administrator to directors/managers and IT helpdesks. Case in point:

Improved visuals for the Dashboard

The new charts break out, allowing you to view some very high-level information easily. The chart tracking authentication types over time is interesting/helpful, as well.

Because not all IT shops are identical (and UNI tends to be non-mainstream at times), I’d love to be able to customize which charts and information are shown on the Dashboard. Adding the ability to further filter on a particular chart/graph would also be helpful. For instance, if I’m only looking at Registered Users, how many of those are the various device families? Or of those devices that are disconnected, how many have the Registered Profile? The new charts provide a great first step toward information awareness about what is happening within Identity and Access and I look forward to its continued evolution.

Usability enhancements continue with the integration of other features. One that will be helpful for troubleshooting in the future is the PortView feature, which was added a version back but continues to be more closely integrated:

Right-clicking on an end-system reveals the PortView feature.

Choosing the PortView option, you get presented with the following screen:

PortView info

It shows the path your device takes across the network, as well as the link state across there (this takes some time to show the link, which is why one link is green and the other isn’t yet green). You can’t see it here, but when you highlight each device in the path, there’s a very tiny dot beside each device that will reveal different information (IP, uptime, date seen, etc.). I’d love to see the information displayed here continue to be refined. For instance, swapping out the dots for icons that display something meaningful for each grouping of data. Or possibly allowing additional info to be showing as a highlighted overlay on each device. I’m still amazed at this level of detail Enterasys has provided.

Finally, sometimes it’s the little things that make a big difference. Before, if I wanted to search for a MAC, it had to be in this format:


Now I can also search for this as:


and get the same results! Of course, partial matches still apply, but it’s a nice improvement for usability.

Enterasys’ team has really done a great job of adding value to the tools they provide and making them more accessible. From high-level details (charts/graphs) to tighter integration (PortView) down to little details like searching for devices in various ways, refinements continue to our benefit and those of our users.

About thomast

I support UNI's residential network, primarily providing end-user Internet access support to 4,500 residents.
This entry was posted in Uncategorized and tagged , , , , . Bookmark the permalink.

2 Responses to OneView Usability Enhancements in 4.3

  1. Fernando Camargo says:

    Hey man,

    My N7 is taking high cpu util in the last days. I sent a show support to Enterasys but dont receive any return about it.
    Do you know some troubles that could make it? We try isolate the Bridge switches but nothing made the high Router Control Plane.

    If could help me, i appreciate, i dont know any website about enterasys so thanks for yours.

    • howarda says:

      High CPU could relate to a number of problems. My troubleshooting process would involve running show system utilization to determine if a particular process or blade is using more cpu than others. The processes or blades with the highest cpu might give you a hint. I also trend cpu utilization and port utilization with tools like cacti or netsight. An N7 chassis distributes processing power across all blades you may be able to triage the problem by distributing high utilization links across multiple ports. The next way to triage might be to capture or sample packets from various interfaces and try to identify suspicious traffic such as flooding, a high pps rate. Knowing your network might help you filter unnecessary traffic with policy and monitor the effects on CPU, for example if you don’t need IPV6 disable it, at least temporarily.

      I don’t have much experience troubleshooting the Router Control Plane Process. Perhaps asking GTAC which features are associated with that process would help you key in areas specific to your configuration. I find taking the time to send GTAC a network diagram is also helpful. I would guess dynamic routing protocols might be in play. I know that router control plane is correlated with increased traffic utilization. If overall throughput characteristics haven’t changed you might examine RMON or netflow trends to determine if the type of traffic the N7 is handling has changed.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>