garethb1 Absent Member.
Absent Member.
1891 views

Agent Binding to NIC with multiple Bonded NICs and VLANS

Hi

I am having an issue with agent communication where the agent installs on a server, but is then unable to communicate correctly with the primary servers. This error is typically reported through the Zenworks agent status in ZCC "Unable to connect to the agent service through the IP Address or DNS."

It seems that when the agent installs it selects what it deems to be the primary NIC and then binds to this address. I have a large number of servers within my deployment domain and whilst in some instances it will be relatively straight forwadr to change the binding order in other instances this can be quite complex and will greatly increase the complexity and timeframe for our deployment project. Can anyone help with my questions below.

1 Can anyone confirm that this is indeed the default behaviour ?

2 Is there any way to specify the specific interface for the agent to bind to ?

3 Does anyone have any practical examples of workarounds for this issue ?

Many Thanks
Gareth
Labels (2)
0 Likes
3 Replies
Micro Focus Expert
Micro Focus Expert

Re: Agent Binding to NIC with multiple Bonded NICs and VLANS

Find the Server in the ZCC, Select the Settings Tab and Modify the
"Restricted IP Addresses" to tell devices to not use a specific address.



On 4/26/2012 5:56 AM, garethb wrote:
>
> Hi
>
> I am having an issue with agent communication where the agent installs
> on a server, but is then unable to communicate correctly with the
> primary servers. This error is typically reported through the Zenworks
> agent status in ZCC "Unable to connect to the agent service through the
> IP Address or DNS."
>
> It seems that when the agent installs it selects what it deems to be
> the primary NIC and then binds to this address. I have a large number of
> servers within my deployment domain and whilst in some instances it will
> be relatively straight forwadr to change the binding order in other
> instances this can be quite complex and will greatly increase the
> complexity and timeframe for our deployment project. Can anyone help
> with my questions below.
>
> 1 Can anyone confirm that this is indeed the default behaviour ?
>
> 2 Is there any way to specify the specific interface for the agent to
> bind to ?
>
> 3 Does anyone have any practical examples of workarounds for this issue
> ?
>
> Many Thanks
> Gareth
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
garethb1 Absent Member.
Absent Member.

Re: Agent Binding to NIC with multiple Bonded NICs and VLANS

Hi Craig thanks for the update.

I was looking at this option for the target server where the agent is installed, but it tells me this is only available for ZenWorks Servers ?

I have two primary servers in my environment are you suggesting I can add the addresses to exclude here and this will have an impact on the servers where the agent is installed ?

Thanks
Gareth
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Agent Binding to NIC with multiple Bonded NICs and VLANS

On the Agent, it should use all installed NICs.
It does not really bind to any NIC but simply sends out to the server's
IP address.


On 4/26/2012 9:06 AM, garethb wrote:
>
> Hi Craig thanks for the update.
>
> I was looking at this option for the target server where the agent is
> installed, but it tells me this is only available for ZenWorks Servers
> ?
>
> I have two primary servers in my environment are you suggesting I can
> add the addresses to exclude here and this will have an impact on the
> servers where the agent is installed ?
>
> Thanks
> Gareth
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.