> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/product-advisories/historical-notices/obsolescence-notice-g269-tube-rod-insu.md).

# G269 Tube Rod Insulators obsolescence — July 2019

Review the G269 Tube Rod Insulator discontinuation and replacement guidance.

The **Tube Rod Insulator**, also known as the Sleeve Insulator, is outsource-manufactured in New Zealand.

Resulting from numerous quality-related issues, the supplier is no longer supplying the product, and there is **no alternative supplier available**. This results in **immediate obsolescence once existing stock is consumed**.

## Products affected

| Part   | Description                           |
| ------ | ------------------------------------- |
| G26901 | TUBE ROD INSULATOR BLK 2.4M (26 WIRE) |
| G26902 | TUBE ROD INSULATOR BLK 0.7M (7 WIRE)  |
| G26903 | TUBE ROD INSULATOR BLK 1.0M (11 WIRE) |
| G26905 | TUBE ROD INSULATOR BLK 2.1M (23 WIRE) |
| G26906 | TUBE ROD INSULATOR BLK 2.6M (28 WIRE) |
| G26907 | TUBE ROD INSULATOR BLK 3.0M (33 WIRE) |

## Recommendation

Use the equivalent Gallagher **security post and intermediate insulators** as replacements. Alternative solutions were being investigated but will take time.

Contact: Dave Solly, Product Manager - Perimeter Systems.

***

🔗 **Related**

* [Product Advisories](/knowledge-hub/products/product-advisories.md). The full register of obsolescence, security, and deprecation notices.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/product-advisories/historical-notices/obsolescence-notice-g269-tube-rod-insu.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.