topic Virtual Switch appears disconnected in Smart Console, traffic works. in Hyperscale Firewall (Maestro)

Virtual Switch appears disconnected in Smart Console, traffic works.

Alex- — Fri, 12 Sep 2025 11:12:58 GMT

SMS R82 Take 34

Maestro 19200 R81.20 Take 105, VSX SG

Smart Console R82.1057

We have created a VSW successfully, it appears in the VS list, ping works, L2 is fine, no issues reported by the HW.

However, the VSW appears in red in the SC, with the message that connection to the VSW is lost.

Actions taken so far:

- Install database

- cpstop, cpstart

- Reboot

VSW still shows red. Any indications?

Re: Virtual Switch appears disconnected in Smart Console, traffic works.

Chris_Atkinson — Fri, 12 Sep 2025 14:31:28 GMT

Anything of interest shown if you do:

cpwd_admin list -ctx <vsid>

Re: Virtual Switch appears disconnected in Smart Console, traffic works.

Bob_Zimmerman — Fri, 12 Sep 2025 20:24:34 GMT

As far as I'm aware, this is normal. All of my switch contexts have had that red circle with the X ever since moving my managements to R80. The detailed message is always "Connection with <switch name> is lost". This seems expected to me, because the switch has no addresses, so there's nothing to connect to.

The traffic-light status in SmartConsole has never worked properly for me. I just ignore it.

Re: Virtual Switch appears disconnected in Smart Console, traffic works.

Chris_Atkinson — Sat, 13 Sep 2025 03:45:17 GMT

That's certainly the case for DAIP objects and I thought I recalled an SK or limitation mention as much for VSW on VSX but it only talks to licensing errors.

Refer: sk182031, sk112067, sk166495, sk163076

Re: Virtual Switch appears disconnected in Smart Console, traffic works.

emmap — Sun, 14 Sep 2025 01:09:46 GMT

This is an old issue, I thought it had been resolved but I guess it returned somehow. If it's bothering you it probably needs a TAC case but as you say it seems to just be cosmetic.

Re: Virtual Switch appears disconnected in Smart Console, traffic works.

Alex- — Sun, 14 Sep 2025 14:45:08 GMT

@Bob_Zimmerman Interesting, on our side it's the first time I see this structurally on VSW, this was typically a one-off resolved by restarting the SC.

@emmap I guess that's what I'll do.