From 0c8cf5d60c0c6fab6210d1660bf3d97e9f2f75c7 Mon Sep 17 00:00:00 2001 From: Lynn Chiang Date: Thu, 1 Aug 2024 13:20:06 -0700 Subject: [PATCH] updating content to reflect EOS --- products/expedition/docs/expedition.md | 6 +++- products/expedition/docs/expedition_apiInt.md | 6 +++- .../expedition/docs/expedition_contact.md | 3 +- products/expedition/docs/expedition_export.md | 24 ++++++++++------ products/expedition/docs/expedition_qs.md | 8 ++++-- .../docs/expedition_workflow_bulkchange.md | 22 +++++++-------- .../docs/expedition_workflow_filters.md | 20 ++++++------- .../docs/expedition_workflow_migration.md | 14 +++++----- .../expedition_workflow_removeunusedobject.md | 22 +++++++-------- .../docs/expedition_workflow_searchrule.md | 28 +++++++++---------- products/expedition/docs/workflow.mdx | 28 +++++++++---------- 11 files changed, 100 insertions(+), 81 deletions(-) diff --git a/products/expedition/docs/expedition.md b/products/expedition/docs/expedition.md index b16f04c90..086ea789c 100644 --- a/products/expedition/docs/expedition.md +++ b/products/expedition/docs/expedition.md @@ -18,7 +18,11 @@ image: /expedition/img/expedition.png --- :::note -Expedition 1.x is the only supported version at time. Learn more about the release at our [Live Community](https://live.paloaltonetworks.com/t5/expedition/ct-p/migration_tool) site. +**End of Life Announcement for Palo Alto Networks Expedition** + +We are excited to share some great news with you, as a valued user of Expedition functionalities. We are currently in the process of transferring the core functionalities of the tool into new products. This strategic move aligns with our commitment to meet the evolving needs of our customers and enhance our range of product offerings. + +Starting from January 2025, Palo Alto Networks will no longer support the Expedition tool, including all versions of both Expedition1 and Expedition2 branches. We believe this transition will bring even more value and improved capabilities to our users. For more details, please refer to [Live Community](https://live.paloaltonetworks.com/t5/expedition-articles/important-update-end-of-life-announcement-for-palo-alto-networks/ta-p/589642) site. ::: ## What is Expedition? diff --git a/products/expedition/docs/expedition_apiInt.md b/products/expedition/docs/expedition_apiInt.md index 64e9e90ed..19a54b920 100644 --- a/products/expedition/docs/expedition_apiInt.md +++ b/products/expedition/docs/expedition_apiInt.md @@ -19,7 +19,11 @@ image: /expedition/img/expedition.png --- :::note -Expedition 1.x is the only supported version at time. Learn more about the release at our [Live Community](https://live.paloaltonetworks.com/t5/expedition-articles/expedition-2-0-release-date-postponed/ta-p/423747) site. +**End of Life Announcement for Palo Alto Networks Expedition** + +We are excited to share some great news with you, as a valued user of Expedition functionalities. We are currently in the process of transferring the core functionalities of the tool into new products. This strategic move aligns with our commitment to meet the evolving needs of our customers and enhance our range of product offerings. + +Starting from January 2025, Palo Alto Networks will no longer support the Expedition tool, including all versions of both Expedition1 and Expedition2 branches. We believe this transition will bring even more value and improved capabilities to our users. For more details, please refer to [Live Community](https://live.paloaltonetworks.com/t5/expedition-articles/important-update-end-of-life-announcement-for-palo-alto-networks/ta-p/589642) site. ::: ## Introduction diff --git a/products/expedition/docs/expedition_contact.md b/products/expedition/docs/expedition_contact.md index 4972a9d5c..7b60945d5 100644 --- a/products/expedition/docs/expedition_contact.md +++ b/products/expedition/docs/expedition_contact.md @@ -30,8 +30,7 @@ To report bugs, requests for new features or personal contact, please reach us v | Role | Members | e-mail | | ------------------------------------------------- | --------------------------------- | -------------------------------------------------- | | Senior Manager Solutions Architect | David Puigdomenech | | -| Architecture and Analytics | Didac Gil | | | API development | Anna Carreras | | -| Solution Architect | Sathesh Anandh | | | Front-End development | Janosch Zbick | | +| Solution Engineer | Carles Costas | | | Technical Solution Architect | Lynn Chiang | | diff --git a/products/expedition/docs/expedition_export.md b/products/expedition/docs/expedition_export.md index 3fb05f3e9..aec842af6 100644 --- a/products/expedition/docs/expedition_export.md +++ b/products/expedition/docs/expedition_export.md @@ -268,16 +268,24 @@ The configuration is exported as a **.txt** file and is readable using any text ## SonicWall -Issue below commands in CLI: +In collaboration with the Expedition Team, Migration Factory team has committed to redesigning all the converters present in the Expedition2 tool with the goal of pushing their capabilities further and increasing maintainability. The team also develops a tool called **PANser**, a parser for PAN-OS configuration files that is designed to be flexible and extensible, making it a valuable tool for a wide range of use cases. -```bash -no cli pager session -show current-config -``` +By using PANser as an external parser on your Expedition2 environment, you can enhance the number and variety of 3rd party parsers. + +Please fulfil and follow instructions on the form to download the **PANser docker image** + +For more details, please reach out to the Migration Factory team at +pso-migration-factory@paloaltonetworks.com + +To export the configuration of a SonicWall firewall, you can follow these general steps: + +1. Log in to the SonicWall firewall management interface using a web browser. +2. Navigate to the "System" or "Administration" section of the interface. +3. Look for an option like "Export Settings" or "Backup Configuration." +4. Select the option to export the configuration. +5. Choose a location to save the configuration file on your local machine. +6. Save the configuration file with a **.EXP** format. -:::note -The configuration is exported as a **.txt** file, **.EXP** format is not supported. -::: ## Forcepoint diff --git a/products/expedition/docs/expedition_qs.md b/products/expedition/docs/expedition_qs.md index 095c4d3ce..2ab7957df 100644 --- a/products/expedition/docs/expedition_qs.md +++ b/products/expedition/docs/expedition_qs.md @@ -18,12 +18,16 @@ image: /expedition/img/expedition.png --- :::note -Expedition 1.x is the only supported version at time. Learn more about the release at our [Live Community](https://live.paloaltonetworks.com/t5/expedition/ct-p/migration_tool) site. +**End of Life Announcement for Palo Alto Networks Expedition** + +We are excited to share some great news with you, as a valued user of Expedition functionalities. We are currently in the process of transferring the core functionalities of the tool into new products. This strategic move aligns with our commitment to meet the evolving needs of our customers and enhance our range of product offerings. + +Starting from January 2025, Palo Alto Networks will no longer support the Expedition tool, including all versions of both Expedition1 and Expedition2 branches. We believe this transition will bring even more value and improved capabilities to our users. For more details, please refer to [Live Community](https://live.paloaltonetworks.com/t5/expedition-articles/important-update-end-of-life-announcement-for-palo-alto-networks/ta-p/589642) site. ::: ## Install Expedition -Expedition 2.0 is in constant development to cover new functionalities available in the market and to correct implementation issues that are identified in the code. Installation steps will be published when the tool is ready for testing. +Expedition 2.0 is in constant development to cover new functionalities available in the market and to correct implementation issues that are identified in the code. Installation steps are stated in the readme of Expedition2-release Beta drive. :::note The installation process does not support migrating Expedition 1 instances to Expedition 2.0 diff --git a/products/expedition/docs/expedition_workflow_bulkchange.md b/products/expedition/docs/expedition_workflow_bulkchange.md index badd22068..5aab1a4de 100644 --- a/products/expedition/docs/expedition_workflow_bulkchange.md +++ b/products/expedition/docs/expedition_workflow_bulkchange.md @@ -90,7 +90,7 @@ API syntax for creating a new device : ::: -`https://localhost/api/v1/project` | _in url_
{ **"project"**:"project1", **"description"**:"Project for testing" } | | example | `https://localhost/api/v1/project` | {"project":"MyLittleProject", "description":"A migration project"} | -"https://localhost/api/v1/device/{device_id}/upload_config" | **"device_id"**: device_Id | | Example | "https://localhost/api/v1/device/23/upload_config" | | -`https://localhost/api/v1/project/{project_id}/import/device` | _in url_
**"project_id"**:project_Id
in_body
{**"device_id"**:device_Id } | | example | `https://localhost/api/v1/project/22/import/device` | {"device_id":"23""} | -`https://localhost/api/v1/project/{project_id}/source` | _in url_
**"project_id"**:project_Id
in_body
{**"device_id"**:device_Id} | | example | `https://localhost/api/v1/project/22/source` | {**"device_id"**: 23} | -`https://localhost/api/v1/project/{project_id}/tools/filter` | _in url_
**"project_id"**:project_Id
in_body
{**"name"**:filter_name,**"filter"**:filter, **"reference"**:filter_reference,**"source"**:sourceId, } | | example | `https://localhost/api/v1/project/22/tools/filter` | {**"name"**: "all allowed rules", **"filter"** : "[security_rule] action equals \"allow\"",**"reference"**: "all allowed rules", **"source"** :4486 } | -`https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}/execute` | _in url_
**"project_id"**:project_Id, **"filter_id"**:filter_Id
in_body
{**"source_id"**: source_id of the PAN-OS config file} | | example | `https://localhost/api/v1/project/22/tools/filter/1/execute` | {**"source_id"**: "23564"} | -`https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}/success` | _in url_
**"project_id"**:project_Id, **"filter_id"**:filter_Id | | example | `https://localhost/api/v1/project/22/tools/filter/1/success` | | -`https://localhost/api/v1/project/{project_id}/collection/{Collection_Id}/content` | _in url_
**"project_id"**:project_Id, **"collection_id"**:collection_Id | | example | `https://localhost/api/v1/project/22/collection/20793/content` | | -`https://localhost/api/v1/project/{project_id}/object/profile_group` | _in url_
**"project_id"**:project_Id | | example | `https://localhost/api/v1/project/22/object/profile_group` | | -`https://localhost/api/v1/project/{project_id}/policy/security` | _in url_
**"project_id"**:project_Id
in_body
{**"add[profile][0]"**: object_id of the SPG, **"id"**: collection_id} | | example | `https://localhost/api/v1/project/22/policy/security` | {**"add[profile][0]"**: "11714", **"id"**:"20793"} | -`https://localhost/api/v1/project/{project_id}/tools/filter` | name, filter | {**"name"**:"filter_name", **"filter"**:**"[address, address_group] name contains \"office\""}** | -`https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}` | name, filter | {**"name"**:"filter_name", **"filter"**:**"[address, address_group] name contains \"office\""}** | -`https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}` | {project_id}, {filter_id} | `https://localhost/api/v1/project/48/tools/filter/22` | - +}> ```python @@ -424,11 +424,11 @@ The successful Json response will be similar to the following: | ------ | --------------------------------------------------------------------------------------- | ---------------------------------------- | -------------------------------------------------------------------- | | GET | `https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}` | {project_id}, {filter_id} | `https://localhost/api/v1/project/48/tools/filter/23/success` | - +}> ```python @@ -485,11 +485,11 @@ The successful Json response will be similar to the following: | ------ | ---------------------------------------------------------------------------- | --------------------------- | ----------------------------------------------------------------- | | GET | `https://localhost/api/v1/project/{project_id}/tools/filter/` | {project_id} | `https://localhost/api/v1/project/48/tools/filter` | - +}> ```python @@ -550,7 +550,7 @@ The successful Json response will be similar to the following: | ------ | ----------------------------------------------------------------------------------------------- | ---------------------------------------- | ---------------------------------------------------------------------------- | | POST | `https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}/execute` | {project_id}, {filter_id} | `https://localhost/api/v1/project/48/tools/filter/23/execute` | -`https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}/history` | {project_id}, {filter_id} | `https://localhost/api/v1/project/48/tools/filter/23/history` | -`https://localhost/api/v1/project` | _in url_
{ **"project"**:Name of the project, **"description"**:Description of the project } | | example | `https://localhost/api/v1/project` | {"project":"MyLittleProject", "description":"A migration project"} | -`https://localhost/api/v1/project/{project_id}/migration` | _in url_
**"project_id"**:"ProjectId"
in_body
{**"device_type"**:"panorama or firewall" } | | example | `https://localhost/api/v1/project/22/migration` | {"device_type":"panorama"} | -`https://localhost/api/v1/project/{project_id}/migration/{migration_Id}/resource/{resource_Id}/discover` | _in url_
**"project_id"**:projectId
**"migration_id"**:migrationId
**"resource_id"**:resourceId
 | | example | `https://localhost/api/v1/project/22/migration/25/resource/35/discovery` | _in url_
**"project_Id"**: 22,
**"migration_id"**: 25,
**"resource_id"**: 35 | -`https://localhost/api/v1/project/22/migration/25/resource/35/map` | _in url_
**"project_Id"**: 22,
**"migration_id"**: 25,
**"resource_id"**: 35 | -`https://localhost/api/v1/project/{project_id}/migration/{migration_Id}/convert` | _in url_
**"project_id"**:projectId
**"migration_id"**:migrationId | | example | `https://localhost/api/v1/project/22/migration/25/convert` | _in url_
**"project_Id"**: 22,
**"migration_id"**: 25 | -`https://localhost/api/v1/project/{project_id}/import/device` | _in url_
**"project"**: "projectID"

_in body_
{ **"device_id"**: "deviceId" } | | example | `https://localhost/api/v1/project/22/import/device` | _in url_
project=22

_in body_
{ "device_id": "23" } | -`https://localhost/api/v1/project` | _in url_
{ **"project"**:"project1", **"description"**:"Project for testing" } | | example | `https://localhost/api/v1/project` | {"project":"MyLittleProject", "description":"A migration project"} | -"https://localhost/api/v1/device/{device_id}/upload_config" | **"device_id"**: device_Id | | Example | "https://localhost/api/v1/device/23/upload_config" | | -`https://localhost/api/v1/project/{project_id}/import/device` | _in url_
**"project_id"**:project_Id
in_body
{**"device_id"**:device_Id } | | example | `https://localhost/api/v1/project/22/import/device` | {"device_id":"23""} | -`https://localhost/api/v1/project/{project_id}/source` | _in url_
**"project_id"**:project_Id
in_body
{**"device_id"**:device_Id} | | example | `https://localhost/api/v1/project/22/source` | {**"device_id"**: 23} | -`https://localhost/api/v1/project/{project_id}/tools/filter/generate_predefined` | _in url_
**"project_id"**:project_Id
in_body
{**"type"**:filter_type,**"source"**:sourceId} | | example | `https://localhost/api/v1/project/22/tools/filter/generate_predefined` | {**"type"**: "basic", **"source"** : sourceId} | -`https://localhost/api/v1/project/{project_id}/tools/filter?type={filter_type}&query={string to search}` | _in url_
**"project_id"**:project_Id, **"type"**:filter_type,**"query"**:string to search | | example | `https://localhost/api/v1/project/22/tools/filter?type=predefined&query=unused%20objects` | | -`https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}/execute` | _in url_
**"project_id"**:project_Id, **"filter_id"**:FILTER_ID | | example | `https://localhost/api/v1/project/22/tools/filter/1/execute` | | -`https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}/success` | _in url_
**"project_id"**:project_Id, **"filter_id"**:filter_Id | | example | `https://localhost/api/v1/project/22/tools/filter/1/success` | | -`https://localhost/api/v1/project/{project_id}/collection/{Collection_Id}/content` | _in url_
**"project_id"**:project_Id, **"collection_id"**:collection_Id | | example | `https://localhost/api/v1/project/22/collection/20793/content` | | -`https://localhost/api/v1/project/{project_id}/collection/{collection_id}/content` | _in url_
**"project_id"**:project_Id, **"collection_id"**:collection_Id | | example | `https://localhost/api/v1/project/22/collection/20793/content` | | -`https://localhost/api/v1/project` | _in url_
{ **"project"**:"project1", **"description"**:"Project for testing" } | | example | `https://localhost/api/v1/project` | {"project":"MyLittleProject", "description":"A migration project"} | -"https://localhost/api/v1/device/{device_id}/upload_config" | **"device_id"**: device_Id | | Example | "https://localhost/api/v1/device/23/upload_config" | | -`https://localhost/api/v1/project/{project_id}/import/device` | _in url_
**"project_id"**:project_Id
in_body
{**"device_id"**:device_Id } | | example | `https://localhost/api/v1/project/22/import/device` | {"device_id":"23""} | -`https://localhost/api/v1/project/{project_id}/source` | _in url_
**"project_id"**:project_Id
in_body
{**"device_id"**:device_Id} | | example | `https://localhost/api/v1/project/22/source` | {**"device_id"**: 23} | -`https://localhost/api/v1/project/{project_id}/tools/filter` | _in url_
**"project_id"**:project_Id
in_body
{**"name"**:filter_name,**"filter"**:filter, **"reference"**:filter_reference,**"source"**:sourceId} | | example | `https://localhost/api/v1/project/22/tools/filter` | {**"name"**: "all allowed rules", **"filter"** : "[address] ipaddress contains \"10.1\"",**"reference"**: "all allowed rules", **"source"** :4486} | -filter** filter_name1.success **or** **filter** filter_name2.success -`https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}/execute` | _in url_
**"project_id"**:project_Id, **"filter_id"**:filter_Id
in_body
{**"source_id"**: source_id of the PAN-OS config file} | | example | `https://localhost/api/v1/project/22/tools/filter/6/execute` | {**"source_id"**: "23564"} | -`https://localhost/api/v1/project/{project_id}/tools/filter/{filter_id}/success` | _in url_
**"project_id"**:project_Id, **"filter_id"**:filter_Id | | example | `https://localhost/api/v1/project/22/tools/filter/6/success` | | -`https://localhost/api/v1/project/{project_id}/collection/{Collection_Id}/content` | _in url_
**"project_id"**:project_Id, **"collection_id"**:collection_Id | | example | `https://localhost/api/v1/project/22/collection/20793/content` | | -/api/v1/login` | | { **"username"** : "admin" , **"password"** : "paloalto" } | -/api/v1/projects` | | { **"project"**: "project1", **"description"**: "Project for testing" } | -/api/v1/projects/{projectId}/importConfig`

With sample template value **"project"**: "1"

The full API EndPoint will become:

`https:///api/v1/projects/1/importConfig` | **"project"**: "$projectID" | {**"config"**: "/tmp/cisco.xml" } | - +}> ```python @@ -375,7 +375,7 @@ API syntax for adding a PAN-OS device into the project: The API response will provide us an internal Expedition identificator for the newly generated device. - +}> ```python @@ -654,7 +654,7 @@ API syntax for attach device to the Expedition project: In the snippet below, we show how the device created above which id we prior stored in the **$deviceId** variable, is attached to the newly created project. This call is making a modification on the project settings, therefore we are sending a PUT request to the project route. -/api/v1/projects/{projectId}/export` | {**"projectId"**:"$projectId"}

With sample parameter value: **{projectID}**:"1"

API EndPoint Full path will become:

_`https:///api/v1/projects/1/export`_ | {**"out:"**-> PAN-OS configuration file ,

**"sourceID:"**-> you can get the source id with the sources given in the previous api call
} | - +}>