topic Re: OSSV host name truncated on DFM in Active IQ Unified Manager Discussions

OSSV host name truncated on DFM

BRIANLIU11 — Thu, 05 Jun 2025 06:37:22 GMT

Hi there,

A few OSSV hosts have been successfully added to DFM but they look quite different in description.

Some of them show as fully qualified domain name and some else not. Please see this,

> dfbm primary host list

ID:	2724
Primary System:	2304cpc1.infra.det.win

Primary Directories:

NDMP Password:	******
NDMP User:	test

NDMP Port:

ID:	2665
Primary System:	1744cpc1

Primary Directories:

NDMP Password:	******
NDMP User:	test

NDMP Port:

> DNS lookup

--------

PS C:\Users> nslookup 2304cpc1.infra.det.win

Server: pugdc01.itbntu.det.nsw.edu.au

Address: 153.107.78.120

Non-authoritative answer:

Name: 2304cpc1.infra.det.win

Address: 10.26.66.41

PS C:\Users> nslookup 1744cpc1.infra.det.win

Server: pugdc01.itbntu.det.nsw.edu.au

Address: 153.107.78.120

Non-authoritative answer:

Name: 1744cpc1.infra.det.win

Address: 10.15.21.41

They run on the same domain "infra.det.win" but the second host whose name has been truncated ended up failing on streaming the dataset.

Re: OSSV host name truncated on DFM

stjerna — Wed, 18 Jan 2012 10:12:17 GMT

Hi,

You don't mention what version of DFM/Operations Manager you are using.

There's a fix in Operations Manager 4.0.2D4 for BURT 479828 which seems it could be a match:

http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=479828

Hope this helps,

Erik

Re: OSSV host name truncated on DFM

adaikkap — Wed, 18 Jan 2012 10:51:39 GMT

As Erik,mentioned you are facing bug 479828. Pls add an /etc/hosts entry in your filers as a work around. This bug is also fixed in upcoming GA release of 5.0 namely 5.0.1

Regards

adai

Re: OSSV host name truncated on DFM

BRIANLIU11 — Wed, 18 Jan 2012 21:54:44 GMT

Thanks Erik and Adai. My DFM (OnCommand) version is 5.0.0.7636 (5.0).

Re: OSSV host name truncated on DFM

stjerna — Thu, 19 Jan 2012 09:17:24 GMT

Ok, so since 5.0.1 is not out just yet, just give the /etc/hosts workaround a try. I have used this before at a customer site but never really understood it was a bug 🙂 Just noticed the secondary could not reach the source(s) and started poking around from there.