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

# sk183755 - SNMP Port Index Inconsistency Across Security Group Members in a Maestro Security Group

| Property | Value |
|----------|-------|
| Solution ID | sk183755 |
| Date Created | 2025-08-21 |
| Last Modified | 2025-08-25 |
| Technical Level | Advanced |
| Products | Scalable Platforms |
| Versions | R81.20, R81.10 (EOS) |
| OS | Gaia |
| Platform | 7000 |

## Symptoms

- * WHen you run the `snmpwalk` command on Security Group Members (SGMs) in a Maestro Security Group, the output shows a mismatch among the `IF-MIB:Descr` entries.

* For the same ports (bond1, bond5, bond5.2086), SNMP indices differ between SGM1 (170, 172, 173) and SGM2/SGM3 (169, 170, 171).

* This discrepancy leads to inconsistent monitoring results, making it difficult to reliably track port status using SNMP-based monitoring tools.

## Cause

The SNMP daemon retrieves port index information directly from the kernel. The kernel assigns port indices dynamically during the boot process of each SGM, which can result in different index values for the same ports across SGMs.

**Example SNMP query output:**   

`SGM1:`  
`bond1 index: 170`  
`bond5 index: 172`  
`bond5.2086 index: 173`  

`SGM2/SGM3:`  
`bond1 index: 169`  
`bond5 index: 170`  
`bond5.2086 index: 171`

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# 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