# ISV logging in 17.1.2.2

**URL:** <https://community.f5.com/t/isv-logging-in-17-1-2-2/76356>\
**Category:** Technical Forums\
**Tags:** application-delivery\
**Created:** [July 17, 2025, 10:05am UTC](https://community.f5.com/t/isv-logging-in-17-1-2-2/76356 "2025-07-17T10:05:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![KeesvandenBos](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@KeesvandenBos](https://community.f5.com/u/KeesvandenBos)\
**Post date:** [July 17, 2025, 10:05am UTC](https://community.f5.com/t/isv-logging-in-17-1-2-2/76356/1 "2025-07-17T10:05:36Z")

</div>

Today I noticed logging on a BIG-IP VE that I can’t explain. Also I can’t find much about online.

We see the following logging (in a fast rate):

Jul 17 10:44:20 BIGIP-10 info tmm[18302]: 017b0007:6: IVS (connecting from parent 10.10.10.111:443 → :::0): Internal virtual server /Common/Monitor-example.com\_ivs is sending HTTP Response  
Jul 17 10:44:20 BIGIP-10 info tmm[18302]: 017b0008:6: IVS (connecting from parent 10.10.10.111:443 → :::0): Internal virtual server /Common/Monitor-example.com\_ivs is done sending HTTP Response  
Jul 17 10:44:20 BIGIP-10 info tmm1[18302]: 017b0004:6: IVS (connecting from parent 10.10.10.162:443 → :::0): Internal virtual server /Common/Monitor-www.excample.com\_ivs accepted internal connection  
Jul 17 10:44:20 BIGIP-10 info tmm1[18302]: 017b0007:6: IVS (connecting from parent 10.10.10.162:443 → :::0): Internal virtual server /Common/Monitor-www.example.com\_ivs is sending HTTP Response  
Jul 17 10:44:20 BIGIP-10info tmm1[18302]: 017b0008:6: IVS (connecting from parent 10.10.10.162:443 → :::0): Internal virtual server /Common/Monitor-www.example.com\_ivs is done sending HTTP Response

There are no internal virtual servers on the system, log levels are default.

Logging is at a high rate.

Has any of you seen this on their own boxes? And I would like to stop it.

Thanks in advance.

Kees

---

<div class="post-metadata">

**Author:** ![VishnuGatla](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/vishnugatla/32/10865_2.png) [@VishnuGatla](https://community.f5.com/u/VishnuGatla)\
**Post date:** [July 17, 2025, 12:54pm UTC](https://community.f5.com/t/isv-logging-in-17-1-2-2/76356/2 "2025-07-17T12:54:06Z")

</div>

Hello Kees,

Try with changing the logging level for TMM from info to warning:

tmsh modify /sys db log.tmm.level value warning

Increase the monitor interval to reduce how often checks happen.

---

<div class="post-metadata">

**Author:** ![KeesvandenBos](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@KeesvandenBos](https://community.f5.com/u/KeesvandenBos)\
**Post date:** [July 20, 2025, 3:39pm UTC](https://community.f5.com/t/isv-logging-in-17-1-2-2/76356/3 "2025-07-20T15:39:20Z")

</div>

Hello,

Thank you unfortunately changing the tmm log level didn’t resolve it.

---

<div class="post-metadata">

**Author:** ![VishnuGatla](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/vishnugatla/32/10865_2.png) [@VishnuGatla](https://community.f5.com/u/VishnuGatla)\
**Post date:** [July 20, 2025, 5:47pm UTC](https://community.f5.com/t/isv-logging-in-17-1-2-2/76356/4 "2025-07-20T17:47:38Z")

</div>

Thank you, have you tried with increasing the monitor timeout values ?

---

<div class="post-metadata">

**Author:** ![KeesvandenBos](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@KeesvandenBos](https://community.f5.com/u/KeesvandenBos)\
**Post date:** [August 2, 2025, 9:06am UTC](https://community.f5.com/t/isv-logging-in-17-1-2-2/76356/5 "2025-08-02T09:06:35Z")

</div>

It was a logging profile with informational. changes it to warning to resolve it.

Thank you for the suggestions.

Cheers,

Kees