808bits

LX-4000T and LX-8000S Series Console Servers

FIPS 140-2 certificate #837 · MRV Communications · data as of 2026-08-28
Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number837
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorMRV Communications · website
Hardware versions600-R3248 RevB, 600-R3249 RevB, 600-R3250 RevB, 600-R3251 RevB, 600-R3252 RevC, 600-R3253 RevC, 600-R3254 RevB, 600-R3255 RevB, 600-R3256 RevB, 600-R3257 RevB, 600-R3258 RevC, 600-R3259 RevC, and 600-R3265 RevA through 600-R3288 RevA (inclusive)
Firmware versionslinuxito Version: 4.1.4 and ppciboot Version: 4.1.4

Module description

The LX-4000T and LX-8000S Series Console Servers are a key component of MRV╞s Out-of-Band Network solution. Out-of-Band Networks provide secure remote service port access and remote power control to devices in an organization╞s networks and infrastructures. This nearly eliminates the need for physical presence at a device to correct problems or manage its everyday operation. MRV╞s Out-of-Band Network solution includes console servers, terminal servers, device servers, remote power control and management system, making the LX Series an ideal choice for secure remote access.

Approved algorithms

AlgorithmCAVP certificate
AES348
DSA156
HMAC151
RNG166
RSA226
SHS423
Triple-DES408

Other algorithms

DES; MD5; Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 178 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2007-09-11InitialSAIC-VA

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2007-09-11

Source documents