infoblox_nios:support
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| infoblox_nios:support [2024/03/08 16:31] – [Creating Cases] bstafford | infoblox_nios:support [2025/04/25 11:58] (current) – bstafford | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== NIOS Support ====== | ====== NIOS Support ====== | ||
| + | ====== Infoblox Support Portal ====== | ||
| + | For an end user to request access, they need to go to | ||
| + | |||
| + | * [[https:// | ||
| + | |||
| + | * [[https:// | ||
| + | |||
| + | * [[https:// | ||
| + | |||
| + | * [[https:// | ||
| + | |||
| + | * [[https:// | ||
| + | |||
| + | * [[https:// | ||
| + | ===== Hardware Support ===== | ||
| + | From [[https:// | ||
| + | |||
| + | 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. | ||
| + | |||
| + | |||
| + | --- [[https:// | ||
| + | |||
| + | Support may include next business day Hardware replacement service (“NBD”). To be eligible for NBD Hardware replacement, | ||
| + | |||
| + | ===== NIOS Lifecycle ===== | ||
| + | NIOS Lifecycle policy is published [[https:// | ||
| + | |||
| + | 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. | ||
| + | ===== RMA ===== | ||
| + | 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' | ||
| + | |||
| + | 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 [[https:// | ||
| + | |||
| + | Returning faulty hardware instructions [[https:// | ||
| + | |||
| + | 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. | ||
| + | ===== Get Support Files ===== | ||
| + | * How to collect Support bundle, Traffic capture and Database backup [[https:// | ||
| ===== Creating Cases ===== | ===== Creating Cases ===== | ||
| * Keep the title concise. e.g. " | * Keep the title concise. e.g. " | ||
| - | * Put detail in the description but not too much. Case updated | + | |
| + | | ||
| * Support Bundle from the member(s) experiencing the issue (including Core Files) | * Support Bundle from the member(s) experiencing the issue (including Core Files) | ||
| * Support Bundle from the active Grid Master (including Core Files) | * Support Bundle from the active Grid Master (including Core Files) | ||
| Line 35: | Line 82: | ||
| Serial number of the failed unit: | Serial number of the failed unit: | ||
| - | Ship to Organization : | + | * 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. | 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. | ||
| - | ===== Support Types ===== | ||
| + | ===== Creating SEV 2 Cases ===== | ||
| + | When creating SEV 2 cases, prepare to provide support with the following info | ||
| + | * Number of clients/end users impacted: | ||
| + | * Number of Infoblox hosts/ | ||
| + | * Impacted service (DNS/ | ||
| + | * Date and Time when the issue started: | ||
| + | * Business/ | ||
| + | * Production/ | ||
| + | ===== Support Types ===== | ||
| + | ==== Software ==== | ||
| * Premium Maintenance-Enterprise | * Premium Maintenance-Enterprise | ||
| * Elite Maintenance-Enterprise | * Elite Maintenance-Enterprise | ||
| Line 57: | Line 113: | ||
| * Premium Maintenance-MSP | * Premium Maintenance-MSP | ||
| + | ==== Hardware ==== | ||
| * Premium Maintenance-Enterprise | * Premium Maintenance-Enterprise | ||
| * Elite Maintenance-Enterprise | * Elite Maintenance-Enterprise | ||
infoblox_nios/support.1709915519.txt.gz · Last modified: by bstafford
