ise2.7升级3.3,因3.3需要重新部署2.7的配置能入导入到3.3

[angel9999]

ise2.7升级3.3,因3.3需要重新部署2.7的配置能入导入到3.3

如果可以步骤如何导入导出

[ilay · Accepted solution]

如果不是使用upgrade的包一步一步升上去，那么2.7的配置是没有办法直接恢复到3.3版本的。会出现备份的版本比支持的版本低的一个错误（见下图）

从ise的软件上来看，从2.7最高可以直接升到3.2版本，2.7不能直升3.3； 3.x的任意版本可以直接升级3.3。如果像你描述的那样需要直接安装3.3，那么只能对照这2.7的配置手动搞一下了，或者将2.7的配置恢复到3.0-3.2的设备上试试，如果成功再进行一次导出导入操作

如果ise有正式的许可服务，建议直接开case进行处理，tac会给一个更为详尽的解决方案。

[angel9999]

目前3.3虚拟机版本支持快照和恢复了吗，3.1v2v3版本功能对比哪里有看

[ilay]

When Cisco ISE is run on VMware, VMware snapshots are not supported for backing up ISE data.

Note

Cisco ISE does not support VMware snapshots for backing up ISE data because a VMware snapshot saves the status of a VM at a given point in time. In a multinode Cisco ISE deployment, data in all the nodes are continuously synchronized with current database information. Restoring a snapshot might cause database replication and synchronization issues. Cisco recommends that you use the backup functionality included in Cisco ISE for archival and restoration of data. Using VMware snapshots or any third-party backup service to back up Cisco ISE data might result in interrupting Cisco ISE services. When a backup is initiated by VMware or any other third-party backup service like CommVault SAN level backup, it quiesces the file system to maintain crash consistency, which can cause your Cisco ISE functionalities to freeze. A reboot is required to resume the services on your Cisco ISE deployment.

https://www.cisco.com/c/en/us/td/docs/security/ise/3-3/admin_guide/b_ise_admin_3_3/b_ISE_admin_33_maintain_monitor.html?bookSearch=true#reference_4F69987D3294499E95C1B652C4D1E73D

ISE 3.x 思科仍旧不建议使用虚拟软件的快照和恢复功能。在多节点部署的情况会引发数据同步问题。生成快照的时候也有可能造成ISE crash，生产系统建议按照官方指导，使用backup的内置功能进行备份，测试用途随意

ISE 3.x个版本的功能可以查看对应版本的ReleaseNotes，对应的文档会介绍相应版本添加或者修改的功能或者feature

参考链接：https://www.cisco.com/c/en/us/support/security/identity-services-engine/products-release-notes-list.html