topic BPE / VPEX Physical Location in ExtremeCloud IQ- Site Engine Management Center

BPE / VPEX Physical Location

Sanktis — Thu, 02 Oct 2025 06:59:09 GMT

Hello Community,

We need to document in ExtremeCloud IQ (XIQ) where our Virtual Port Extenders (VPEX) are physically located.

For example, we have ten VPEX units running on a single Access Switch. These VPEX units are physically located in different offices.

We would like to be able to set a specific location for a VPEX. For instance, the VPEX named V300-101-Floor10-001 is physically located in Office 2001.

The only method I've found so far is to create a map using a floor plan, add the VPEX to the map, and place it manually.

Unfortunately, the VPEX is not displaying its name on the XIQ map; it only shows the Slot ID and the IP Address of the Access Switch.

How do you solve this issue?

How are you documenting the physical location of your VPEX units within XIQ?

Thanks for any hints and comments! 🙂

Florian

Re: BPE / VPEX Physical Location

Zdeněk_Pala — Fri, 03 Oct 2025 09:53:38 GMT

Hi Florian.

Seems like it is an ExtremeCloud IQ - Site Engine question.

Your observation is correct. We display on the map only the slot ID.

You can draw objects on the map (Edit > Tool > Draw Rectangle), you can add additional text to the map. So you can adjust the map.

Then you can have your devices (incluing VPEX units) in some areas:

Hope it helps.

Re: BPE / VPEX Physical Location

Sanktis — Mon, 06 Oct 2025 06:54:12 GMT

Hello Zdeněk,

Thank you for your reply and your great work here in the Forum. I've read a lot of your posts and answers! 🙂

I was hoping there was another tweak for this. Unfortunately, we have a lot of these VPEX devices across different buildings. There is a high chance that users will move a VPEX from Switch A to Switch B. Of course, this changes the slot ID as well 😄 (We do have a ZTP solution for the VPEX).

Perhaps a feature request could be that the Description of the VPEX can be optionally displayed in the MAP, or even better, as its own Device Category for Inventory 😉

Cheers
Florian