[cisco-voip] Expressway Clustering...

[Jonathan Charles]

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 at 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 at 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 at puck.nether.net> *On Behalf Of *Jonathan
>> Charles
>> *Sent:* Thursday, May 12, 2022 5:10 PM
>> *To:* cisco-voip at 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
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20220514/1ee03a22/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2491 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20220514/1ee03a22/attachment.png>