For an end user to request access, they need to go to

• Community Request

• Support Portal Request

• Support Contact Information

• Support Overview

• Support SLA

From Hardware Addendum in EULA. - RMA kit is Refurbished.

If Customer makes a claim that Hardware has failed more than sixty (60) days after the Delivery Date, but during the Hardware Warranty Period, and Infoblox opts to replace the Hardware, replacement will be with refurbished Hardware. All replacement or repaired Hardware shall be warranted for the remainder of the original Hardware Warranty Period or for a period of thirty (30) days following the repair or replacement date, whichever is longer.

— This page then says about NBD:

Support may include next business day Hardware replacement service (“NBD”). To be eligible for NBD Hardware replacement, Hardware must be located in a geography’s depot delivery radius as identified on Infoblox’s Global RMA Locations List for NBD service coverage. In order to ship the same day, the RMA must be processed by 3:00 pm local time of the depot processing the RMA for shipment. For Hardware located outside of a geography’s depot delivery radius identified as NBD accessible, replacement Hardware will be shipped by reasonable, commercially available means for carrier delivery to Customer based on available delivery times. If Infoblox’s record of the installation location differs from the Customer’s requested ship to address, Infoblox will use commercially reasonable efforts to deliver Hardware by NBD.

NIOS Lifecycle policy is published here.

An important thing to note is that if EOL is extended beyond 36 months after GA, then the EOL will eat into the EOTS window rather than push the EOTS window further out.

Thus, 8.6 goes EOL 31 Oct 2024 which is three years and seven months after GA. THis means that there is no EOTS window and any needed EOTS window must be agreed with support and senior management PRIOR to NIOS 8.6 going EOL.

When you receive a replacement device (RMA) you should find that the document pouch on the replacement device shipping box contains not only the waybill for the delivery to you but also the return AirWay Bill (RAWB) for delivery of the faulty appliance back to Infoblox.

In certain cases, the RAWB maybe missing in the Pouch due to an error from Logistics/ Delivery partner's end.

If the document is missing, update the support case used for the RMA and instructions will be given on how to get the RAWB.

RMA Return instructions here.

Returning faulty hardware instructions here (RMA Return Process: How to Request a Waybill, Pack, and Ship a Defective Unit).

From the page linked above (RMA Return Process: How to Request a Waybill, Pack, and Ship a Defective Unit)

NOTE: If you do not wish to return the Hard Drive with the defective appliance due to security concerns, you may remove it before shipping. However, please note that if the failure is related to the Hard Drive, Failure Analysis (FA) will not be possible.

• How to collect Support bundle, Traffic capture and Database backup KB Article

• Keep the title concise. e.g. “Company Name - NIOS - HW Device Rebooting”. Remember, you and your team at Infoblox may want to review cases and it is much easier to read a list if the titles are well put together.
• If you use a shared account to access the support portal (e.g. networkoperations@example.com), make sure you put your name at the end of your replies to support. There can be cases where the account team at Infoblox are asked to help out but they don't know who at the customer site to contact because there is no actual name.
• Put detail in the description but not too much. Case updates and notes are where the full data should go (e.g. only a paragraph or so in description). I've seen some customers paste pages and pages of console output into the description. Don't be that guy.
• Support Bundle from the member(s) experiencing the issue (including Core Files)
• Support Bundle from the active Grid Master (including Core Files)
• Grid Backup
• Timestamp for when this environment was last confirmed to be working
• Timestamp for when the issue was first observed
• Timestamps for any related changes or admin activity
• Please provide the below CLI output from the impacted member(s):
  • show disk
  • show disk_usage_sorted (after the first page of results, press 'q' and <return> to avoid printing the full list)
• If an RMA is needed, you will be asked for the following for shipping:
  • Serial number of the failed unit
  • Ship to Organization
  • Shipping address
  • Contact
  • Phone Number
  • Ship to city
  • Postal code
  • NOTE, if you need Infoblox to ship to somewhere like a data center, check with your data center to see if they need a reference number to accept goods. If they do, you must provide support with this reference number before the device ships or there may be delays in getting it delivered.

Infoblox and Customer will commit resources during local business hours to resolve issue or obtain workaround.

For Hardware specific issues, the appliance in concern MUST have an active maintenance contract for processing any RMA (if needed).

When RMA needed, customer must provide:

Serial number of the failed unit:

• Ship to Organization :
• Shipping address :
• Contact :
• Phone Number :
• Ship to city:
• Postal code :

IF DELIVERING TO A DATACENTRE, THE CUSTOMER MAY NEED TO PROVIDE A REFERENCE NUMBER FOR THE COURIER TO USE. E.G when delivering to a large banking DC.

When creating SEV 2 cases, prepare to provide support with the following info

• Number of clients/end users impacted:
• Number of Infoblox hosts/servers affected:
• Impacted service (DNS/DHCP/DDNS/NTP):
• Date and Time when the issue started:
• Business/financial impact:
• Production/UAT environment details:

• Premium Maintenance-Enterprise
• Elite Maintenance-Enterprise
• Partner Premium Maintenance-Enterprise
• Partner Elite Maintenance-Enterprise

• Premium Maintenance-ISP
• Elite Maintenance-ISP
• Partner Premium Maintenance-ISP
• Partner Elite Maintenance-ISP

• Premium Maintenance-MSP

• Premium Maintenance-Enterprise
• Elite Maintenance-Enterprise
• Hardware Maintenance-Enterprise
• Partner Premium Maintenance-Enterprise
• Partner Elite Maintenance-Enterprise
• Partner Hardware Maintenance-Enterprise

• Premium Maintenance-ISP
• Elite Maintenance-ISP
• Hardware Maintenance-ISP
• Partner Premium Maintenance-ISP
• Partner Elite Maintenance-ISP
• Partner Hardware Maintenance-ISP

• Premium Maintenance-MSP
• Hardware Maintenance-MSP