nanog mailing list archives
Re: Juniper hardware recommendation
From: Saku Ytti <saku () ytti fi>
Date: Mon, 17 May 2021 10:34:19 +0300
On Mon, 17 May 2021 at 00:22, Sander Steffann <sander () steffann nl> wrote:
How do you normalise? Use L2 or L3 octets stats, and use the number of packets to calculate the L2 and/or L1 overhead the stats are missing? Or do you have a better way?
That's the way one of my employers did it, and I can't think of a better way. bytes += PPS*overhead Overhead is likely 20bytes (preamble, SFD, ifg). But it could also be 24B (FCS/CRC might be missing in what otherwise is claimed to be L2). You may need a lab to confirm what exactly is being counted. This adjustment could be in DB or it could be render-time, both have pro and con. -- ++ytti
Current thread:
- RE: Juniper hardware recommendation, (continued)
- RE: Juniper hardware recommendation Michael Fiumano (May 14)
- RE: Juniper hardware recommendation Adam Thompson (May 14)
- Re: Juniper hardware recommendation Jason Healy (May 16)
- Re: Juniper hardware recommendation Colton Conor (May 16)
- Re: Juniper hardware recommendation Mark Tinka (May 16)
- Re: Juniper hardware recommendation Jon Lewis (May 16)
- RE: Juniper hardware recommendation Adam Thompson (May 14)
- RE: Juniper hardware recommendation Michael Fiumano (May 14)
- Re: Juniper hardware recommendation Saku Ytti (May 15)
- Re: Juniper hardware recommendation Mark Tinka (May 15)
- Re: Juniper hardware recommendation Saku Ytti (May 15)
- Re: Juniper hardware recommendation Sander Steffann (May 16)
- Re: Juniper hardware recommendation Saku Ytti (May 17)
- RE: Juniper hardware recommendation Jean St-Laurent via NANOG (May 17)