# IBM I extension error

**URL:** <https://community.dynatrace.com/t/ibm-i-extension-error/48323>\
**Category:** Extensions\
**Tags:** databases, ibm, extensions\
**Created:** [October 14, 2024, 7:57pm UTC](https://community.dynatrace.com/t/ibm-i-extension-error/48323 "2024-10-14T19:57:19Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marcelo\_santand](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/marcelo_santand/32/13828_2.png) [@Marcelo\_santand](https://community.dynatrace.com/u/Marcelo_santand)\
**Post date:** [October 14, 2024, 7:57pm UTC](https://community.dynatrace.com/t/ibm-i-extension-error/48323/1 "2024-10-14T19:57:19Z")

</div>

We are trying to configure the new IBM i extension, but we are getting the following message: Failed to assign monitoring configuration to ActiveGate. Reason: Error connecting to host 10.132.0.26. Code: HYT00. Msg: [HYT00] [IBM][System i Access ODBC Driver]Connection login timed out. (30189) (SQLDriverConnect)."

---

<div class="post-metadata">

**Author:** ![Mike\_L](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/mike_l/32/11717_2.png) [@Mike\_L](https://community.dynatrace.com/u/Mike_L)\
**Post date:** [October 14, 2024, 8:19pm UTC](https://community.dynatrace.com/t/ibm-i-extension-error/48323/2 "2024-10-14T20:19:38Z")

</div>

Can you try a telnet from the ActiveGate to 10.132.0.26?

---

<div class="post-metadata">

**Author:** ![Marcelo\_santand](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/marcelo_santand/32/13828_2.png) [@Marcelo\_santand](https://community.dynatrace.com/u/Marcelo_santand)\
**Post date:** [October 14, 2024, 9:49pm UTC](https://community.dynatrace.com/t/ibm-i-extension-error/48323/3 "2024-10-14T21:49:19Z")

</div>

The documentation does not refer to any port, I imagine it should be 8443. Unfortunately telnet is not enabled and I must create a change control to enable this function.

---

<div class="post-metadata">

**Author:** ![Mike\_L](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/mike_l/32/11717_2.png) [@Mike\_L](https://community.dynatrace.com/u/Mike_L)\
**Post date:** [October 14, 2024, 10:14pm UTC](https://community.dynatrace.com/t/ibm-i-extension-error/48323/4 "2024-10-14T22:14:01Z")

</div>

A quick google on what port ODBC uses makes me think it is 8471 for non-SSL and 9471 for SSL. Make sure that they are open.

---

<div class="post-metadata">

**Author:** ![diego\_morales](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/diego_morales/32/2556_2.png) [@diego\_morales](https://community.dynatrace.com/u/diego_morales)\
**Post date:** [October 14, 2024, 10:17pm UTC](https://community.dynatrace.com/t/ibm-i-extension-error/48323/5 "2024-10-14T22:17:05Z")

</div>

Check the [Dynatrace Hub Tile for the IBM i extension](https://www.dynatrace.com/hub/detail/ibm-i/?query=ibm+i&filter=all). It has a TCP table of all the ports for all the different services the driver uses to communicate with IBM i.

---

<div class="post-metadata">

**Author:** ![diego\_morales](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/diego_morales/32/2556_2.png) [@diego\_morales](https://community.dynatrace.com/u/diego_morales)\
**Post date:** [October 14, 2024, 10:54pm UTC](https://community.dynatrace.com/t/ibm-i-extension-error/48323/6 "2024-10-14T22:54:56Z")

</div>

Another note, it’s not very clear but when the driver reports a “login timeout” error, it can also mean the wrong username and/or password was entered.

---

<div class="post-metadata">

**Author:** ![Marcelo\_santand](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/marcelo_santand/32/13828_2.png) [@Marcelo\_santand](https://community.dynatrace.com/u/Marcelo_santand)\
**Post date:** [October 15, 2024, 5:07pm UTC](https://community.dynatrace.com/t/ibm-i-extension-error/48323/7 "2024-10-15T17:07:16Z")

</div>

I managed to activate the extension, the problem was port 449 that was not open and did not work via telnet
