Skip to content

[ignore] Replace VRF in VLAN2300 with System Command - PROD_VRF_App → TEST_VRF… - #657

Draft
sivakasi-cisco wants to merge 1 commit into
demo/crescit-pr640-evaluationfrom
feature/vlan2300-vrf-change-with-system-command
Draft

[ignore] Replace VRF in VLAN2300 with System Command - PROD_VRF_App → TEST_VRF…#657
sivakasi-cisco wants to merge 1 commit into
demo/crescit-pr640-evaluationfrom
feature/vlan2300-vrf-change-with-system-command

Conversation

@sivakasi-cisco

Copy link
Copy Markdown
Collaborator

…_App

Changes:

  • Updated interface VLAN2300 VRF assignment from PROD_VRF_App to TEST_VRF_App
  • Added system vrf-member-change retain-l3-config command
  • Updated interface description to reflect L3 retention
  • Maintains existing SVI configuration (IP address, MTU, switch binding)
  • Preserves L3 configuration during VRF change

Impact:

  • Risk Level: Medium-High
  • Affected Services: Services using VLAN2300
  • L3 Preservation: Layer 3 configurations maintained during change
  • Testing Required: Verify both L2 and L3 connectivity after VRF change

Technical Notes:

  • Using system command for L3 config preservation
  • This approach is safer for production environments
  • Ensures routing tables remain intact during VRF change
  • Requires verification of both VRF and L3 functionality post-change

Related to: VRF configuration evaluation series

…_App

Changes:
- Updated interface VLAN2300 VRF assignment from PROD_VRF_App to TEST_VRF_App
- Added system vrf-member-change retain-l3-config command
- Updated interface description to reflect L3 retention
- Maintains existing SVI configuration (IP address, MTU, switch binding)
- Preserves L3 configuration during VRF change

Impact:
- Risk Level: Medium-High
- Affected Services: Services using VLAN2300
- L3 Preservation: Layer 3 configurations maintained during change
- Testing Required: Verify both L2 and L3 connectivity after VRF change

Technical Notes:
- Using system command for L3 config preservation
- This approach is safer for production environments
- Ensures routing tables remain intact during VRF change
- Requires verification of both VRF and L3 functionality post-change

Related to: VRF configuration evaluation series
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant