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

can't connect with hipath 4000 ppp dial

Status
Not open for further replies.

illios

Technical User
Jul 29, 2006
33
TN
i have a hipath 4000 v2 pabx in office , my problem is that
we must have a PC outside the site to administrate the hipath , i have use a modem v24 dial up connection with a rtcp line but can't connect with the equipement , i heard the ring during the connection but nothing else
remarque : i have verifie the too modem , one connected to a v24 to the pabx and the one on my pc , the line is also ok
can any one help me and explaine me the necessary of a like coonection ; i.e ppp dial up connection
 
My question is how are you trying to access the 4K. You need to know the IP address of your 4K to get in and talk to the box. Basically you need to setup a network connection and then browse to the Ip address of the swith do your client preperation and then you should be able to get in. The only issue you may have is if your Java is not compatiable.
 
No, the o/p is talking about a PPP connection directly to the Hipath through the unixware/v24, you are talking about using the physical LAN connection to connect over the customer network.

To set the modem up, you need to add the modem in UBA under device pools (you'll have more chance of success with a supported modem) and add a PPP link, access from EWS, where you configure your chap password and username, and you can then start a dialup PPP session to the Hipath.

You may find it easier to access the company network via some other method and connect to the main ip address of the Hipath over the wired lan.
 
thanks for your response
Moriendi , you have understand my request , please more
explain about how to configue a ppp link from EWS
 
Under UBA you need "PPP Links". In there there is an "Access from EWS" tab. Just fill in the config under that tab, all it wants to know is what modem to use (which you have already configured in "device pools") and a chap/secret, which is just the PPP username and password you'd put in dialup networking in your PC, and set the PC for DHCP.

As long as you have a supported modem there shouldn't be a problem.
 
thanks
after many investiguation it seems that the v24 backplane the hipath is HS , also the number one v24 under which we collect the CDR datta is also seems HS , i don't know how the two v24 crachs in the same time , but my problem now is how to recuperate the CDR datta from the hipath
the version 2 as i know don't support the ip collect of CDR
please help
 
I don't really understand what you just said, but it seems to be something out about V24 ports and call logging.

IP collection of CDR data is a function of the architecture, more than the software build. CPCI archicture supports IP collection - in fact that's the only way - and the older Atlantic (H330E/H350E) architecture supports CDR collection by V24.

From what you've said, it sounds like you must have Atlantic hardware and an existing V24 connection for CDR data. So you should have lines 8 & 9 reserved for RMX (call logging from line 9) and lines 10 & 11 reserved for Unix, line 11 is for direct V24 access to the Unix, line 10 for the modem.

Those are logical line numbers, they are not marked as such on the backplane. Line 8 is on the ADP processor, 9, 10 and 11 are on the backplane.

If you are call logging from line 10 at the moment, you must reconfigure it to line 9 as lines 10 and 11 should be reserved for Unixware.
 
thanks Moriendi
our CDR collection is on logic line 9 witch is v24 backplane (we have a 3 v24 connecteur backplane) this line is activated but we have not a CDR trame it seems to be HS ( it works normally until last week)
normally dev1 is reserved for CDR , dev2 for modem connection , dev3 for printer ; thats what me said a technical siemens agent, in fact to replace my CDR connection in other v24 we must reconfigured it
i do know if my hipath support a IP collect of CDR , and if yes how to do this
my problem now is not to connect to hipath under ppp but how to repair CDR collection
 
the alarm sent in my case is F6166
even if i replace the device to hd save (CDRC1) i have the same alarm
 
You're getting that alarm as the buffer is full, for some reason it can't output the records.

If the call logger is on line 9 try act-lssm:A1,9; to put the port (back) in service.

If the records don't start coming out at the logger replace it with a normal PC connected directly to line 9 (use procomm/hyperterminal (check baud/bits)) to prove the Hicom is functioning correctly.
 
i connect a pc directly in line 9 with a null modem cable
result : nothing trame in hyperterminal
the line 9 is already activated ( act-lssm )
bauds and bits are correct
if i connect a pc on dev 1 (v24) front side with a db25/db9
cable ,i can connect with comwin , On the other hand if i connect to line 9 with comwin with the same cable (com connection ) ,the connection don't pass
 
Are you sure the baud rate is correct ?

If you can't get the #######'s then CDR output won't work either.

AMO ATCSM will tell you the baud rate.

Have you restarted the ADP processor? It might help.
 
for line 9 i use a strait cable
the rate is also ok
today i will restart the ADP and i will see
i inform you
thanks
 
i have restart the adp but the probleme still the same
Remark : when i deactivate and activate the line 9 i have
####### but not a really cdr trame , just a line and nothing after (hyperterminal under null modem )
if the v24 interface is controlled by dpc5 (ADP) i'm thinking to change him if it is really a hardware probleme but i want to bee sure that it is
 
If you have the hashes it sounds OK, you should try and run AMO's on line 9, if it's OK, there's nothing wrong with the port. You don't need a null modem for a line 9, it's a straight cable, so I have no idea what is actually happening.

If you saw the hashes you should see the call logging. Are you sure it's activated ?

Post the output from

dis-aps:,psgl,y*;
reg-sels;
reg-gezu;
reg-gefe;
reg-atcsm;
reg-tcsm;
dis-selg;
dis-bcsm:A1,dpp;
dis-cdsm;
dis-cdsu;
 
Here are output

DISPLAY-APS:;
DISPLAY-APS:;
H500: AMO APS STARTED
ADINIT STARTED
PROGRAM SYSTEM : D0-EL0DC
VERSION NUMBER : 30
CORRECTION VERSION NUMBER : 022
PART NUMBER : P30252B4300D00112
PROGRAM SYSTEM WITH CODE SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

PROGRAM SYSTEM : A0-EL0AC
VERSION NUMBER : 30
CORRECTION VERSION NUMBER : 078
PART NUMBER : P30252B4300A00112
PROGRAM SYSTEM WITH CODE SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

PROGRAM SYSTEM : S0-EL0SC
VERSION NUMBER : 30
CORRECTION VERSION NUMBER : 025
PART NUMBER : P30252B4300S00112
PROGRAM SYSTEM WITH CODE SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

PROGRAM SYSTEM : S0-TLXSX
VERSION NUMBER : 20
CORRECTION VERSION NUMBER : 036
PART NUMBER : P30252B4350S00112
PROGRAM SYSTEM WITH TEXT SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

PROGRAM SYSTEM : L0-EL0LC
VERSION NUMBER : 30
CORRECTION VERSION NUMBER : 033
PART NUMBER : P30252B4300W00112
PROGRAM SYSTEM WITH CODE SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

PROGRAM SYSTEM : L0-TLKLK
VERSION NUMBER : 10
CORRECTION VERSION NUMBER : 022
PART NUMBER : P30252B4300W40112
PROGRAM SYSTEM WITH TEXT SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

PROGRAM SYSTEM : Y0-EL0YC
VERSION NUMBER : 10
CORRECTION VERSION NUMBER : 001
PART NUMBER : P30252N4312B00004
PROGRAM SYSTEM WITH CODE SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

PROGRAM SYSTEM : B0-EL0BC
VERSION NUMBER : 30
CORRECTION VERSION NUMBER : 085
PART NUMBER : P30252B4300B00112
PROGRAM SYSTEM WITH CODE SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

PROGRAM SYSTEM : Y7-PLTYT
VERSION NUMBER : 60
CORRECTION VERSION NUMBER : 001
PART NUMBER : P30252B4300U00702
PROGRAM SYSTEM WITH TEXT SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

ADINIT COMPLETED
STATUS = H'0000
AMO-APS -111 SOFTWARE LOAD UPGRADE
DISPLAY COMPLETED;

REGENERATE-GEZU:;
REGENERATE-GEZU:;
H500: AMO GEZU STARTED
ADD-GEZU:TTY,DEV1,TTY,TERM1;
ADD-GEZU:TTY,DEV2,TTY,TERM2;
ADD-GEZU:TTY,DEV3,TTY,TERM3;
ADD-GEZU:TTY,DEV4,TTY,TERM4;
ADD-GEZU:DP,DP,NOSERV,NODEV," "," "," ";

REGENERATE-GEFE;
REGENERATE-GEFE;
H500: AMO GEFE STARTED
CHANGE-GEFE:KNMATINT,NOPTY;
CHANGE-GEFE:KNMATOUT,NOPTY;
CHANGE-GEFE:KNMATINC,NOPTY;
CHANGE-GEFE:pREINT,NOPTY;
CHANGE-GEFE:pREOUT,NOPTY;
CHANGE-GEFE:pREINC,NOPTY;
CHANGE-GEFE:ATTNDOUT,N;
CHANGE-GEFE:ATTNDINC,N;
CHANGE-GEFE:CCALLDIR,N;
CHANGE-GEFE:RNGDT,N;
CHANGE-GEFE:QUEUEDUR,N;
CHANGE-GEFE:SRSUBS,Y;
CHANGE-GEFE:DN,N;
CHANGE-GEFE:SAMEPP,Y;
CHANGE-GEFE:REALUNIT,N;
CHANGE-GEFE:INCOLD,N;
CHANGE-GEFE:CONFAOCS,THRCONN,BASCOMM&CSETUP;
CHANGE-GEFE:CONFAOCS,NTHRCONN,NBASCOMM&NCALLATT;
CHANGE-GEFE:CAR,1,PULSE,N;
CHANGE-GEFE:CAR,2,MIX,N;
CHANGE-GEFE:CAR,3,MIX,N;
CHANGE-GEFE:CAR,4,MIX,N;
CHANGE-GEFE:CAR,5,MIX,N;
CHANGE-GEFE:CAR,6,MIX,N;
CHANGE-GEFE:CAR,7,MIX,N;
CHANGE-GEFE:CAR,8,MIX,N;
CHANGE-GEFE:CAR,9,MIX,N;
CHANGE-GEFE:METHOD,1,0,0,0,0;
CHANGE-GEFE:METHOD,2,0,0,0,0;
CHANGE-GEFE:METHOD,3,0,0,0,0;
CHANGE-GEFE:METHOD,4,0,0,0,0;
CHANGE-GEFE:METHOD,5,0,0,0,0;
CHANGE-GEFE:METHOD,6,0,0,0,0;
CHANGE-GEFE:METHOD,7,0,0,0,0;
CHANGE-GEFE:METHOD,8,0,0,0,0;
CHANGE-GEFE:METHOD,9,0,0,0,0;

REGENERATE-ATCSM:UNIT=A1;
REGENERATE-ATCSM:UNIT=A1;
H500: AMO ATCSM STARTED
ADD-ATCSM:A1,CFIG,TYPE,PT88,0D0A,0C,
0,0,0,0,
0,0,62,80;
ADD-ATCSM:A1,CFIG,TYPE,QUOSC,0D0A,0,
0,0,0,1B4730,
1B4731,03,22,80;
ADD-ATCSM:A1,CFIG,TYPE,QUOPT,0D0A,0C,
0,1B60,1B61,0,
0,0,62,80;
ADD-ATCSM:A1,CFIG,TYPE,QUSCAPT,0D0A,0,
0,0,0,0,
0,03,22,80;
ADD-ATCSM:A1,CFIG,TYPE,PCOSC,0D0A,0,
0,0,0,1B5B306D,
1B5B386D,03,17,80;
ADD-ATCSM:A1,CFIG,TYPE,PCOPT,0D0A,0C,
0,1B60,1B61,0,
0,0,62,80;
ADD-ATCSM:A1,CFIG,TYPE,PCSCAPT,0D0A,0C,
0,1B40,1B41,1B5B306D,
1B5B386D,03,62,80;
ADD-ATCSM:A1,CFIG,TYPE,RSV1,0D0A,0C,
1B5B2470,0,0,0,
0,0,26,80;
ADD-ATCSM:A1,CFIG,TYPE,RSV2,0D0A,0,
0,0,0,1B4730,
1B4731,03,22,80;
ADD-ATCSM:A1,CFIG,TYPE,RSV3,0D0A,0,
0,0,0,1B5B306D,
1B5B386D,03,17,80;
ADD-ATCSM:A1,CFIG,DEV,2,ECHO&ARCVCO,80,F8,1,04,00,
00&00,00,0,02,0D,0D,0D&0A,65535,65535,65535,600,120,300,
600,120,C2C1C4C3,C2C1C4C3;
ADD-ATCSM:A1,CFIG,DEV,3,ECHO&ARCVCO,80,F8,1,04,00,
00&00,00,0,02,0D,0D,0D&0A,65535,65535,65535,600,120,300,
600,120,C2C1C4C3,C2C1C4C3;
ADD-ATCSM:A1,CFIG,DEV,4,ECHO&ARCVCO,80,F8,1,04,00,
00&00,00,0,02,0D,0D,0D&0A,65535,65535,65535,600,120,300,
600,120,C2C1C4C3,C2C1C4C3;
ADD-ATCSM:A1,ADD,TYPE,CON2,Y,PCOSC,2;
ADD-ATCSM:A1,ADD,TYPE,CON3,Y,PCOSC,3;
ADD-ATCSM:A1,ADD,TYPE,CON4,Y,PCOSC,4;
ADD-ATCSM:A1,ADD,LN,2,9,N;
ADD-ATCSM:A1,ADD,LN,3,10,N;

REGENERATE-TCSM:UNIT=A1;
REGENERATE-TCSM:UNIT=A1;
H500: AMO TCSM STARTED

AMO-TCSM -111 TERMINAL CONFIGURATION OF SERVER


DISPLAY-SELG:SELGNO=1;
DISPLAY-SELG:SELGNO=1;
H500: AMO SELG STARTED

+==============================================================================+
| SELECTION GROUP : 1 |
+------------------------------------------------------------------------------+
| |
| OPERATING STATE : ON |
| |
| RESOP : N |
| BASDEV : DEV2 BLBAS : 1 |
| RESDEV : NODEV BLRES : 0 |
| |
+==============================================================================+
| |
| SELECTION GROUP : 1 SELECTION TABLE : 1 |
| |
| FORMBAS : FORM03 TARIFF : NOCALC |
| FORMRES : NOFORM DESTCNT : A22 |
| |
| LEVEL0 : 0&&999 |
| LEVEL1 : 0&&254 |
| LEVEL2 : 0&&30 |
| CDRCD : 0&&15 |
| |
| ATNDGR : 0&&15 |
| SERVICE : VOICE |
| |
| CDRULT : 0 CONNTL : 00 : 00 : 00 |
| COPIN : 0&&8 CARRIER : 0&&9 |
| |
| SELECTION FEATURES 1 : |
| |
| CTYPE : ALL PAYPARTY : ALL NSTAT : N |
| CDRAC : N SFSETUP : N CDBAD : Y |
| CDRC : N CDRSTA : N THRGCON : N |
| SECTION : N TIE-LINE : N EXPENS : N |
| CONNTYP : OUTG |
| RECTYP : ALL |
| |
| SELECTION FEATURES 2 : |
| |
| CDCHU : N CDRULTE : N CONNT : N |
| PCODE : N PPCF : N STATAB1 : N |
| STATAB2 : N DNOTBL1 : N DNOTBL2 : N |
| |
+==============================================================================+


DISPLAY-BCSM:UNIT=A1,CONF=DPP;
DISPLAY-BCSM:UNIT=A1,CONF=DPP;
H500: AMO BCSM STARTED
DATA-PROCESSOR-PORTS

+------+------+
| LINE | RMX |
+------+------+
| 9 | Y |
+------+------+
| 10 | Y |
+------+------+
| 11 | N |
+------+------+

DISPLAY-SDSM:UNIT=A1;
DISPLAY-SDSM:UNIT=A1;
H500: AMO SDSM STARTED

A1 - CENT
---------
MOUNTING LOCATION MODULE NAME NOM. BD(#-ACT) STATUS
P201.UCD .CCD1.046 DPC5 128MB #Q2270-X100

A1 - LN
---------
MOUNTING LOCATION MODULE NAME NOM. BD(#-ACT) STATUS
P204.UPR .LTU1.067 PSIO Q2139-X AMO/PRES/CREA
LTG: 1 LTU: 3 PBC: 001 DC STATUS:
LOCAL MEMORY IN SWU:
CC-A: 127 MB
CC-B: 127 MB

DISPLAY-CDSU:;
DISPLAY-CDSU:;
H500: AMO CDSU STARTED

CABINET ADDRESS: P101
CABINET TYPE : UACD
CODE NUMBER : G5405-X

SHELF : 1
FRAME TYPE : PSD
CODE NUMBER : B5427-X

CABINET ADDRESS: P201
CABINET TYPE : UCD
CODE NUMBER : G5403-X

SHELF : 1
FRAME TYPE : CCDAXD1 (A)
CODE NUMBER : B5384-X
| PEN | CURR. MOD. HW ABB |STATUS|FIRMWARE|
|-----+---------------------+------+--------|
| 58 | Q2270-X100 DPC5 | 5 | D971-H |
| 70 | Q2113-X100 QDCL | 2 | D407-C |
| 79 | Q2234-X100 SICOE | 2 | D802-B |
| 79 | Q2234-X100 SICOE | 2 | D802-B |
| 79 | .......... ........ | | |
| 85 | Q2224-X1 MTSCG | 1 | - |
| 85 | Q2224-X1 MTSCG | 1 | D640-J |
| 91 | Q2270-X100 DPC5 | 5 | D971-H |
| 103 | Q2113-X100 QDCL | 2 | D407-C |
| 112 | Q2234-X100 SICOE | 2 | D802-B |
| 112 | Q2234-X100 SICOE | 2 | D802-B |
| 112 | .......... ........ | | |
| 118 | Q2224-X1 MTSCG | 1 | - |
| 118 | Q2224-X1 MTSCG | 1 | D640-J |

CABINET ADDRESS: P202
CABINET TYPE : UPR
CODE NUMBER : G5404-X

SHELF : 1
FRAME TYPE : LTUW1 1
CODE NUMBER : B5388-X

CABINET ADDRESS: P203
CABINET TYPE : UPR
CODE NUMBER : G5404-X

SHELF : 1
FRAME TYPE : LTUW1 2
CODE NUMBER : B5388-X

CABINET ADDRESS: P204
CABINET TYPE : UPR
CODE NUMBER : G5404-X

SHELF : 1
FRAME TYPE : LTUW1 3
CODE NUMBER : B5388-X

CABINET ADDRESS: P301
CABINET TYPE : UPR
CODE NUMBER : G5404-X

SHELF : 1
FRAME TYPE : LTUW1 4
CODE NUMBER : B5388-X

CABINET ADDRESS: P302
CABINET TYPE : UPR
CODE NUMBER : G5404-X

SHELF : 1
FRAME TYPE : LTUW1 5
CODE NUMBER : B5388-X



 
OK forget the LCSM, I wanted to see the baud rate but it's not important.

Your Hipath is UV1.0 not UV2.0 but that doesn't affect the configuration.

The configuration for Line 9 is all standard, no reason why it shouldn't be working. You need a straight cable to connect to it, if you are using a null modem convertor, then you don't have a straight cable to start with, so that's something you could look at.

I don't know why you have all the GEZU devices assigned if you only want one output. I would change the SELG BASDEV to DEV1, change GEZU DEV1 to output on TERM2, and change the rest of the GEZU devices to NOSERV,NODEV;

Your BCSM DPP config shows line 10 is reserved for RMX. With Unixware running lines 10 and 11 are for Unix, not RMX. So you need to delete that ATCSM config for 3,10 and add-bcsm:dpp so that line 10 is not reserved for RMX. If you want PPP access to the switch, that's what you are going to have to do.

It's not likely to be a DPC5 problem but if you wanted to test it, you could swap the DPC5 processor from the standby half, don't forget to change the jumper for SCSI (J6) as the ADP will need the SCSI activating.

 
thanks Moriendi
about the LCSM it's Ok the rate 4800
a have done what you say ; change the dev2 to dev1 and dev1
to term2 , but nothing change
can you tell me if i down off the system to change the ADP
is there any risk that the hipath can't reboot ?
and what precaution must i have ?
thanks for your help
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top