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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OS Access PRI mdoule & OS4K branch

Status
Not open for further replies.

yayayoyo

Programmer
Jul 20, 2015
57
DE
Hey Guys !

i couldn't connect my new Openscape Access PRI mdoule (S30807-U6648-X170-16) to the Openscape 4000 Branch (V8 R1.19) ,
dis-bcsu -> it shows me "defect" .

but when i use an old hipath access PRI module (S30807-U6648-X170-12 ) with the same configuration & the same OS branch everything work well and the board is "ready".


i used all the last hotfixes

Thank you,
 
Hi,
Can you log on to the HiPath/OS4KV8 and
DIS-BCSU;

 
If you really are on the latest loadware I would expect at first this is the wrong MAC address for the new PRI module.
 
@sbcsu here is the creation and the display of the bcsu .

ADD-BCSU:MTYPE=DIU,LTG=1,LTU=30,SLOT=15,PARTNO="Q2335-X",LWVAR="0",FCTID=1,HWYBD
L=A,ALARMNO=0,MACADDR=00-1A-E8-3D-4B-70,TDMLAW=0;
ADD-BCSU:MTYPE=DIU,LTG=1,LTU=30,SLOT=15,PARTNO="Q2335-X",LWVAR="0",FCTID=1,
HWYBDL=A,ALARMNO=0,MACADDR=00-1A-E8-3D-4B-70,TDMLAW=0;
H500: AMO BCSU STARTED
H01: BD 1.30. 15 ASSIGNED

AMO-BCSU -111 BOARD CONFIGURATION, SWITCHING UNIT
ADD COMPLETED;
<ADD-BCSU:MTYPE=DIU,LTG=1,LTU=30,SLOT=16,PARTNO="Q2335-X ",LWVAR="0",FCTID=1
,HWYBDL=A,ALARMNO=0,MACADDR=00-1A-E8-3D-11-1E,TDMLAW=0;
ADD-BCSU:MTYPE=DIU,LTG=1,LTU=30,SLOT=16,PARTNO="Q2335-X ",LWVAR="0",FCTID=1,
HWYBDL=A,ALARMNO=0,MACADDR=00-1A-E8-3D-11-1E,TDMLAW=0;
H500: AMO BCSU STARTED
H06: PARAMETER LWVAR WILL BE IGNORED, SIMILAR MODULE TYPE ALREADY ASSIGNED.
VARIANT CAN BE CHANGED USING AMO ZAND.
H01: BD 1.30. 16 ASSIGNED

AMO-BCSU -111 BOARD CONFIGURATION, SWITCHING UNIT
ADD COMPLETED;
<
<DISPLAY-BCSU:TYPE=TBL,LTU=30,SLOT=15;
DISPLAY-BCSU:TYPE=TBL,LTU=30,SLOT=15;
H500: AMO BCSU STARTED

LTG 1 LTU 30 SRCGRP 1 ALARMNO-LTU 0 SOFTGATE1000 240 PORTS USED
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
| | | |S|H|AL-| | | |
| ASSIGNED | MODULE |FCT|E|W|ARM| | INSERTED | HW- | MODULE
PEN | MODULE | TYPE |ID |C|Y|NO | | MODULE |STATE INFO | STATUS
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
15 | Q2335-X DIUT2-E1 1 0| | Q2335-X | 1 -10 - | DEFECT
+--------------------------------+-+------------+------------+------------
| MAC ADDRESS: 00-1A-E8-3D-4B-70 | | TDMLAW : 0(SYSTEM)
+--------------------------------+-+------------+------------+------------

AMO-BCSU -111 BOARD CONFIGURATION, SWITCHING UNIT
DISPLAY COMPLETED;
<DISPLAY-BCSU:TYPE=TBL,LTU=30,SLOT=16;
DISPLAY-BCSU:TYPE=TBL,LTU=30,SLOT=16;
H500: AMO BCSU STARTED

LTG 1 LTU 30 SRCGRP 1 ALARMNO-LTU 0 SOFTGATE1000 240 PORTS USED
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
| | | |S|H|AL-| | | |
| ASSIGNED | MODULE |FCT|E|W|ARM| | INSERTED | HW- | MODULE
PEN | MODULE | TYPE |ID |C|Y|NO | | MODULE |STATE INFO | STATUS
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
16 | Q2335-X DIUT2-E1 1 0| | Q2335-X | 1 -09 - | READY
+--------------------------------+-+------------+------------+------------
| MAC ADDRESS: 00-1A-E8-3D-11-1E | | TDMLAW : 0(SYSTEM)
+--------------------------------+-+------------+------------+------------
 
@Moriendi maybe the MAC address for one PRI was wrong, but i do have 6 PRI .
 
You have tried 6 different PRI and none work?

What is the softgate loadware ? sta-list:":pds:apsp/ltg/lga0/pzksgw50",,100,b;

It would be interesting to make a tcpdump from branch linux and filter on the mac of the defect PRI, see if there is any actual traffic or just syn's.. ie is the PRI responding.
 

. yes i've tried all of them and none work .

. this is the last loadware from the partner portal Spec_LW_V8_R1_19_7 Pilot Usage 2018-08-23 .

. i just did exactly what you said, mirroring on the switch for each module the "new" and the "old" PRI, the defect PRI is acting exactly like the ready PRI, both are exchanging UDP packets with the Branch !!!
 
Can you restart that shelf?

"service socod restart" on the branch.

Also, what do you mean "mirroring on the switch". Access modules should connect directly to the Branch - no customer switch in between.
 


dis-bgdat; check whether you found partno.the inserted PRI module or not?
 
@Moriendi yes it should connect directly but just to see the packets with wireshark i used a switch in between .

@hipath4k yes i already did this .
 
yes of course here is the credential of the teamviewer

ID: 498 724 892
PSW: 3888
 
i just had this answer from our support,

"It may be also that the Access modules you acquired are delivered more or less in the March 2018 time frame??
There is a problem ticket NA15837629 that was found out that there’s a problem with the FW of this module. "

can anybody confirm this information please ?!
 
If you have added it correctly (looks like you did), the loadware is the latest and has been applied to the Branch, you've made a socod restart of the shelf as a final test, and your provider is telling you there is a firmware problem of the module - it sounds to me like you have already confirmed it. For sure there is a bug somewhere.
 
thank you very much guys for everything you did, i can confirm now the modules were faulty .
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top