Incorrect status and statitistics reported on some interface
I am trying to monitor an IBM switch (OEM from DLINK) and for some reason OpManager appears to be incorrectly parsing the iftable. I have attached a walk of the iftable as well as a screen capture from OpManager.
I don't know if this is relevant, but I saw this when we were running build 7102. I then performed the updates and restarts as described to update to build 7205.
The issue is most obvious at ifindex 16 and .17. OpManager shows the port 16 to be down and not passing traffic. It shows port 17 to up and passing traffic. I know that 16 (external 2) is up and passing trafic. Port 17 (external 3) is definately down, because it has no cable attached to it.
I would welcome any suggestions on how to have OpManager report the port statuses correctly. If there is additional information that would be useful, please let me know.
I don't know if this is relevant, but I saw this when we were running build 7102. I then performed the updates and restarts as described to update to build 7205.
The issue is most obvious at ifindex 16 and .17. OpManager shows the port 16 to be down and not passing traffic. It shows port 17 to up and passing traffic. I know that 16 (external 2) is up and passing trafic. Port 17 (external 3) is definately down, because it has no cable attached to it.
I would welcome any suggestions on how to have OpManager report the port statuses correctly. If there is additional information that would be useful, please let me know.