[cisco-voip] Expressway Clustering...

[Adam Pawlowski]

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 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/20220513/4515f9a8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2491 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20220513/4515f9a8/attachment.png>