Mailing List Archive

A few thoughts.
Clustering does require H323 to be enabled.
Check DNS resolution
if Expressway-E, you can statically define name resolution for peers in
the case where the defined DNS might not be able to resolve the peers
"inside" address

On Thu, May 12, 2022 at 4:19 PM Jonathan Charles <jonvoip@gmail.com> wrote:

> Howdy!
>
> We are seeing an error on our Expressway E nodes right after we form a
> cluster.
> The cluster is up and fully operational, however, we get:
>
> Peer Not Responding
> A peer address for the LocalZone local zone is down and unreachable.
>
> It then tells you to check the zones page and verify the failing peer
> address...
>
> There are no zones configured, as of yet... just the DefaultZone and it
> has no option for peers to be configured.
>
> The LocalZone also has no peer configuration as an option.
>
> Any ideas?
>
>
> Thanks!
>
>
> Jonathan
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

Another thing, the clustering is kind of funky, so you need to make sure they are listed in the same order on both nodes.  Sent from my T-Mobile 5G Device
-------- Original message --------From: Brian V <bvanbens@gmail.com> Date: 5/12/22 3:24 PM (GMT-08:00) To: Jonathan Charles <jonvoip@gmail.com> Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] Expressway Clustering... A few thoughts.Clustering does require H323 to be enabled.Check DNS resolution if Expressway-E,  you can statically define name resolution for peers in the case where the defined DNS might not be able to resolve the peers "inside" addressOn Thu, May 12, 2022 at 4:19 PM Jonathan Charles <jonvoip@gmail.com> wrote:Howdy! We are seeing an error on our Expressway E nodes right after we form a cluster.The cluster is up and fully operational, however, we get:Peer Not RespondingA peer address for the LocalZone local zone is down and unreachable.It then tells you to check the zones page and verify the failing peer address...There are no zones configured, as of yet... just the DefaultZone and it has no option for peers to be configured.The LocalZone also has no peer configuration as an option.Any ideas?Thanks!Jonathan
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

We ran into something similar in the past where things get generated in the background but aren’t visible in the GUI.

Traversal zones that allocate ports for disabled protocols, but then throw an alarm about port conflicts as they’re configured.

From what I can tell, LocalZone should have been a zone in VCS land, but has since disappeared from Expressway. It may be floating in the background somewhere and may be worth a look through the xapi to see if it’s visible and get poked.

Adam Pawlowski
Network Engineer?| Network and Communication Services
University at Buffalo Information Technology (UBIT)
243 Computing Center, Buffalo, NY 14260
[contact_line]

From: cisco-voip <cisco-voip-bounces@puck.nether.net> On Behalf Of Jonathan Charles
Sent: Thursday, May 12, 2022 5:10 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Expressway Clustering...

Howdy!

We are seeing an error on our Expressway E nodes right after we form a cluster.
The cluster is up and fully operational, however, we get:

Peer Not Responding
A peer address for the LocalZone local zone is down and unreachable.

It then tells you to check the zones page and verify the failing peer address...

There are no zones configured, as of yet... just the DefaultZone and it has no option for peers to be configured.

The LocalZone also has no peer configuration as an option.

Any ideas?


Thanks!


Jonathan

I am seeing H.225 RAS messages being sent and not replied to on both E's...
all UDP 1719...

My firewall guys say they see no port 1719 traffic, but the pcaps show
1719...

Joy.


Jonathan

On Fri, May 13, 2022 at 9:11 AM Adam Pawlowski <ajp26@buffalo.edu> wrote:

> We ran into something similar in the past where things get generated in
> the background but aren’t visible in the GUI.
>
>
>
> Traversal zones that allocate ports for disabled protocols, but then throw
> an alarm about port conflicts as they’re configured.
>
>
>
> From what I can tell, LocalZone should have been a zone in VCS land, but
> has since disappeared from Expressway. It may be floating in the background
> somewhere and may be worth a look through the xapi to see if it’s visible
> and get poked.
>
>
>
> *Adam Pawlowski*
>
> Network Engineer?| Network and Communication Services
>
> University at Buffalo Information Technology (UBIT)
>
> 243 Computing Center, Buffalo, NY 14260
>
> [image: contact_line]
>
>
>
> *From:* cisco-voip <cisco-voip-bounces@puck.nether.net> *On Behalf Of *Jonathan
> Charles
> *Sent:* Thursday, May 12, 2022 5:10 PM
> *To:* cisco-voip@puck.nether.net
> *Subject:* [cisco-voip] Expressway Clustering...
>
>
>
> Howdy!
>
>
>
> We are seeing an error on our Expressway E nodes right after we form a
> cluster.
>
> The cluster is up and fully operational, however, we get:
>
>
>
> Peer Not Responding
>
> A peer address for the LocalZone local zone is down and unreachable.
>
>
>
> It then tells you to check the zones page and verify the failing peer
> address...
>
>
>
> There are no zones configured, as of yet... just the DefaultZone and it
> has no option for peers to be configured.
>
>
>
> The LocalZone also has no peer configuration as an option.
>
>
>
> Any ideas?
>
>
>
>
>
> Thanks!
>
>
>
>
>
> Jonathan
>

OK, so my firewall guys were, um, let's say 'misinformed...'

I grabbed packet captures from both Expressways, saw 1719 UDP RAS messages
being sent on both sides and neither one receiving them.... sent them off
to the firewall weirdos, they said, 'oh...' and then add an allow and the
error cleared.

Yay.

Jonathan

On Fri, May 13, 2022 at 9:25 AM Jonathan Charles <jonvoip@gmail.com> wrote:

> I am seeing H.225 RAS messages being sent and not replied to on both
> E's... all UDP 1719...
>
> My firewall guys say they see no port 1719 traffic, but the pcaps show
> 1719...
>
> Joy.
>
>
> Jonathan
>
> On Fri, May 13, 2022 at 9:11 AM Adam Pawlowski <ajp26@buffalo.edu> wrote:
>
>> We ran into something similar in the past where things get generated in
>> the background but aren’t visible in the GUI.
>>
>>
>>
>> Traversal zones that allocate ports for disabled protocols, but then
>> throw an alarm about port conflicts as they’re configured.
>>
>>
>>
>> From what I can tell, LocalZone should have been a zone in VCS land, but
>> has since disappeared from Expressway. It may be floating in the background
>> somewhere and may be worth a look through the xapi to see if it’s visible
>> and get poked.
>>
>>
>>
>> *Adam Pawlowski*
>>
>> Network Engineer?| Network and Communication Services
>>
>> University at Buffalo Information Technology (UBIT)
>>
>> 243 Computing Center, Buffalo, NY 14260
>>
>> [image: contact_line]
>>
>>
>>
>> *From:* cisco-voip <cisco-voip-bounces@puck.nether.net> *On Behalf Of *Jonathan
>> Charles
>> *Sent:* Thursday, May 12, 2022 5:10 PM
>> *To:* cisco-voip@puck.nether.net
>> *Subject:* [cisco-voip] Expressway Clustering...
>>
>>
>>
>> Howdy!
>>
>>
>>
>> We are seeing an error on our Expressway E nodes right after we form a
>> cluster.
>>
>> The cluster is up and fully operational, however, we get:
>>
>>
>>
>> Peer Not Responding
>>
>> A peer address for the LocalZone local zone is down and unreachable.
>>
>>
>>
>> It then tells you to check the zones page and verify the failing peer
>> address...
>>
>>
>>
>> There are no zones configured, as of yet... just the DefaultZone and it
>> has no option for peers to be configured.
>>
>>
>>
>> The LocalZone also has no peer configuration as an option.
>>
>>
>>
>> Any ideas?
>>
>>
>>
>>
>>
>> Thanks!
>>
>>
>>
>>
>>
>> Jonathan
>>
>

+???? for firewall weirdos. ;)

Sent from my iPhone

On May 14, 2022, at 12:03 PM, Jonathan Charles <jonvoip@gmail.com> wrote:

?

CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp@uoguelph.ca


OK, so my firewall guys were, um, let's say 'misinformed...'

I grabbed packet captures from both Expressways, saw 1719 UDP RAS messages being sent on both sides and neither one receiving them.... sent them off to the firewall weirdos, they said, 'oh...' and then add an allow and the error cleared.

Yay.

Jonathan

On Fri, May 13, 2022 at 9:25 AM Jonathan Charles <jonvoip@gmail.com<mailto:jonvoip@gmail.com>> wrote:
I am seeing H.225 RAS messages being sent and not replied to on both E's... all UDP 1719...

My firewall guys say they see no port 1719 traffic, but the pcaps show 1719...

Joy.


Jonathan

On Fri, May 13, 2022 at 9:11 AM Adam Pawlowski <ajp26@buffalo.edu<mailto:ajp26@buffalo.edu>> wrote:
We ran into something similar in the past where things get generated in the background but aren’t visible in the GUI.

Traversal zones that allocate ports for disabled protocols, but then throw an alarm about port conflicts as they’re configured.

From what I can tell, LocalZone should have been a zone in VCS land, but has since disappeared from Expressway. It may be floating in the background somewhere and may be worth a look through the xapi to see if it’s visible and get poked.

Adam Pawlowski
Network Engineer?| Network and Communication Services
University at Buffalo Information Technology (UBIT)
243 Computing Center, Buffalo, NY 14260
[image001.png]

From: cisco-voip <cisco-voip-bounces@puck.nether.net<mailto:cisco-voip-bounces@puck.nether.net>> On Behalf Of Jonathan Charles
Sent: Thursday, May 12, 2022 5:10 PM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] Expressway Clustering...

Howdy!

We are seeing an error on our Expressway E nodes right after we form a cluster.
The cluster is up and fully operational, however, we get:

Peer Not Responding
A peer address for the LocalZone local zone is down and unreachable.

It then tells you to check the zones page and verify the failing peer address...

There are no zones configured, as of yet... just the DefaultZone and it has no option for peers to be configured.

The LocalZone also has no peer configuration as an option.

Any ideas?


Thanks!


Jonathan
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip