Avidia Pairgain 8000 problem

Hello,

I am just testing an Avidia Pairgain 8000 DSLAM together with a Redback SMS 500 Router and an Actiontec Home-dsl Modem. Now i am stuck and hoping someone from this Newsgroups who knows that product can help me.

My testsetup is the following:

PC-Windows-XP Actiontec Home-DSL Modem (txvpi 0 rxvpi 0 txvci

35 rxvci 35) (Port 5.2 0 35) Avidia 8000 (port 12.1 100 100) (atm 5/0 100 100) SMS500

Modem syncs with dslam, no problem. OC3 comes up avidia 8000: slot 5: 12 Port ADSL; Slot 12: OC3 - Configured Cross Connect PVC 5.2 0 35 12.1 100 100 - (atm - cell - pvc : new 5.2 0 35 12.1 100 100 -admin up) SMS 500: - configured atm 5/0 pvc 100 100 multi

Problem: - SMS500 receives packets from PC (PPPOE PADIs or IP-ARP Requests) - SMS 500 reply does not reach PC! Reply is send out on atm 5/0 pvc 100 100 - When SMS 500 is replying: - on the 8000 the OC3 counter rises / os3 receive led blinks - The ADSL 5.2 outgoing counter is 0 - when the PC is sending Packets: - the ADSL 5.2 incoming counter rises - The oc3 outgoing counter rises - the sms 500 even fills his arp table with the right information learned from broadcasts originating from the pc and modem.

Question: Why is noting sent out on the adsl 5.2 interface? Does the 8000 need one pvc for receiving and one for transmitting on the ADSL side? And if so, how do i configure that? - tried: atm - cell - pvc : new 12.1 100 100 5.2 0 35 -admin up - Got Error, nothing was added to the pvc table. No wonder, pvc´s allready in use - entered pvc new 5.2 x x 12.1 x x and new 12.1 y y 5.2 y y to define directions - when showing the pvc table both entries started with 5.2 and

12.1 was the destination, so it seemed to make no difference. And besides

that,how would the redback know when to use which pvc?

I will appreciate any help or suggestion, if some more or more detailed data is needed just ask, i will provide it as soon as possible!

Thanks in advance,

Uwe Dahlmann snipped-for-privacy@uni-mainz.de Hello,

I am just testing an Avidia Pairgain 8000 DSLAM together with a Redback SMS 500 and an Actiontec Homedsl Modem. Now i am stuck and hoping someone from this Newsgroups knows that product and can help me.

My testsetup is the following:

PC-Windows-XP Actiontec Home-DSL Modem (txvpi 0 rxvpi 0 txvci

35 rxvci 35) (Port 5.2 0 35) Avidia 8000 (port 12.1 100 100) (atm 5/0 100 100) SMS500

Modem syncs with dslam, no problem. OC3 comes up avidia 8000: slot 5: 12 Port ADSL; Slot 12: OC3 - Configured Cross Connect PVC 5.2 0 35 12.1 100 100 - (atm - cell - pvc : new 5.2 0 35 12.1 100 100 -admin up) SMS 500: - configured atm 5/0 pvc 100 100 multi

Problem: - SMS500 receives packets from PC (PPPOE PADIs or IP-ARP Requests) - SMS 500 reply does not reach PC! Reply is send out on atm 5/0 pvc 100 100 - When SMS 500 is replying: - on the 8000 the OC3 counter rises / os3 receive led blinks - The ADSL 5.2 outgoing counter is 0 - when the PC is sending Packets: - the ADSL 5.2 incoming counter rises - The oc3 outgoing counter rises - the sms 500 even fills his arp table with the right information learned from broadcasts originating from the pc and modem.

Question: Why is noting sent out on the adsl 5.2 interface? Does the 8000 need one pvc for receiving and one for transmitting on the ADSL side? And if so, how do i configure that? - tried: atm - cell - pvc : new 12.1 100 100 5.2 0 35 -admin up - Got Error, nothing was added to the pvc table. No wonder, pvc´s allready in use - entered pvc new 5.2 x x 12.1 x x and new 12.1 y y 5.2 y y to define directions - when showing the pvc table both entries started with 5.2 and

12.1 was the destination, so it seemed to make no difference. And besides

that,how would the redback know when to use which pvc?

I will appreciate any help or suggestion, if some more or more detailed data is needed just ask, i will provide it as soon as possible!

Thanks in advance,

Uwe Dahlmann snipped-for-privacy@uni-mainz.de Johannes Gutenberg Universitaet Mainz

Reply to
Uwe Dahlmann
Loading thread data ...

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.