This group allowed us to create an alarm that would let us know if an uplink goes down but does not get triggered by the front facing ports going down. This is useful because we have duel uplinks between closets so it is possible to lose a link without losing a device. Works great!
This group also allows us to monitor the CRC errors that the uplink ports are taking, usually as a result of bad fiber. We found this to be useful because many of our K-12 customers have old fiber plants and do not have the funds to replace all their outdated fiber. I created a custom FlexView to monitor these errors and a few other items we found useful, and it works great in Console. At least until this morning.
The problem is that when trying to use this FlexView in OneView NetSight polls every port on every device that has a port in the group. This fails because OneView is trying to process too much data.
Is this a known issue?
In this shot you can see that the UplinkPort group is highlighted but at the right it is displaying the host devices instead of the ports in the group.
In the short term using Console is a simple work around but as you work towards phasing out the Java apps it will become more important for OneView to process this the same a Console does.
Exos 220.127.116.11 Patch 1-2