Discovery | F5 rSeries Appliances Running F5OS Are Not DiscoveredIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper p { margin: 0 0 0.75em 0; } Discovery of F5 rSeries appliances (including r4800, r5800, and other rSeries models) fails to create a complete CI. While a custom SNMP OID Classification can be added to trigger the out-of-box (OOB) F5 Load Balancer pattern, the pattern cannot collect any meaningful data from the device, and the IRE fails with reason MISSING_MINIMUM_ATTRIBUTES. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper ul { margin: 0 0 0.75em 0; padding-left: 1.5em; } .kb-wrapper li { margin-bottom: 0.4em; } .kb-wrapper code { background:#e6f0f5; color:#032D42; border:1px solid #b8cfd8; padding:1px 4px; border-radius:3px; font-size:11pt; } Discovery run completes but no Load Balancer CI is created for the F5 rSeries device.IRE failure with reason MISSING_MINIMUM_ATTRIBUTES appears in the Discovery log.Only sysName and sysDescr are populated from the device; all F5-specific fields are empty.No Serial Number, Status ID, LB Interfaces, Virtual Servers, Pools, Pool Members, or VLANs are collected.Other non-rSeries F5 devices on the same Discovery schedule complete successfully. Facts<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper ul { margin: 0 0 0.75em 0; padding-left: 1.5em; } .kb-wrapper li { margin-bottom: 0.4em; } .kb-wrapper code { background:#e6f0f5; color:#032D42; border:1px solid #b8cfd8; padding:1px 4px; border-radius:3px; font-size:11pt; } F5 rSeries appliances run F5OS as the host operating system, not BIG-IP TMOS.The OOB F5 Load Balancer patterns (SNMP, SSH, and iControl REST) were built exclusively against the BIG-IP TMOS SNMP MIB (1.3.6.1.4.1.3375).F5OS does not implement the 1.3.6.1.4.1.3375 MIB subtree and returns no data for any OID under that enterprise prefix.Adding a custom SNMP OID Classification can trigger the OOB F5 Load Balancer pattern against an rSeries device, but because F5OS does not implement the required MIB subtree, no F5-specific data is returned regardless.The device does respond to the standard system MIB (1.3.6.1.2.1.1), which is why sysName and sysDescr are collected.F5 rSeries appliances can host BIG-IP TMOS tenants, each with their own dedicated management IP.There is no OOB data model support for the parent-child relationship between an rSeries host and its BIG-IP tenants.This issue affects all ServiceNow versions. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Releases Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper p { margin: 0 0 0.75em 0; } .kb-wrapper code { background:#e6f0f5; color:#032D42; border:1px solid #b8cfd8; padding:1px 4px; border-radius:3px; font-size:11pt; } The OOB F5 Load Balancer Discovery patterns rely entirely on the BIG-IP TMOS SNMP MIB (1.3.6.1.4.1.3375) to collect Load Balancer data. Additionally, the patterns do not trigger against F5 rSeries devices out of the box — a custom SNMP OID Classification must be added manually to cause the classifier to match the device. Even with that classification in place, F5 rSeries appliances run F5OS at the platform level, which does not implement the required MIB subtree, so the pattern cannot collect the data needed to build a complete CI. The missing Serial Number causes the IRE to fail with MISSING_MINIMUM_ATTRIBUTES, as both name and serial number are required to identify and create a Load Balancer CI. F5 rSeries/F5OS Discovery is not supported by OOB patterns at this time. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper p { margin: 0 0 0.75em 0; } .kb-wrapper .option-heading { font-size: 13pt; font-weight: bold; color: #032D42; margin: 1em 0 0.4em 0; } .kb-wrapper .callout-info { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 0.6em 1em; margin: 0.75em 0; border-radius: 0 4px 4px 0; } .kb-wrapper a { color: #032D42; } There is no OOB resolution at this time. The following options are available. Option 1 - Discover via BIG-IP Tenant IP The rSeries platform hosts BIG-IP tenants, each with their own dedicated management IP address accessible via CLI, web UI, and API. Tenants running standard BIG-IP TMOS may be discoverable using the existing OOB F5 Load Balancer patterns pointed at the tenant management IP. Note: This approach discovers the tenant only, not the underlying rSeries platform. The parent-child relationship between the rSeries host and its tenants is not reflected in the current data model. Option 2 - Vote on Enhancement Request An active Community Idea exists for rSeries Discovery support. Vote and add business justification in the comments to help prioritize this with the product team: COMMIDEA0025026 - F5 r5800 Hypervisors running F5OS are not supported out-of-box by ServiceNow Discovery If the Ideas portal is not accessible, contact Now Support to submit a vote on your behalf. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper ul { margin: 0 0 0.75em 0; padding-left: 1.5em; } .kb-wrapper li { margin-bottom: 0.6em; } .kb-wrapper a { color: #032D42; } .kb-wrapper .disclaimer { font-size: 10pt; font-style: italic; display: block; margin-top: 2px; } KB1646476 - Discovery pattern 'F5 Load Balancer' filtering out valid Load Balancer ServicesCOMMIDEA0025026 - F5 r5800 Hypervisors running F5OS are not supported out-of-box by ServiceNow Discovery This link points to a ServiceNow Community article. Community content is not official ServiceNow documentation and may be updated or removed without notice.