8510 ESS

[joe8413]

Hi,

I'm trying to get this ESS app to work with the following scenario:

Main site: pair of 8720's with cntrl network A 198.152.254.201 and 202
Corp LAN 172.27.0.2 and 3
IPSI 198.152.254.205 port net 1
IPSI 198.152.254.206 port net 2
Def Gateway 198.152.254.253

ESS: S8510 with cntrl network A
Corp LAN 192.168.201.10
198.152.253.201
IPSI 198.152.253.202 port net 3
Def Gateway 198.152.253.353

I have no problems pinging across the network, but for some reason I can't get cabinet 3a to sync. Could there be some port that is being BLOCKED?

I got fed up and took ESS equipment to main site, changed ip's to IPSI's cntrl network and equipment registers with no problem...How can I prove its the customer's network if his argument is that pinging is not an issue?

Thanks...

 

[billybobdan]

I had a similar issue, I could ping and even ssh to the remote IPSI. But it would not come into service.

Issue was that the client had set the remote IPSI switch port as an Access port not a Trunk port.

To prove this I set vlan tagging disabled, then the IPSI came into service

 

[joe8413]

billybobdan,

Avaya engineer corrected the issue by issuing a "cnc status" and then a "cnc on" command under linux. I guess when you have a remote IPSI then a control network C comes to place.

Thanks for your feedback anyways which was also helpful...

 

[billybobdan]

Thanks for the feedback on the resolution.

This may have been caused by the fact that there is no gateway defined for CNA and/or CNB. . Would have to stetup a static route to the IPSI using the cna interface and gateway. Done via the configure server web page on both servers.

By Avaya turning on CNC they will use CNC over the corporate LAN rather than over the CNA subnet.

This may not be what you desire given QOS, Bandwidth and other factors.

 

[jimbojimbo]

If the customer network was correctly configured and isolated then this shouldn't actually work. The issue is that the IP Address of the remote IPSI is not on the same network as the local IPSI. It looks like the intent is to have a private network. This would then require you set up static routes in the server configuration to send the traffic for the specific remote subnets out the corresponding local control network interfaces. Using CNC is an option and we have used it many times however for the IP Addressing scheme you supplied it does not look like the correct method.

 

[joe8413]

jimbojimbo,

The Main site was configured by Avaya and the ESS was configured by my team so we decided to use the same IP scheme that Avaya already had in place for the control network A private LAN. As the ESS was placed across the WAN then we just kept the private network and put the 198.152.253.201 on the IPSI for the ESS and customer did routing towards the 198.152.254.0 network. Nevertheless, customer does not like the IP scheme that Avaya used for the private network in the IPSI's so they will prob change it this year.

I heard that these private networks in Avaya are not being used as much as they were before. What would you suggest?

Thanks for the feedback...