diff --git a/docs/administration/advanced-routing.md b/docs/administration/advanced-routing.md index b90d51ca..b4bca091 100644 --- a/docs/administration/advanced-routing.md +++ b/docs/administration/advanced-routing.md @@ -3,17 +3,30 @@ title: "Advanced Routing" sidebar_position: 2 --- -You can add complex or advanced routing for your Device42 appliance or delete it using the console menu. +You can add complex or advanced routing for your Device42 appliance or delete it using the virtual machine (VM) console menu. -1. To configure advanced routing, choose option **15** from the **Device42 Setup/Troubleshooting Menu**. Log in to the console of the Device42 VM to access this menu: +To add a new route, follow these steps: - ![advanced-routing-option](/assets/images/advanced-routing/console-advanced-routing-option.png) +1. Log in to the Device42 VM console. +2. Choose **(u) Network, Connectivity and Utilities**. -2. To add a new route, enter option **a**. Print the routing table with option **b**. + ![Network options](/assets/images/advanced-routing/1-network.png) + +3. Select **(r) Routing**. + + ![Routing options](/assets/images/advanced-routing/2-routing.png) + +4. Select **(a) Add a new Route** from the **Routing Configuration Main Menu**. - ![Advanced routing options](/assets/images/advanced-routing/console-routing-submenu.png) + ![Add route option](/assets/images/advanced-routing/3-route-options.png) + +5. Fill in the new route details and click **Add Route**. Use the `Tab` key to navigate to the next field. + + ![Add route details](/assets/images/advanced-routing/4-route-details.png) -3. After configuring the new route, enter option **d** to apply changes. The Device42 VM must be manually rebooted to clear deleted routes. +6. After configuring the new route, enter option **(p) Apply Routes** from the previous menu to apply the changes. + +The Device42 VM must be manually rebooted to clear deleted routes. :::info Advanced routing instructions are also available [in video format here](how-to-videos/add-a-new-route-to-device42.md). diff --git a/docs/getstarted/faqs/index.mdx b/docs/getstarted/faqs/index.mdx index 0128cc46..07b77a60 100644 --- a/docs/getstarted/faqs/index.mdx +++ b/docs/getstarted/faqs/index.mdx @@ -1,19 +1,22 @@ --- -title: "FAQ's" +title: "FAQs" --- import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' -Whether you're new to Device42 or a seasoned pro, this list of **Device42 frequently asked questions** probably has information you'll find useful. This list is updated pretty regularly, and contains a selection of the questions most often asked about Device42. +The **Device42 frequently asked questions** list is regularly updated and includes information for both new users and seasoned professionals. -If you've just downloaded Device42 for the first time and are looking for help getting up and running, please refer to our [getting started guide](getstarted/index.md) if you're looking for help getting your instance up and running. The getting started guide is tailored to new users, specifically. +If you've just downloaded Device42 for the first time and want help getting your instance up and running, our [Getting Started](getstarted/index.md) guide is specifically tailored for users who are new to our software. -## How do I log into my Device42 instance? +## How Do I Log In to My Device42 Instance? -With a default configuration, visit: `https://IP_or_fqdn_for_device42_vm` in your favorite web browser, and then log in by entering the following \[default\] credentials: Default user: `admin` Default pass: `adm!nd42` +With a default configuration, visit `https://IP_or_fqdn_for_device42_vm` in your favorite web browser, and log in using the following default credentials: -## Which browser should I use? +- Username: `admin` +- Password: `adm!nd42` + +## Which Browser Should I Use? Device42 recommends using the web browsers (or more recent versions) listed below. @@ -22,44 +25,63 @@ Device42 recommends using the web browsers (or more recent versions) listed belo - Firefox — 72.0.1 - Safari — 13.1.2 (13609.3.5.1.5) -## How do I get my current data into Device42? +## How Do I Get My Current Data Into Device42? + +You can use any of the following tools to import your data to Device42: + +- [**Device42 autodiscovery**](auto-discovery/index.mdx): Device42 features a variety of autodiscovery methods for different user needs, including SNMP network device discovery, VMware autodiscovery, ping sweep, Windows and Linux autodiscovery, and more. You may also use individual Python or PowerShell scripts to customize and automate your discovery and inventory processes. + + :::note + Review the [recommended initial discovery sequence](auto-discovery/autodisc-best-practices.md) to learn more. + ::: -**There are many ways to get your data into Device42**: +- [**Microsoft Excel / CSV (spreadsheet) import**](integration/imports/index.md): The **Tools > Imports/Exports (xls)** page outlines your options for importing MS Excel spreadsheets to Device42 and provides sample Excel sheets to help you format your existing spreadsheets so that uploading your existing data is as easy as possible. +- [**Device42 generic import tool**](https://www.device42.com/blog/2018/06/19/new-features-added-to-the-generic-import-tool/): You can use the Device42 generic import tool to add and map fields for existing data from most spreadsheet formats. Learn more about formatting best practices in the Device42 walkthrough for manually [Importing Data From Existing Spreadsheets](getstarted/importing-data-from-existing-spreadsheets.mdx). +- [**RESTful APIs**](https://api.device42.com): These enable you to programatically automate your network documentation and leverage your asset data for scripts and automation. Simply add RESTful APIs to your regular workflow to leverage Device42 as single source of truth for systems such as provisioning and monitoring. +- **Device42 web UI**: You can use the Device42 web interface to import your data. +- **Templates/bulk operations**: Certain object types are easier to add using templates or models. For example, it is easier to use [PDU models](infrastructure-management/power-units/defining-pdu-models.md) to create PDUs, [switch port templates](infrastructure-management/ipam/switch-templates.md) to create switches and ports, and [patch panel models](infrastructure-management/power-units/defining-pdu-models.md) to create patch panel ports and bulk backport connectivity for patch panels. -- [**Device42 Auto-discovery**](auto-discovery/index.mdx): D42 features a variety of autodiscovery methods, the best of which depends on your needs: SNMP network device discovery, VMware auto-discovery, ping sweep, Windows and Linux auto-discovery, and more; you may also use individual python/powershell scripts to customize & automate your discovery and/or inventory process. Read about the [recommended initial discovery sequence](auto-discovery/autodisc-best-practices.md) here, as well! -- [**Microsoft Excel / CSV (spreadsheet) import**:](integration/imports/index.md) _Tools > Imports/Exports (xls)_ has options for MS Excel spreadsheet import, including sample Excel sheets that will help you format your existing spread sheets to make bringing your existing data into Device42 as easy as possible. -- The [**Device42 Generic Import Tool**](https://www.device42.com/blog/2018/06/19/new-features-added-to-the-generic-import-tool/) is another way to import data from existing spreadsheets of just about any format, mapping fields as appropriate via the Device42 generic import tool. For manual spreadsheet import, see this [walkthrough on how to best format an existing spreadsheet for import into Device42.](getstarted/importing-data-from-existing-spreadsheets.mdx) -- [**RESTful APIs**](https://api.device42.com): Programatically automate your network documentation and/or leverage your asset data for scripts & automation! Add these to your regular work flow to leverage Device42 as single source of truth for systems such as provisioning and monitoring. -- The **Device42 Web UI**: Of course, you can always use the web-UI _(user interface)_ to add data :) -- **Templates/bulk operations**: Certain types of objects are easier to add using templates or models. For example, [PDU models](infrastructure-management/power-units/defining-pdu-models.md) to create PDUs, [Switch port templates](infrastructure-management/ipam/switch-templates.md) to create switches and ports, [Patch panel models](infrastructure-management/power-units/defining-pdu-models.md) to create patch panel ports and bulk back port connectivity for patch panels. +## What Is the Recommended Order for Running Different Discoveries? -## What is the recommended order for running different discoveries? +The recommended **Initial Discovery Sequence** section of the [**Autodiscovery Best Practices**](/auto-discovery/autodisc-best-practices/) provides a detailed rundown of how to order multiple discoveries. -See the "Recommended Initial Discovery Sequence" section of the [autodiscovery best practices](/auto-discovery/autodisc-best-practices/) page for a full detailed rundown. +**In short**: Run network discovery first to build your layer-2 network landscape. Discovered devices will then be added to their appropriate subnets as they are discovered. -**In short**: run network discovery first to build your Layer 2 network landscape. Discovered devices, going forward, are added to their appropriate subnets as they are discovered -- _Note that if device discoveries are run before the subnets for those devices exist in Device42, you might run into issues and/or create extra work for yourself!_ +:::note +If device discoveries are run before the subnets for devices that exist in Device42, you might run into issues or create extra work for yourself! +::: -## How do I set up an RC / Remote collector? +## How Do I Set Up a Remote Collector? -Setting up a remote collector is easy! See the [RC Setup Instructions](auto-discovery/remote-collector-rc.md) which include deployment examples. +Easily set up a Remote Collector (RC) by referring to the instructions and deployment examples on the Device42 [Remote Collector](auto-discovery/remote-collector-rc.md) page. -## How do I migrate my existing data from other tools? +## How Do I Migrate My Existing Data From Other Tools? -We provide few ready to use scripts to migrate your data from tools like RackTables, Rackmonkey, OpenDCIM, Solarwinds IPAM, Aperture etc. and the download links can be found at [Device42 Migration page](https://www.device42.com/migrations/) or at [Device42 github repository](https://github.com/device42). +The Device42 [Migrations](https://www.device42.com/migrations/) page provides a few ready-to-use scripts for migrating your data from tools like RackTables, Rackmonkey, OpenDCIM, SolarWinds IPAM, Aperture, etc. The download links for these scripts can also be found in the [Device42 GitHub repository](https://github.com/device42). -## What discovery jobs can I run from a Remote Collector / RC? +## Which Discovery Jobs Can I Run From a Remote Collector? -Current releases of Device42 support ALL discovery jobs, now including WMI & Power SNMP from RC's. If you are reading this, all of them! [Setup your RC](auto-discovery/remote-collector-rc.md) today! (RC will only automatically update when it coincides with an MA update) +Current releases of Device42 support **all** discovery jobs, including WMI and Power SNMP from RCs. [Set up your RC](auto-discovery/remote-collector-rc.md) today! -## How do I Migrate Existing Power Appliance Jobs to a Remote Collector (RC)? +:::note +RCs will only automatically update when an RC update coincides with an MA update. +:: -Migrating jobs that were created for the original standalone power appliance is possible with existing tools. Simply follow the [existing power job migration guide here](infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration.md) to migrate jobs to the new RC of your choice. +## How Do I Migrate Existing Power Appliance Jobs to a Remote Collector? -## How do I add blade servers to Device42? +You can use existing tools to migrate jobs that were created for the original standalone power appliance to a new RC of your choosing. Simply follow the [Power RC Setup and Existing Job Migration](infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration.md) guide. -This topic has been discussed on support portal : [How to represent blade servers in Device42?](https://support.device42.com/hc/en-usentries/23369387) tldr; Add a new device with "blade chassis" selected. Then you add devices, type "blade", and choose the blade chassis device as the host device. _Note that blade chassis accept blades in "blade slots", which you can custom-configure to match your chassis & port layout!_ +## How Do I Add Blade Servers to Device42? -## How do I handle unknown device types? +The Device42 Support Portal article, [How to represent blade servers in Device42](https://support.device42.com/hc/en-us/articles/222221468-How-to-represent-blade-servers-in-device42#:~:text=When%20adding%20a%20new%20device,the%20blade%20server%20belongs%20to.), discusses this in detail. + +**In short**: Add a new device with "blade chassis" selected. When you add devices, type "blade" and choose the blade chassis device as the host device. + +:::note +Blade chassis accept blades in "blade slots" that you can custom-configure to match your chassis and port layout! +::: + +## How Do I Handle Unknown Device Types? -During initial device discovery, some devices will show up as type "unknown". This can be fixed by: +During initial device discovery, some devices will show up as type "unknown". This can be fixed using the following methods: + +- From **Infrastructure > [Hardware Models](/infrastructure-management/devices/hardware-models-templates.mdx)**, change the associated hardware model. This will change all current and future associated devices. +- From **Devices > All Devices**, filter for type "unknown" and bulk change the device type. +- Export unknown devices in Excel format by clicking the **Report** button in the top right corner of the device list page. Edit the Excel file to match **Tools > Imports/Exports (xls)**. Change the type and re-import the Excel file. +- Make the change using RESTful APIs. -- Changing the associated hardware model (this will change all associated devices - current and future). Do this from **Infrastructure > [Hardware Models](/infrastructure-management/devices/hardware-models-templates.mdx)**. -- From **Devices > All Devices**, you can filter for type "unknown" and bulk change the device type. -- You can export unknown devices in Excel format by clicking the **Report** button on the top right corner of the device list page. Edit the Excel file to match **Tools > Imports/Exports (xls)**. Change the type and re-import the Excel file. -- Make the change using REST APIs. +## How Can I Create Reports? -## How can I create reports? +Data can be exported in Excel or CSV format by downloading current data from the following locations: -Data can be exported in excel or csv format using: +- **Reports > Reports > Add Report** +- **Reports > Generate Run Book** +- **Tools > Exports (CSV)** +- **Tools -> Imports/Exports** -- Reports > Reports > Add Report. -- Reports > Generate Run Book -- Tools > Exports (CSV) -- Tools -> Imports/Exports to download current data. +## How Do I Back Up My Data? -## How do I backup my data? +Log in to the Device42 appliance manager at `https://your\_device42\_ip\_or\_FQDN:4242/` using the following default credentials: -Device42 appliance manager runs at https://your\_device42\_ip\_or\_FQDN:4242/ Default username password is d42admin/default You can create backup from Backup/Restore > Backup now. +- Username:`d42admin` +- Password: `default` -This is also discussed under section : [appliance manager.](/administration/appliance-manager/) +Create a backup from **Backup/Restore > Backup now**. -## How do I update to the latest release? +This is also discussed on the [Appliance Manager](/administration/appliance-manager/) page. -1. Download the latest release update file from [Device42 update page](https://www.device42.com/update/) -2. From the D42 main menu: _Tools > Update;_ Click _"Link to Appliance Manager"_, then browse to the downloaded update file ; Click "Upload". -3. Choose Option #3 on the Main Appliance's VM console to apply the update; follow the on-screen prompts. +## How Do I Update to the Latest Release? -This is also detailed on the support portal: [D42 Upgrade steps.](https://support.device42.com/hc/en-usentries/21783332) +1. Download the latest release update file from the Device42 [Update](https://www.device42.com/update/) page. +2. From the Device42 main menu, navigate to **Tools > Update**, click **Link to Appliance Manage**, browse to the downloaded update file, and click **Upload**. +3. Choose **Option 3** on the Main Appliance (MA) virtual machine (VM) console to apply the update, and follow the on-screen prompts. -For more information about Main Appliance and Remote Collector updates, see the  [Main Appliance and Remote Collector](/administration/appliance-manager/) page. +The [Device42 Upgrade Steps](https://support.device42.com/hc/en-us/articles/222221228-Upgrade-Steps-Device42) are also detailed on our Support Portal. -You can subscribe to the [Device42 Blog rss feed](https://www.device42.com/blog/feed/) or follow us on [twitter](https://twitter.com/device42) to get immediate notifications for new releases. +Learn more about MA and RC updates on the [Appliance Manager](/administration/appliance-manager/) page. -## How do I Install Device42 xen/kvm appliance if import existing disk image option is missing? +You can subscribe to the [Device42 Blog RSS feed](https://www.device42.com/blog/feed/) or follow us on [X](https://x.com/device42) to get immediate notifications for new releases. -If you are trying to install the Device42 appliance on Xen or KVM based platforms, but the import disk image option is missing, see our page [Installing Device42 Appliance but Import to disk is missing](/getstarted/installation/how-do-i-install-device42-xenkvm-appliance-if-import-existing-disk-image-option-is-missing/) +## How Do I Install the Device42 Appliance on Xen/KVM if the Import Existing Disk Image Option Is Missing? -## Where can I get help with something not covered here? +If you are trying to install the Device42 appliance on Xen- or KVM-based platforms but the **Import Disk Image** option is missing, follow the instructions on our [Import Disk Alternate Install](/getstarted/installation/how-do-i-install-device42-xenkvm-appliance-if-import-existing-disk-image-option-is-missing/) page. -We always recommend searching the [Device42 support portal](https://support.device42.com/hc/en-us) when faced with a question that doesn't seem to be addressed in our documentation. That said, if you do find one, or get stuck, go ahead and open a support ticket. Send a note to support@device42.com or visit the 'support' tab at the top of this page. +## Where Can I Get Help With Something Not Covered Here? +We always recommend searching the [Device42 Support Portal](https://support.device42.com/hc/en-us) when faced with a question that doesn't seem to be addressed in our documentation. That said, if you cannot find a solution or get stuck, please open a support ticket by sending a note to [support@device42.com](mailto:support@device42.com) or visiting the **Support** tab at the top of this page. diff --git a/docs/getstarted/index.md b/docs/getstarted/index.md index d76a4c93..98ec064e 100644 --- a/docs/getstarted/index.md +++ b/docs/getstarted/index.md @@ -3,18 +3,20 @@ title: "The Hitchhiker's Guide to Device42" sidebar_postion: 1 --- -Welcome to _"The Hitchhiker's Guide to Device42"_, AKA the Device42 Docs site. The following pages contain answers to the ultimate questions about infrastructure, the data-center, and everything _(and of course, answers to many common Device42 questions, as well)_. +Welcome to **The Hitchhiker's Guide to Device42**, AKA the Device42 docs site. -**Navigate through the D42 documentation topics using either the navigation bar to your left, and/or search for help using the search box found hanging out at the top right of the page - _much in the same way that bricks don't._** +The following pages contain answers to the ultimate questions about infrastructure, the data center, and everything _(and the answers to many common Device42 questions, too)_. + +**Navigate through the Device42 documentation topics using the left-hand navigation bar or the search box found hanging out at the top right of the page - _much the same way that bricks don't_.** * * * ## What is Device42? -Device42 is a comprehensive IT infrastructure management software suite with powerful agentless autodiscovery and application dependency mapping tools, a configuration management database (CMDB), a complete data center infrastructure management (DCIM) suite, full IT asset & inventory management (ITAM) functionality, plus IP address management (IPAM), password management and lots more -- all _in a single tool_. +Device42 is a comprehensive IT infrastructure management software suite with powerful, agentless autodiscovery and application dependency mapping tools, a configuration management database (CMDB), a complete data center infrastructure management (DCIM) suite, full IT asset and inventory management (ITAM) functionality, plus IP address management (IPAM), password management and lots more - all in a single tool. * * * -If you aren't able to find an answer to your question in the menu or using search, click  [here](https://support.device42.com) to open a support ticket. If you'd prefer, send us a note at [support@device42.com](mailto:support@device42.com). Our support team _loves_ hearing from customers, and are all especially fond of a good challenge! +If you don't find an answer to your question in the menu or using search, click  [here](https://support.device42.com) to open a support ticket or send us a note at [support@device42.com](mailto:support@device42.com). Our support team _loves_ hearing from customers, and they're all especially fond of a good challenge! diff --git a/docs/getstarted/installation/resource-and-deployment-architecture-overview.md b/docs/getstarted/installation/resource-and-deployment-architecture-overview.md index af28be11..099ca50a 100644 --- a/docs/getstarted/installation/resource-and-deployment-architecture-overview.md +++ b/docs/getstarted/installation/resource-and-deployment-architecture-overview.md @@ -6,35 +6,32 @@ Learn about the Device42 core resources and how they fit into our deployment arc ## Device42 Resources -**Main Appliance:** The Device42 Main Appliance is the kick off point for all the discovery -and insights that will proliferate through your environment. It is a pre-configured virtual -appliance (built on Linux) that is hosted by the end customer, enabling full protection under the -client’s data center security architecture and policies. +### Main Appliance -Device42 operates with only 5 ports open to the virtual appliance: -- Port 80: redirects to 443 -- Port 443: web (HTTPS) -- Port 4242: redirects to 4343 -- Port 4343: appliance manager (HTTPS) -- Port 404: SSH for limited console menu operations +The Device42 Main Appliance (MA) is the kick-off point for all the discovery and insights that will proliferate through your environment. It is a preconfigured virtual appliance (built on Linux) hosted by the end customer, enabling full protection under the client’s data center security architecture and policies. -**Remote Collector:** The Remote Collector (RC), is a much lighter pre-configured virtual -appliance (built on Linux), used to perform agentless discovery across network segments. It -also provides scalability by offloading discovery workloads from the MA. We require that you -install at least 1 RC with any deployment of Device42. +Device42 operates with only five ports open to the virtual appliance: -**Windows Discovery Service:** The Windows Discovery Service (WDS) is a .net service which -runs on a Windows system and makes WMI queries on behalf of the Linux-based RC and MA. If -you’ll be running Windows discoveries, you will need to deploy at least 1 WDS instance and -connect it to an RC. +- **Port 80:** Redirects to port 443 +- **Port 443:** Web (HTTPS) +- **Port 4242:** Redirects to port 4343 +- **Port 4343:** Appliance manager (HTTPS) +- **Port 404:** SSH for limited console menu operations -## Deployment Architecture +### Remote Collector -Device42 deployment architecture is similar to a hub and spoke model, with each RC/WDS -collecting data and syncing back to the centralized MA. It is typically recommended for RCs -and WDS instances to be deployed in pairs, if Windows discovery is required. +The Remote Collector (RC) is a much lighter preconfigured virtual appliance (built on Linux) used to perform agentless discovery across network segments. It also provides scalability by offloading discovery workloads from the MA. We require you to install at least one RC with any deployment of Device42. -Device42 Deployment Example: Segmented Network +### Windows Discovery Service -![](/assets/images/deployment-architecture.png) +The Windows Discovery Service (WDS) is a `.net` service that runs on a Windows system and makes WMI queries on behalf of the Linux-based RC and MA. If you’ll be running Windows discoveries, you will need to deploy at least one WDS instance and connect it to an RC. + +## Deployment Architecture + +Device42 deployment architecture is similar to a hub-and-spoke model, with each RC/WDS collecting data and syncing back to the centralized MA. It is typically recommended that RCs and WDS instances are deployed in pairs if Windows discovery is required. +### Device42 Deployment Example + +The following image illustrates the segmented network structure used for Device42 deployments. + +![](/assets/images/deployment-architecture.png) diff --git a/docs/getstarted/installation/security-posture-and-high-level-permissions.md b/docs/getstarted/installation/security-posture-and-high-level-permissions.md index 0a3424de..34997cd8 100644 --- a/docs/getstarted/installation/security-posture-and-high-level-permissions.md +++ b/docs/getstarted/installation/security-posture-and-high-level-permissions.md @@ -7,10 +7,12 @@ The section outlines how Device42 ensures data security in transit and at rest, ## Security Posture -- All data in transit from WDS to RC and RC to MA is over SSL or HTTPS. +- All data in transit from Windows Discovery Service (WDS) to Remote Collector (RC), and RC to Main Appliance (MA) is transferred via Secure Sockets Layer (SSL) or HTTPS. - All data stays at rest within the MA in an end-user environment. - Only data voluntarily shared by the end user leaves the premises. ## Required Permissions -Device42 uses the principle of least privilege in it’s agentless discovery. For a detailed overview of permissions, please reference our Pre-requisites guide or please see the discovery section on our website and locate the relevant jobs for clarity on required permissions. \ No newline at end of file +Device42 uses the principle of least privilege in its agentless discovery. + +For a detailed overview of permissions, please reference our prerequisites guide or use the **Discovery** section on our website to locate the relevant jobs and view their required permissions. diff --git a/static/assets/images/advanced-routing/1-network.png b/static/assets/images/advanced-routing/1-network.png new file mode 100644 index 00000000..18e28d15 Binary files /dev/null and b/static/assets/images/advanced-routing/1-network.png differ diff --git a/static/assets/images/advanced-routing/2-routing.png b/static/assets/images/advanced-routing/2-routing.png new file mode 100644 index 00000000..c4c5e7c1 Binary files /dev/null and b/static/assets/images/advanced-routing/2-routing.png differ diff --git a/static/assets/images/advanced-routing/3-route-options.png b/static/assets/images/advanced-routing/3-route-options.png new file mode 100644 index 00000000..cd542dd7 Binary files /dev/null and b/static/assets/images/advanced-routing/3-route-options.png differ diff --git a/static/assets/images/advanced-routing/4-route-details.png b/static/assets/images/advanced-routing/4-route-details.png new file mode 100644 index 00000000..8390ec75 Binary files /dev/null and b/static/assets/images/advanced-routing/4-route-details.png differ diff --git a/static/assets/images/advanced-routing/console-advanced-routing-option.png b/static/assets/images/advanced-routing/console-advanced-routing-option.png deleted file mode 100644 index 0506b79f..00000000 Binary files a/static/assets/images/advanced-routing/console-advanced-routing-option.png and /dev/null differ diff --git a/static/assets/images/advanced-routing/console-routing-submenu.png b/static/assets/images/advanced-routing/console-routing-submenu.png deleted file mode 100644 index efd800ca..00000000 Binary files a/static/assets/images/advanced-routing/console-routing-submenu.png and /dev/null differ