> Source: [sk185243](https://support.checkpoint.com/results/sk/sk185243)

# sk185243 - Gaia does not display optical transceiver details on Security Gateway ports

| Property | Value |
|----------|-------|
| Solution ID | sk185243 |
| Date Created | 2026-08-06 |
| Last Modified | 2026-08-12 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |
| Platform | 6000 |

## Symptoms

- * On some Security Gateway ports, Gaia does not display optical transceiver information.  
  Examples:  
  `show interfaces xcvr`  
  The command reports: `transceiver information not available`  
  The following commands also do not display transceiver details:  
  * `show interfaces xcvr_detail`
  * `show interface eth1-01 xcvr`
  * `show interface eth1-01 xcvr_detail`
* This behavior can occur with supported Check Point transceivers, including:
  * SX-SFP-1G-I-CP
  * CPAC-TR-1SX-C

## Cause

Gaia transceiver information commands rely on the Linux utility: `ethtool -m`

Ports that use the igb network driver do not support EEPROM access through `ethtool -m`. Because the driver cannot provide the optical module data, Gaia cannot display transceiver diagnostic information and reports that the information is unavailable.

This behavior is a driver capability limitation. It does not indicate a link failure, transceiver malfunction, or traffic impact.

## Solution

No configuration change or Hotfix enables transceiver diagnostics on ports that use the igb driver.

Verify that the interface and transceiver operate correctly with the following steps.

#### Step 1 - Confirm link status and traffic operation

Run on the Security Gateway in Clish:  
`show interface eth1-01`  

Expected result:

* Link state is Up
* Speed is 1000M
* Duplex is full

If the link is up and traffic passes, the missing transceiver information is cosmetic only.

#### Step 2 - Confirm the driver limitation

Run on the Security Gateway in Expert mode:  
`ethtool -i eth1-01`

Expected output: `driver: igb`

Run:  
`ethtool -m eth1-01`

Expected output:

* Cannot get module EEPROM Information
* Operation not supported (or no optical data)

If the interface uses the igb driver and ethtool -m cannot retrieve EEPROM information, Gaia cannot display transceiver diagnostics for that port.

#### Step 3 - Verify transceiver compatibility

Run on the Security Gateway in Expert mode.

Generate an HCP report:  
`run hcp -r all`

Expected output: Review the **Transceivers Support** section to verify that the installed transceiver is approved for the appliance.

Additionally:

* Review [sk92755 - Compatibility of transceivers for Check Point appliances](https://support.checkpoint.com/results/sk/sk92755).
* Verify that the exact transceiver model appears in the supported hardware list.

#### Step 4 - When optical diagnostics are required

The 6200 appliance supports NICs up to 10G and does not support `i40e-class` NICs.

Some hardware that uses the ixgbe driver may support transceiver EEPROM access through `ethtool -m`.

**Important**: Any hardware replacement must be validated against official Check Point appliance compatibility requirements and support guidance before implementation.

**Expected Result:**   
The interface remains operational and traffic passes normally.

Gaia continues to show unavailable transceiver diagnostic information on affected igb ports because the driver does not support the required EEPROM diagnostics. No corrective action is necessary when the interface operates normally.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content