Re: [Networker] Integration between Data Domain and NetWorker

To check the community string.

1. ssh into the DD system
2. Enter "snmp show rw-communities". This will list all of the community
strings defined.
3. You can use any of these in NMC. If you don¹t see any, create one using
"snmp add rw-community <your string here>".

In NMC
1. Click Enterprise on the main task bar.
2. Right click on the DD system and select Properties...
3. In the Properties dialog, click the SNMP Monitoring tab.
4. Verify the SNMP community string matches the one set on the DD system.

Cheers,
Skip

On 5/4/11 9:47 AM, "STANLEY R. HORWITZ" <stan AT temple DOT edu> wrote:

>Skip,
>
>How do I check that the community string is correct in NMC? SNMP is
>definitely enabled on the DD system.
>
>On 5/4/2011 12:36 PM, "Skip Hanson" <skip.hanson AT EMC DOT COM> wrote:
>
>>Hello. I would make sure the SNMP Community string for the DD system is
>>correct in NMC. You can rsh into the DD system to get the list of Public
>>community strings. Also make sure SNMP is enabled for the DD system.
>>
>>Cheers,
>>Skip
>>
>>On 5/4/11 8:51 AM, "STANLEY R. HORWITZ" <stan AT TEMPLE DOT EDU> wrote:
>>
>>>I am in the process of testing a brand new NetWorker data zone with a
>>>new
>>>Data Domain 860, DD Boost, a new Dell server running 64-bit Red Hat
>>>Linux
>>>and 64-bit NetWorker 7.6 SP2 RA, and two new Spectralogic T50e tape
>>>libraries with LTO-5 tape drives in them.
>>>
>>>One little glitch I am encountering is that in the NetWorker Management
>>>Console (which runs on its own server), every time I click on the DD
>>>device resource entry, I get a pop-up window that says:
>>>
>>>"Error gathering SNMP event and usage information for 'ddinternal1'.
>>>Make sure SNMP is enabled on the system and the system is reachable."
>>>
>>>Note that "ddinternal1" is the short name for the network link (10GigE
>>>Fiber) between the new NetWorker server and the DD 860. I can ping this
>>>name from the server and backups to it work fine. People from EMC are
>>>looking into this situation, but thus far, the problem continues. I am
>>>wondering if anyone on this mailing list has encountered this problem
>>>and
>>>if so, how did you fix it?
>>>
>>>To sign off this list, send email to listserv AT listserv.temple DOT edu and
>>>type "signoff networker" in the body of the email. Please write to
>>>networker-request AT listserv.temple DOT edu if you have any problems with 
>>>this
>>>list. You can access the archives at
>>>http://listserv.temple.edu/archives/networker.html or
>>>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>>>
>>
>>To sign off this list, send email to listserv AT listserv.temple DOT edu and
>>type "signoff networker" in the body of the email. Please write to
>>networker-request AT listserv.temple DOT edu if you have any problems with 
>>this
>>list. You can access the archives at
>>http://listserv.temple.edu/archives/networker.html or
>>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER