Brocade Fibre Channel Networking Community

Expand all | Collapse all

Hitachi hitrack

  • 1.  Hitachi hitrack

    Posted 8 days ago
    Morning Everyone, I'm encountering communication errors on hitrack remote ops monitor agent polling several brocade switches in several geographical areas. The switches themselves are not reporting any errors it's just the hitrack monitoring. example

    SWFCIP71_SEDC SEDC-DC75 FCIP Replication Brocade 7800  Okay 2019/12/02 08:20:50

    Thanks in advance.


  • 2.  RE: Hitachi hitrack

    Posted 8 days ago

    Status is showing as 'Okay' and timestamp for last communication update looks current, so I can't see evidence of a communication error from your example.




  • 3.  RE: Hitachi hitrack

    Posted 6 days ago
    My apologies, the screenshot provided does not show the image for Okay. The image is yellow (yield) and as you can see from the dashboard image below it is posting a comms.error.

    Device Error Comms. Error Device Okay Not Monitored Total Devices
    0 1 30 0 31
    Refresh Devices / Page
    Secs.




  • 4.  RE: Hitachi hitrack

    Posted 6 days ago
    Really need more information. 'Comms. Error' covers a multitude of issues. A start would be the contents of the 'Status' box that will be in the 'Communication Errors' section that sits just above all of the 'Devices Okay' in Hi-Track.

    Next to the status error in that box is an icon that looks like a 'D'. Click on that and it will give you further information.

    Fundamentally, communication issues from Hi-Track to Brocade will likely fall in to two main areas. Either an IP connectivity issue or an SNMP configuration issue. For the former, ensure basic IP connectivity between server hosting Hi-Track and the switch in both direction. Check for any firewall ports (including IPTables on the switch) that might be blocking SNMP. For the latter, make sure you've setup SNMP correctly on the switch and that that configuration is matched when entering the switch details in Hi-Track.





  • 5.  RE: Hitachi hitrack

    Posted 6 days ago

    Calvin, thanks for your input. Although my first thoughts were this is a network issue I believe from a core router change I did find a work around/fix, advice from Hitachi support states that I should edit the HitDFmon.config file with Admin privileges. Gonna give it a go and see what's up. Thanks again