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

# sk182096 - "SIC port is not yet open" messages in CME logs with Security Gateway in NSX-T

| Property | Value |
|----------|-------|
| Solution ID | sk182096 |
| Date Created | 2024-03-11 |
| Last Modified | 2026-04-12 |
| Technical Level | Advanced |
| Products | Cloud Firewall |
| Versions | R82.10, R81.20, R82 |
| OS | Gaia |
| Platform | VMWare NSX-T |

## Symptoms

- * CME logs show that the CME fails to connect to the SIC port of a Virtual Machine that was deleted from the NSX-T datacenter, for example:  

  `
  [DATE][TIME] CME_SERVICE INFO SIC port is not yet open between management <Security Management name> and gateway <Security Gateway name>.`

* You can see the deleted Security Gateway in the NSX-T logs below the other Security Gateways:  

  `
  [DATE][TIME] CME_SERVICE INFO The Security Gateways found in <CME controller name>:`  
  `
  [DATE][TIME] CME_SERVICE INFO 1: <normal Security Gateway>`  
  `
  [DATE][TIME] CME_SERVICE INFO 2: <normal Security Gateway>`  
  `
  [DATE][TIME] CME_SERVICE INFO 3: <normal Security Gateway>`  
  `
  [DATE][TIME] CME_SERVICE INFO 4: <normal Security Gateway>`  
  `
  [DATE][TIME] CME_SERVICE INFO 7: <problematic Security Gateway>`

## Cause

The CME continues to try to connect to a deleted Security Gateway because the service deployment configuration is not deleted.

## 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