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

# sk97998 - Virtual System still shows an interface and a route that belonged to an interface, which lead to Virtual Router even after that interface and Virtual Router were deleted

| Property | Value |
|----------|-------|
| Solution ID | sk97998 |
| Date Created | 2014-01-01 |
| Last Modified | 2016-11-28 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- Virtual System still shows an interface and a route that belonged to an interface, which lead to Virtual Router even after that interface and Virtual Router were deleted.

*Example*:

1. Create a Virtual Router
2. Stop one of the members ('`cpstop`'), or disconnect one of the members from the Management Server.
3. Add an interface on Virtual System that leads to Virtual Router
4. Start the stopped member ('`cpstart`'), or reconnect it to the Management Server.
5. Install policy
6. Delete the interface on Virtual System that leads to Virtual Router
7. Delete the Virtual Router
8. Install policy
9. Switch to the context of the Virtual System.
10. Output of '`ifconfig -a`' command in Expert mode still shows the '`wrp`' interface that leads to Virtual Router
11. Output of '`route -n`' command in Expert mode still shows a route that belongs to the '`wrp`' interface (which leads to Virtual Router)

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