Project

General

Profile

Actions

Feature #10526

closed

Support for Cisco NX-OS PowerOn Auto Provisioning (POAP)

Added by Fernando Carolo almost 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Unattended installations
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cisco Nexus switches support a bootstrap method to upgrade software images called PowerOn Auto Provisioning (POAP). Our goal is to add support for POAP provisioning for switches running NX-OS using DHCP and TFTP via Foreman.

Status

Some patches are being prepared, in order to send a pull request. Besides Foreman server, a patch is also required on the DHCP and TFTP smart proxies, since POAP requires different DHCP options sent to the client switches.

Description

POAP is described in some Cisco manuals:

Compatibility

This is being tested with Cisco Nexus 6000 series switches running NX-OS 7.x, but it should also work with other families, such as the Nexus 7000 and 9000 series.


Related issues 1 (0 open1 closed)

Copied to Smart Proxy - Feature #10527: DHCP/TFTP support for Cisco NX-OS PowerOn Auto Provisioning (POAP)ClosedFernando Carolo05/15/2015Actions
Actions #1

Updated by Fernando Carolo almost 9 years ago

  • Copied to Feature #10527: DHCP/TFTP support for Cisco NX-OS PowerOn Auto Provisioning (POAP) added
Actions #2

Updated by Fernando Carolo almost 9 years ago

Update

Some updates, based on the results of my internal tests so far. These issues and quirks will reflected in
the final pull request, so I'm writing them down here:

  • A new OperatingSystem family was added to handle NX-OS, mainly because the necessary scripts and DHCP options are very different from the other operating systems. I used the same solution that handles different DHCP options for Solaris and Junos.
  • A new template type was also added for POAP, to help differentiate it from other provisioning tools.
  • A dummy partition table template was added to keep things a little organized, since this seems to be a requirement. The switches never retrieve and never use them, however.
  • Still thinking about ways to handle versions numbers, since the standard major/minor numbers from Foreman are not enough for Cisco releases.
Actions #3

Updated by The Foreman Bot almost 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2464 added
  • Pull request deleted ()
Actions #4

Updated by Anonymous over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #5

Updated by Marek Hulán over 8 years ago

  • translation missing: en.field_release set to 35
Actions

Also available in: Atom PDF