PG2A not able to connect to controllers on both sides

Unanswered Question
Mar 3rd, 2009

We have side A and side B proggers in our test lab setup. In PG2A pgagent service, the following messages are displaying:

-----------------------------------------

01:00:00 pg2A-pgag Connection to Central Controller side B established (medium priority).

01:00:00 pg2A-pgag Connection to Central Controller side B failed (medium priority).

Last EMT Error [64]: The specified network name is no longer available.

01:00:01 pg2A-pgag Connection to Central Controller side A established (medium priority).

01:00:01 pg2A-pgag Connection to Central Controller side A failed (medium priority).

Last EMT Error [-519897068]: The connection has been closed by the remote process.

-----------------------------------------

PG2B is working fine.

What could be the reason of these errors on PG2A? how to resolve it?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (1 ratings)
geoff@hp.com Wed, 03/04/2009 - 03:21

Just run icm\bin\ICMSetup.exe again and go over the settings carefully.

Regards,

Geoff

lgajdosik Tue, 03/08/2011 - 05:50
/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

Geoff,

Did you point out something specific, or did you thought to go through the setup again in general ?

Rgds, Lg

lgajdosik Tue, 03/08/2011 - 04:56
/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

Hi gents,

Does anyone of you have a solution for this issue ?

We’re facing the same situation and I’ll be glad if you could help me.

Rgds, Lg

klambrec Wed, 03/09/2011 - 11:42

You'd really need to take a look at the overall picture here. We can't guess from this little bit of logs what goes wrong. But assuming you've not changed the configuration (Central Controller hostnames, Logical Controller IDs in the PG Explorer), I'm thinking that there's an issue with the private network on your PG2 machines.

What we're seeing here is that a connection to the central controller is established and then immediately dropped again. The most likely cause I can think of is that CC Agent is refusing this PG2A to register, because it believes this Logical Controller is already connected. Probably the pgagent on PG2B is already Active and connected to the Central Controller, therefor PG2A is rejected.

So in short, check the status of the MDSProc process on both sides of your PG pair and make sure the private network is up.

geoff@hp.com Wed, 03/09/2011 - 13:38

klambrec wrote:

You'd really need to take a look at the overall picture here. We can't guess from this little bit of logs what goes wrong.

Kris, that post was from

Mar 3, 2009

But we need to ask Lg what his problem is. What do his logs show?

If the private communication is over a routed network, you would need persistent static routes on both PGs to deal with the Windows restrictions of a single default gateway for the two NICs. Can you ping the other side of the private network using the hostnames OK? From both machines?

Regards,

Geoff

Benjamin Perez Fri, 03/18/2011 - 10:55

I ran into the same issue.  In my case it was due to an incorrect ICM System ID while setting up the PG.

CSCO11872397 Mon, 03/11/2013 - 11:04

We had the same problem. This was because of duplicate PG number ip "Peripheral Gateway Setup". (We created 2 PG with same ID).  Check correct PG numbering in whole system not only at one host. And recreate PGs with duplicate ID.

Actions

Login or Register to take actions

This Discussion

Posted March 3, 2009 at 10:00 PM
Stats:
Replies:7 Avg. Rating:5
Views:1506 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard