You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

The table below describes which combinations of Opmantek products are tested and work well with what versions of NMIS and MongoDB.

 

ProductProduct VersionNMIS VersionMongoDB VersionNotes
opConfig 2.2.0>= 8.5.0, <= 8.5.8G2.4

opConfig 2.2.0 won't be able to report config

changes to NMIS if you run it with NMIS 8.5.10G

opConfig2.2.2>= 8.5.10G2.4, 2.6 or 3.0 
opConfig2.2.4>= 8.5.10G2.4, 2.6 or 3.0 
opHA2.1.2>= 8.5.0, <= 8.5.8GN/A

opHA 2.1.2 won't be able to transfer NMIS event statuses

if you run it with NMIS 8.5.10G

opHA2.1.4>= 8.5.10GN/A 
opExport1.6.7>= 8.5.0, <= 8.5.8GN/A 
opExport1.6.8>= 8.5.10GN/A 
opFlow2.5.1>= 8.5.0, <= 8.5.8G2.4 
opFlow2.5.2>= 8.5.10G2.4, 2.6 or 3.0 
opEvents1.2.4>= 8.5.02.4 
opEvents1.2.6, 2.0.0, 2.0.2>= 8.5.10G2.4, 2.6 or 3.0 
opReports3.0.2>= 8.5.0N/A 
opCharts2.4.12>= 8.5.6GN/A 
opTrend1.2.1>= 8.5.6G, <= 8.5.8G2.4

opTrend's config optrend_process_condition_in_nmis must

be disabled if you run this version with NMIS 8.5.10G

opTrend1.2.3>= 8.5.10G2.4, 2.6 or 3.0 
opAddress1.0.4> 8.5.02.4 
opAddress1.0.5>= 8.5.10G2.4, 2.6 or 3.0 
opMaps

2.2.2 (broken),

2.2.1 (working)

compiled somewhere before NMIS 8.4.8G

 Works with any NMIS running .nmis files that still uses -view files (uses them to get interface info, must be in .nmis format)
  • No labels