Re: Local Fault/Remote Fault
Boaz,
Your example showed no 64B/66B code. However, the PHY XGXS would
initiate POS/Idle in the direction downstream of the detected fault for
the case you illustrated.
Happy Holidays,
Rich
--
Boaz Shahar wrote:
>
> I see. That is, the PHY-XGXS Layer has to initiate 64/66 code words with
> alternating POS and Idles?
>
> > -----Original Message-----
> > From: Rich Taborek [mailto:rtaborek@xxxxxxxxxxxxx]
> > Sent: Sunday, December 31, 2000 9:21 PM
> > To: Boaz Shahar
> > Subject: Re: Local Fault/Remote Fault
> >
> >
> > Boaz,
> >
> > No. 10GE Transmit and Receive paths operate independently.
> >
> > For the case you describe, it is not appropriate to report the XAUI
> > Transmit path Deskew fault condition via the receive path. It is
> > appropriate to report that condition via the continuation of the
> > transmit path. Any device downstream of the fault condition, including
> > the PHY XGXS, may generate the Fault Message message.
> >
> > Happy Holidays,
> > Rich
> >
> > --
> >
> > Boaz Shahar wrote:
> > >
> > > Some comments/questions:
> > >
> > > >
> > > > 1. Any device, in either its transmit or receive paths, could
> > > > detect a fault condition. The fault may be that the data
> > > > being received is invalid or that some internal problem
> > > > is causing the problem. Some/many faults may go
> > > > undetected. If a device detects a fault condition (i.e.,
> > > > a locally detected fault) it should set its link status
> > > > to zero and not forward what is received, but should,
> > > > at its output, either:
> > > >
> > > > a. generate a local fault pulse ordered set if it is
> > > > capable of doing so,
> > >
> > > If, for instance, in the system: RS - DTE XGXS - (XAUI) -
> > PHY XGXS - PCS -
> > > PMA - PMD a local fault is detected by the local PCS by
> > recognizing that
> > > the XAUI lanes (In the Transmit path) are not de skewed.
> > Then the intention
> > > is that a LF indication will be signaled to the local RS
> > via the RX path?
> > > (That is, the PCS will have a connection from the Transmit
> > path to the
> > > receive path?)
-------------------------------------------------------
Richard Taborek Sr. Phone: 408-845-6102
Chief Technology Officer Cell: 408-832-3957
nSerial Corporation Fax: 408-845-6114
2500-5 Augustine Dr. mailto:rtaborek@xxxxxxxxxxx
Santa Clara, CA 95054 http://www.nSerial.com