Unsolved
This post is more than 5 years old
19 Posts
0
4057
January 29th, 2013 06:00
ISL creation across DWDM link
I need a sanity check for the following process to create ISLs for a dedicated cross-site replication VSAN. I have to provide a process to the implementation guys, but do not have access to test switches to test the process. I really appreciate it if you could cast your eye over this, and let me know whether it's correct or not. Here are the key facts:
- MDS9513's
- ports are on 24-port 8G line card, and the only members of the replication VSAN (once the replicaiton devices are in place they will also be members)
- to be connected over a 4G DWDM link
- only dedicated replicaiton VSAN to merge
- ISL to carry dedciated replication VSAN traffic only, so trunking off for these ports
- configure trunk allow list in case trunking gets turned back on for these port
- VSAN1 must NOT merge - it is being used for host attach (this is will cleared out, but not before the ISL is created across sites)
1. Create dedicated replication VSAN on each switch;
2. Ensure the Domain ID for each switch & VSAN are unique;
3. Ensure the ISL port is admin down, and then modify settings in following order:
- Change VSAN to the Replication VSAN;
- Change port mode to E;
- Change trunk allowlist to include the Replication VSAN only;
- Disable trunking; (is the allowlist persistent? will it exist is trunking was to be enable again?)
- Change rate-mode from shared to dedicated;
- Change speed from auto to 4000;
- Add description
4. Cable switches to DWDM mux;
5. Bring the ports online;
6. Check interfaces for errors
7. Check for VSAN merge errors
0 events found

