I am running 7.4R3.4 everywhere.
I have 12-FE pics of different ages, neither of them had any
problems so
far (P- and PE- ones).
PIC 3 REV 03 750-004177 BB8xxx 12x
FE, 100
BASE-TX
PIC 1 REV 02 750-004176 HG9xxx 12x
FE, 100
BASE-TX
ASIC type: DFE FPGA (12)
Interface type: fe
Firmware Version: 7
PIC model: 12-port FE
ASIC type: DFE FPGA (12)
Interface type: fe
Firmware Version: 7
PIC model: 12-port FE
(all of them have atleast firmware 7)
These are all connected to simple FPC's (non -E).
Tho M320 and M7i utilize different ASICs, i doubt that there
would be a
problem using a somewhat up-to-date JunOS to bundle FE
links. We do it
since like 6.2.
If you need further info please let me know. (probably take
this to
private then as to reduce list noise)
Jonas
On Sun, 2006-11-26 at 19:19, Jee Kay wrote:
> On 26/11/06, Jonas Frey <jf probe-networks.de>
wrote:
> >
> > I am running 802.3ad on 12-FE pics without
problems. I am using them in
> > several M-series without any problems so far.
> > (As well as usual GE pics on different m-series).
>
> Interesting.. if you don't mind my asking, which PICs
are you using?
> We ran into this problem (and had it verified by
Juniper) with the
> following hardware:
>
> # Item Version Part number Serial number
Description
> # Chassis xxxxx
M7i
> # Midplane REV 04 710-00xxxx CJ4xxx
M7i Midplane
> # Routing Engine REV 09 740-00xxxx 1000572xxx
RE-5.0
> # CFEB REV 03 750-01xxxx CH6xxx
Internet Processor II
> # FPC 0
E-FPC
> # PIC 0 REV 08 750-00xxxx CG7xxx
12x FE, 100 BASE-TX
>
> Maybe its a 320 v. 7 issue or a JunOS issue.. we were
running
> 7.1Rsomething at the time.
>
> Ras
_______________________________________________
juniper-nsp mailing list juniper-nsp puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
|