Currently, I've got sensors running on 2.5 and director on 2.2.3 (sol26/sparc) with HPOV NNM 6.1. In the near future I will upgrade the sensors to v3.0 and install the appropriate director service packs, and maybe upgrade the director to sol8.
Will any of this be compatible with HPOV NNM 6.2?
Another question: Even though the director is running v2.2.3 (at least, thats what I think it does), idsvers tells me that the signature version is 18.104.22.168 and the daemons are running 2.2.1 or 22.214.171.124. Is this correct? The version file shows 2.2.3 though.
The Unix director 2.2.3 is not officially supported with HPOV NNM 6.2.
But You can manage v3.0 sensors to with the director2.2.3 running on sol8 with HPOV NNM6.1.
Regarding version information, what you are seeing is the correct information. The signature version would show you the signature update you have on your director. The idsvers output would show you the versions of the different components of unix director. 2.2.3 install updates the postofficed, sapd and smid components.
The Unix Director was based off version 1 of the libraries.
I was told that HP would still sell and support OV 6.1 for a time because of this change.
I think there may be patches you have to download to get OV 6.1 to work on Solaris 8?
As for the Signature Level you, you are still back on signature update 126.96.36.199, while the latest in the field is S10. Just so you know, about a year ago we went to a new signature level numbering convention using the "S" designator. You 188.8.131.52 signatures are about the equivelant of the old S2 signature level of the sensors.
So if you are managing 3.0(2)S10 sensors, you would need to download and install the S10 signature update for the directors.
NOTE: As you noticied, 2.2.3 does not update the signature level of the director, you have to apply the signature update as a separate file.
NOTE2: nrvers won't tell you if 2.2.3 is loaded. It only tells you the signature level and the version of specific daemons.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...