Adding to Ben's response:

Switch migration can be addressed within SANscreen in two ways:

1. The switch migration functionality allows you to define what switches are going to be replaced / migrated and assist you with finding the pre-migration conditions and make sure that post migration you will end up with the same paths and service level (e.g. redundancy) as before

2. More tactically - using the planning functionality you can simulate disconnect and conenct of switches. This will simulate the formation of a new fabric. If the switches have identical zones, the connection would be succesfull. If they are different (but not empty), the connection would fail and the fabric would not form.

Having said that - per Ben's comments, this may be a good opportunity to discuss PS (especially if this is a one-off).

Hope that helps.

Gadi

Eran,

In the plan, the connect action has an error. Did you check what is the error (in the error microview)? It is possible that you get information about why the connection can't be complete. Without this action completing you do not have a new fabric with the new connected switch. Are you sure that all zones are identical between the two switches prior to the connection?

Also, use the analyze violation on the future path outage violations. Look at the future changes (Violation change root-cause) and look for fabric configuration hnage events. If that doesn't provide you with an answer let me know - I may have to look at the DB.

-G