Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Openscape 4K V10.0 enterprise gateway issue

Status
Not open for further replies.

LAAZ

Systems Engineer
Aug 4, 2021
111
IN
Dear friends

I have installed OS4K v10 R1.34.0 duplex with enterprise gateway with 2 LTUCR.

Whwn LAN disconnected ,EGW wait for 5 mineutes and restarted and APE is working fine.

While reconnecting the LAN the system not resumed to normal,but working in APE mode only .

I was waiting for more than 30 mineutes and no switching happen.

So I manually switched to Normal mode.

Have any one faced same issue and what will be the solution for it.

Thanks in Advance
 
As SBCSU said, DISP-APESU; and post here.

EGw wont come back into normal state on auto pilot.
It depends pod many parameters, such as threshold, switchover window and minimum requirement for stable connection which are all configurable.
 
Dear Friends

please see below the APESU

ADD-APESU:CCAP,19,192.168.1.24;
ADD-APESU:APEGRP,2,19,50,AUTO,APEGRP2,1,0,0,0;
ADD-APESU:AP,19,2,50,GROUP;
 
Your SG20 is not connected with the Host nor the APE.
What is SG20, is that Survivable or Non-Survivable?
Have you done replication through HBR?
Can you share the XML of SG20?
 
I don't see any problem with LTU 19
LTu 20 has no connection.

To force a remote site to re-connect to the main site:
EXECUTE-APESU:SYSMODE=NORMAL,LEVEL=AP;
 
Hi Friends

LTU 19 and LTU 20 are working ,

IP address for LTUs are used same IP 192.168.1.26

ADD-UCSU:ENTGW,1,19,"Q2347-X ",19,AP370013,APDL,
192.168.1.26,192.168.1.1,
019,"NEWTAJ ",
,,YES,120,NO,
0,0,IPV4,NO,NO,2,7,7,,,11,HSRTCP
,,
,7,1
;
ADD-UCSU:ENTGW,1,20,"Q2347-X ",19,AP370013,APDL,
192.168.1.26,192.168.1.1,
019,"NEWTAJ ",
,,YES,120,NO,
0,0,IPV4,NO,NO,2,7,7,,,11,HSRTCP
,,
,7,2
;
 
Please:

CHA-FUNCT:REGIN=Y;
REG-SIPCO;
REG-APRT;

 
REGIN = y;
CHA-FUNCT:,,,,,,,,,,,,,,Y;
H500: AMO FUNCT STARTED

AMO-FUNCT-111 SYSTEM SWITCHES
CHANGE COMPLETED;
<reg-aprt;
REG-APRT;
H500: AMO APRT STARTED
ADD-APRT:APNET,19,192.168.2.103,255.255.255.0,0.0.0.0;

AMO-APRT -111 ACCESS POINT ROUTING TABLE
REGENERATE COMPLETED;
<reg-sipco;
REG-SIPCO;
H500: AMO SIPCO STARTED
ADD-SIPCO:192.168.1.0,255.255.255.0,IPV4,192.168.1.1,192.168.1.16,192.168.1.17,0
.0.0.0,N,N;
CHANGE-SIPCO:LSNET,,,,,,,,,,0.0.0.0,0.0.0.0,0.0.0.0;
CHANGE-SIPCO:DIFFSERV,184,104,N,0,16384;
CHANGE-SIPCO:TIMING,60,300,4,5,60;
CHANGE-SIPCO:pLQUAL,200,120,10,4;
CHANGE-SIPCO:BANDW,15,36,;
CHANGE-SIPCO:DMCDATA,N,"G711";
CHANGE-SIPCO:SECURITY,N,24,"128CBC";
 
<cha-funct
CMDECHO =
AMOOK =
AMOHDR =
SUSY =
RTOADS =
RTOTFS =
RTOVMS =
LANG =
SPLIT =
RETENT =
POWERSYS =
PFI =
SS7CTR =
SLANG =
REGIN = ?
REGIN : REGEN OUTPUT INPUT USABLE
CHARACTERISTIC : OPTIONAL
POSS. VALUES : Y YES
N NO
REGIN = yes;
 
You only have one APRT entry ?
Where is the APRT entry for Branch/Shelf 20 ?


CHA-FUNCT:REGIN=Y; is called 'Keyword orientated' - it works just as well as the long winded way of CHA-FUNCT:,,,,,,,,,,,,,,Y;

If you log on via Comwin and then click up top 'Macro / Retreive System Variant' - the Comwin will then know what version of 4K you have.
You can then use Comwin Edit
To use Comwin edit - right mouse click on any command and click MML editor - or just hit CTRL and TAB
This MML editor / Comwin Edit will give you the correct commands for your version of 4K
You can decide on Language EN or DE and decide on Keyword or Position orientated commands.
Give it a try !



 
It's using the new V10 R1 feature where one EntGW will support two physical LTU shelves, so it's correct that there is only one APRT. You can see the config at the end of the UCSU line, 7,1 and 7,2. Shelf ID 7, shelf 1, and Shelf ID 7, shelf 2.

Never tried it with APESU though.

First thing I would do is get it on V10 R1.42 with latest HFs. This is a newish feature so a few bugs may have been ironed out.
 
Well that is certainly good to know and a good feature, hopefully it'll work out.
 
I was thinking about this second shelf. It doesn't make any sense to add it in the APESU. Whatever happens to the IP connection between the HHS and the SG would surely happen to both shelf 1 and shelf 2. There isn't really any need to differentiate between the shelves in the APESU. And looking at the 2nd shelf in the APESU output, we can safely say it is not happy.

I had a look in the Enterprise Gateway documentation. In the section on how to convert a single shelf EntGW to a double shelf, it says to delete the first shelf then re-add both, but it also says :

AP Emergency:
Before deleting an AP shelf in APRT, it needs to be removed from the AP Emergency Group. Afterwards, only Shelf 1 needs to be added again. There is no need to add the second shelf.


So I think here I would delete shelf 20 from the APESU, check weights, make new backup, retest.
 
To add a second shelf in EGW


Reg-aprt;

Del-aprt:apnet,19;

Cha-ucsu:unit=entgw,ltu=19,xegwid=7,xegwshlf=1;

Add the new shelf 20 with xegwid=7,xegwshlf=2;

Add-aprt:apnet,19,192.168.2.103,255.255.255.0;(no need to add aprt for shelf 20)

Exe-ussu:confap,19;

Exe-ussu:confap,20;
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top