# Unable to ping from some self ip on Velos

**URL:** <https://community.f5.com/t/unable-to-ping-from-some-self-ip-on-velos/75825>\
**Category:** Technical Forums\
**Tags:** big-ip-ltm\
**Created:** [February 27, 2025, 11:07am UTC](https://community.f5.com/t/unable-to-ping-from-some-self-ip-on-velos/75825 "2025-02-27T11:07:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![unavailable](https://avatars.discourse-cdn.com/v4/letter/u/b487fb/32.png) [@unavailable](https://community.f5.com/u/unavailable)\
**Post date:** [February 27, 2025, 11:07am UTC](https://community.f5.com/t/unable-to-ping-from-some-self-ip-on-velos/75825/1 "2025-02-27T11:07:05Z")

</div>

Hello team,

I have configured a tenant on my Velos, everything works fine but, recently I have verified that

when I try to ping to my default gw with the&nbsp; interface asociate to a self ip yellow-fe ping is ok but,

wher i try to do it by using another interface associate to a different self ip such as Mam\_Fe ping does not works as expected.

I have attached the evidence.  
I have reconfigured the vlan on my blade with no success; i’ve veified everything on my F5 but it seems that the configuration is ok.

Somebody could&nbsp; help me for fixing this problem ?

Many thanks in advance for your time .

Awaiting your news.

---

<div class="post-metadata">

**Author:** ![Jmtaylor](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/jmtaylor/32/22145_2.png) [@Jmtaylor](https://community.f5.com/u/Jmtaylor)\
**Post date:** [December 12, 2025, 4:45pm UTC](https://community.f5.com/t/unable-to-ping-from-some-self-ip-on-velos/75825/2 "2025-12-12T16:45:16Z")

</div>

@unavailable &nbsp; Hello ,&nbsp; just wondering if you&nbsp; ever found the solution to this query.&nbsp; I&nbsp; was able to&nbsp; find some information for you&nbsp; if not

1. **Remove and re-add the affected VLAN(s) to the tenant.**
2. **Verify ARP table and routing table on the tenant.**
3. **If the issue persists, set the tenant to provisioned, wait, then set back to deployed.**
4. **If you are using&nbsp;ping -I \<self-IP\>, ensure your routing table is correct for the desired egress interface.**
5. **If you are trying to ping management IPs between tenants on the same chassis, this is not supported.**