Migration Hub

The Migration Hub reads a topology from another product (an EVE-NG lab file, a GNS3 project, Packet Tracer files or a public GitHub repository) and rebuilds it on the ONEP canvas, with ONEP's own sizing and your own image library. It shows you a preview before anything is created. The result is a normal environment that you can edit, start and capture on.

What it reads#

The page offers four sources as cards. GitHub is selected when you open the page; select another card to change the source.

A topology file on its own can be up to 10 MB: it is a description, not an image. An archive can be up to 200 MB. An archive that contains more than one environment is refused with a message; upload an archive that holds a single environment. A file that is not one of the formats above is refused with a message listing the supported formats.

Start an import#

1. For a fileDrop the file on the area labeled Drop your … here, or click to browse; the analysis starts at once. Clicking the area instead opens the Source step, where Choose a file opens the file picker. You can also drop a file on that step.
2. For GitHubType the repository address and choose Analyze. A repository that holds several environments lists them with their device and link counts; choose one. If a repository has none, the page says No environments found in this repository.

The right of the page lists what the importer understands: devices and roles, links and interfaces, startup configs, image mapping and canvas layout. On the Packet Tracer card a note says the topology is rebuilt on real device images, and that anything ONEP cannot reproduce, such as wireless and IoT devices, is listed before you deploy.

How an import runs#

A row of five steps across the top shows where you are: Source, Analyze, Review, Canvas and Deploy. Back returns to the previous step; on the first step it returns to the source cards.

1. SourcePick the file, the GitHub repository or the environment inside it.
2. AnalyzeA log shows ONEP reading the devices, links, interfaces and layout and classifying every device by vendor, role and operating system. A side panel counts devices and links, shows the roles found and, once finished, the percentage of devices that matched an image in your library. The analysis takes a short while; Review devices turns on when it is done.
3. ReviewReview shows first what needs a decision. Everything that matched is collapsed into a ready list. See Review the import.
4. CanvasThe environment is drawn on a preview canvas for you to check, with the original layout and annotations, a mini-map, zoom controls and a legend of device classes.
5. DeployDeploy to Environment creates it as an isolated environment with every device stopped; you start it when you are ready.

Review the import#

The top of Review names the environment and its source and shows a verdict: Deployable, or for a GitHub repository Needs Kubernetes, Cloud - Terraform, Scripts only or Review needed. Four figures sit below it: Devices, Links, Images matched and Footprint (total memory as the source built it). If the footprint is more than the appliance has, a warning says so; resize the devices or use a larger appliance. ONEP keeps the source hardware unless you change it. Devices imported with no size are sized by ONEP at deploy, or you can set them.

• Needs your attention lists each device that has no matching image in your library, or whose role ONEP detected with low confidence. For each one you can pick an image from the list, type a vCPU and RAM (MB) (blank means automatic), open Get / register to add the image in Centrum, or choose Looks right to accept the detected role. Re-check images matches again after you add an image.
• Below, a collapsed line reports how many devices are ready, with their specs carried from the source file as they are. Open it for a table with Name, Vendor, Role, Class, Runtime, Image, Config (a View link opens the startup config, with Copy), vCPU, RAM (MB) and Confidence. Name, vendor, image and sizing can be edited in place, and columns can be resized.
• The image dot shows how a device matched: green for a match in your library, blue for a device ONEP supplies itself (such as a workstation), amber for an image ONEP substituted from the same family, and grey for none. Point at the dot for the note.

Deploy stays off while any device has no image. Fix it on Review, or the Canvas step tells you how many devices are missing one.

After you deploy#

The Deploy step shows a log (creating the environment, placing nodes, wiring links, drawing annotations) and a summary. When it finishes, ONEP opens the environment on the canvas. If something needs attention first, a Review before continuing notice appears instead, with Continue to environment. It can say:

• the internet exit is queued and finishes shortly after the environment opens;
• devices that were kept isolated because no internet exit could be confirmed;
• links that could not be reproduced and were skipped;
• any other warning from the importer.

If the import fails, the page returns to the Canvas step and shows an error message.

What carries over#

• Devices and links, mapped onto images in your library. The importer also keeps each device's own icon where the source has one.
• Hardware: each device keeps the CPU and memory it had in the source file. Only blank values get a default for the device type.
• Drawing: text labels, shapes and pictures, at their original positions.
• Environment details that the source file carries, such as the author and the description.

Startup configurations come across where the source file carries them, and you can read them on Review.

What ONEP does not reproduce#

Anything ONEP cannot reproduce is listed in a What ONEP will not reproduce panel on the Deploy step, and the first such line also appears in the analysis log. For Packet Tracer files the list covers:

• devices ONEP has no equivalent for, such as wireless and IoT devices, named as Not imported, and the cables that ended at them;
• command support and behavior: Packet Tracer devices run a teaching model of the Cisco operating system, and ONEP rebuilds them on real device images, so commands and behavior differ;
• simulation-mode scenarios, PDU animations, activity grading in .pka files, and the physical-workspace layout.

What you supply#

• The images. An import maps the topology onto your library; it does not bring vendor images with it. Review lists what is missing, and you add it through Discover or Register image in Centrum.
• Your own Cisco license, for devices that boot Cisco IOS images. It is added on the Cisco IOL license card in Settings › Licensing. See Licensing.

One at a time#

ONEP imports one environment at a time. If you start a second import while one is running, it is refused with the message ONEP imports one environment at a time. Another import is in progress; try again when it finishes. A license can also limit how many imports are allowed in any 30 days; the refusal then states the date the next import is possible.