auto nego question

auto nego question

Post by w » Wed, 02 Jul 2003 18:09:01



Hi,

I need a expert answer for this issue:

after power up, does the link status bit in mii register 1 (status
register) indicates that the auto-nego completed? I know that there is
a special bit in the very same reg that states exactly this (a/n
complete), but I want to know if I can count on the link status bit
for this info as well, and as soon as it is up - read the link partner
reg to decide how to work.

thank you!
wd.

 
 
 

auto nego question

Post by Fritz » Thu, 03 Jul 2003 03:40:59



> after power up, does the link status bit in mii register 1 (status
> register) indicates that the auto-nego completed?

What PHY are you using?

RFM
--
To reply, translate domain from l33+ 2p33|< to alpha.
                4=a  0=o  3=e  +=t

 
 
 

auto nego question

Post by w » Thu, 03 Jul 2003 18:35:46




> > after power up, does the link status bit in mii register 1 (status
> > register) indicates that the auto-nego completed?

> What PHY are you using?

I'm writing the code that analyze the auto-negotiation results.
whoever uses the platform my code runs above, is only restricted to
connect the PHY with MII I/F but not to particular PHY.
Quote:> RFM

 
 
 

auto nego question

Post by Fritz » Fri, 04 Jul 2003 00:50:37



> I'm writing the code that analyze the auto-negotiation results.
> whoever uses the platform my code runs above, is only restricted to
> connect the PHY with MII I/F but not to particular PHY.

Sorry, I don't know what I was thinking :-/  Brain fart I guess.

Look at the autoneg complete bit.  I've seen link status bounce on some
chips with autoneg remaining at zero.

RFM
--
To reply, translate domain from l33+ 2p33|< to alpha.
                4=a  0=o  3=e  +=t

 
 
 

1. LCP nego failures with Ascend MAX

Hi,

I'm having troubles establishing a ppp link between a 26xx and a Max Ascend
over ISDN.

The failures occur while the LCP negotiation is processing.

Both ends request pap authentication and both ends reject the pap requests
of  each other. It seems the 26xx NACK's the pap authentication requests of
the Max interpreting it as a CHAP request

Here's a summary of the the debug on cisco side:

BRI0/0:1 LCP: I   CONFREQ [REQsent] id 2 len 12
                              MRU 1524 ( 0x010405F4)
                                AuthProto PAP (0x0304C023)

BRI0/0:1 LCP: O CONFNACK [REQsent] id 2 len 9
                             AuthProto CHAP (0x0305C22305)

BRI0/0:1 LCP: O CONFREQ [REQsent] id 200 len 14
                                AuthProto PAP (0x0304C023)
                                MagicNumber 0x43E35B69 (0x050643E35B69)

BRI0/0:1 LCP: I  CONFREJ [REQsent] id 200 len 8
                                AuthProto PAP ( 0x0304C023)

If someone has an idea about that , that woud be nice

THX

2. new files on ftp.lip6.fr

3. set port nego m/p disble

4. Recursive make harmful?

5. LAPM/SREJ Protocal Nego

6. Portfolio Management

7. Thanks: PLEASE!!! Help me

8. auto or not to auto

9. auto-summary / no auto-summ explanation please

10. Looking for modems that auto-auto-dial

11. How to auto-unload BEMGR (Backup Exec) for auto-DOWNing

12. Difference between Auto-sense and Auto-negotiate in Ethernet