2010-03-30 01:50 PM
I have two 3140 controllers installed in my environment setup with cluster failover enabled. Each controller has one management port and 6 ports mvif'ed together (I'll eventually create two nested mvifs inside one svif). The management network is x.x.14.0, the data network is y.y.250.0. We originially set up Operations Manager but had to create a new instance on a server which has connections to both the management and data networks.
DFM/Ops Mgr server:
The problem is that I can't get the DFM server to connect to either controller.
I've ran dfm host diag on both controllers' Mgmt and Data IPs and get the same result:
Q:\Documents and Settings\DFM>dfm host diag xx.xx.14.71
IP Address xx.xx.14.71
DNS Aliases xx.xx.14.71
SNMP Version in Use SNMPv1
SNMPv1 Failed: Timeout
SNMP Community public
SNMPv3 Failed: No SNMPv3 username specified.
ICMP Echo Passed (0 ms)
HTTP Passed (0 ms)
Host Agent Connect Failed (transport http; port 4092)
On the controller I have the following SNMP options set:
hostname_a> options snmp
zz.zz.zz.zz (zz.zz.zz.zz) <zz.zz.zz.zz>
Any idea why DFM can't connect to the controllers? Thanks!
Solved! SEE THE SOLUTION
2010-03-30 01:59 PM
It looks like DFM is configured to use a different SNMP community string to that on the Filer(s).
From dfm host diag:
SNMP Community public
If all your Filers run the same SNMP community string the easiest way to fix this is to change the default SNMP community string in DFM to match that on your Filers.
dfm snmp modify -c CompanyName default
If you have different SNMP community strings on different subnets then you may have to add different SNMP rules to DFM.
Hope this helps.
2010-03-31 12:12 AM
It is good to use Operations Manager's "Configuration Management" feature to avoid any inconsistencies (or errors) on configurations across related storage system/vfiler. It is also provides other powerful features like compare configurations, upgrade/revert a configuration to a required ontap version, etc.
Please refer to "Remote Configuration" section of "Operations Manager Administration Guide" for more details.
2010-03-31 09:52 AM
If you dont wish to change the snmp community on the filer add each of the community in dfm using the following command.
[root@lnx ~]# dfm snmp add help
add -- Specify credentials and community name for SNMP discovery and monitoring on this network.
dfm snmp add [ -m mask ] [ -v prefsnmpVersion ] [ -c communityName ]
[ -U <hostLogin> -P <hostPassword> ] [ -A <authProtocol> ]
[ -X <privPassword> ] <address>
-v: Possible values are 1 and 3. Default value
is 1. If specified as 3, then hostLogin and
hostPassword is mandatory. If specified as 1,
then communityName is mandatory.
For discovery, the value in this option will be
tried first. If it fails then the other SNMP version
will be tried if it has not been disabled. However
note that for monitoring, only the version specified
in this option will be tried.
-U: The name of the user to be used for SNMPv3
discovery and monitoring. Mandatory when
prefsnmpVersion is 3.
-P: The authentication password to be used for
SNMPv3 communication. Value must be a string greater
than or equal to 8 characters. Mandatory when
hostLogin is specified.
-m: Can be either dotted mask/prefix length in case of
IPv4 address, and prefix length in case of
-A: Authentication protocol for use with SNMPv3. Valid values are MD5 and
SHA. If not specified, MD5 is the default value.
-X: Privacy password used for encrypting SNMPv3 communication.
DES protocol is used for encryption.