enterprise gateway v10

[ashraf55]

hi all ,
could i ask for favor , if anybody have xml created for enterprise gateway and the commend required for the activation of enterprise gateway , also when i need to apply enterprise gateway license and when no need for it .
Regards
Ashraf

 

[member 1453342]

I tried on mine, with your SIPCO and APESU config, I just swapped the shelf 20 to 17. I unplugged the HHS, and the shelf switched over OK to APESU a short while later.

Looks like the HSR messages are normal in that scenario, I get them also.

So, on the switchover, in the HISTA of the CC-AP (so you connect with Comwin to CC-AP, not the HHS), I get this when the problem is detected

F5919 M4 N0020 NO ACT AP-17 LTUC AP EMERGENCY BEGIN 24-08-09 11:14:08
ALARM CLASS:CENTRAL:037
FORMAT:42

F5780 M4 N0021 NO ACT AP-17 DCL AP CONNECTION LOSS 24-08-09 11:14:10
ALARM CLASS:CENTRAL:016
** :LTG1 :LTU17:006: 00 : 0 -- BST:-- PLS:----
FORMAT:43
SWITCH CONTROL TO CC-AP

A9001 M5 N0022 NO ACT AP-17 NMCALARM MAJOR ALARM ON 24-08-09 11:14:22
ALARM CLASS:CENTRAL:037
ALARM NAME:AP EMERGENCY
FORMAT:2C

Then I get quite a lot of these

F5258 E8 N0023 NO ACT AP-17 DCL HSR ADVISORY 24-08-09 11:14:27
ALARM CLASS:CENTRAL:016
FORMAT:42 MESSAGE-ID: 00006 MESSAGE 01 OF 01
ADDR: D018:7C04 ERROR-CODE: C21C
Unexpected message TLI

and then

F5306 E8 N0037 IN SERV AP-17 LTUC IN (ATTENDANCE LIST) 24-08-09 11:15:00
ALARM CLASS:CENTRAL:002
** :LTG1 :LTU17:006: 00 : 0 Q2329-X SoftGate BST:01 PLS:-09
FORMAT:22

followed by normal shelf-coming-in-service stuff.

So your SIPCO and APESU are OK. I didn't see a problem with the XML, maybe I missed something. Cabling maybe?

Check your CC-AP hista for when a switchover should have happened.

 

[ashraf55]

Thank you so much for your help

I have some clarification please attached screen shoot from the current xml file
You can see I marked on direct link of signalling when we should mark it and when not and what it mean as its totally different when I mark or unmark require changes on the ips .

Additionally you can see the IP Address of the AP in the openscape 4000 lan segment is the same as the customer ip of the enterprise gateway is it right or should be changed .
Thanks again for your help

 

[member 1453342]

"Direct Link for Signalling" maps to the UCSU CONNTYPE parameter, which can be APDL (that parameter is ticked) or APNW (it is not ticked).

APNW is used where the IP shelf is in a different subnet to the SIPCO CCA/CCB addresses.
APDL is used where the IP shelf shares the same subnet as CCA/CCB (like yours, 192.168.30.x)

APDL causes the strange IP address you see in the "IP Address of the IP in AP internal Net Segment", which is the IpAddrSig parameter in the XML, and is where you reversed 2nd and 3rd octets, and used 192.30.168. If you ask yourself, why is that? Why not make the signalling IP a "normal" 192.168.30.x IP, it's so a survivability router can be placed between the HHS, and the IP shelf, if the user has that option.

If you get these parameters wrong, the shelf will not come in service at all, and your shelf is working.

You did not send the hista from the CC-AP, from when a switchover should have taken place.