![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2171362.1 : CVE-1999-0517 An SNMP community name is the default (e.g. public), null, or missing on an Infiniband Switch
In this Document
Applies to:Sun Datacenter InfiniBand Switch 36 - Version All Versions and laterSun Network QDR InfiniBand Gateway Switch - Version All Versions and later Information in this document applies to any platform. SymptomsA security scanner flags ChangesNo changes were done to Simple Network Management Protocol (SNMP) configuration. CauseThis CVE is a configuration proposal, it is flagged when a SNMP community name is the default (e.g. the string "public"). If this is an intended configuration, this can be probably kept. SolutionOption 1 - disable SNMPIf you do not use SNMP on the infiniband switch and Exadata, you can potentially disable it. Access the Oracle ILOM CLI ( See Accessing Oracle ILOM From the CLI). -> set /SP/services/snmp servicestate=disabled
Set ’servicestate’ to ’disabled’
Option 2 - change the community stringIf you use SNMP, you can change the community strings. This is done on all systems and related management software (e.g. Enterprise Manager). On the IB switch, in general, a new snmp community name can be configured on the ILOM of the IB switches. For example, to add the community newcom: -> create /SP/services/snmp/communities/newcom permission=rw
Created /SP/services/snmp/communities/newcom The SNMP community newcom is added. Then you can disable the unwanted community : - delete community private: -> delete /SP/services/snmp/communities/private
Option 3 - use SNMPv3If your environment supports it, you can also use just SNMPv3, Note - Before any re-configuration on an Engineered System, pls. check with support for your Engineered System specifics.
Attachments This solution has no attachment |
||||||||||||||||||||||||
|