Using IPS Network Simulator and SAN Extension Tuner

MDS1(config)#fcip enableEnter configuration commands, one per line. End with CNTL/Z.MDS1(config)# int GigabitEthernet2/2MDS1(config-if)# ip address 192.168.10.1 255.255.255.0MDS1(config-if)# no shutMDS1(config-if)# exitMDS1(config)# exitMDS2(config)#fcip enableEnter configuration commands, one per line. End with CNTL/Z.MDS2(config)# int GigabitEthernet2/2MDS2(config-if)# ip address 192.168.10.2 255.255.255.0MDS2(config-if)# no shutMDS2(config-if)# exitMDS2(config)# exitConfiguration of FCIP interfaces Next, we will do a basic configuration of FCIP by creating a tunnel between MDS1 and MDS2. This tunnel will not come up as we have not yet established connectivity between ports GigabitEthernet2/2 on MDS1 and GigabitEthernet2/2 on MDS2. Once we configure the IPS Network Simulator the ports will be connected. We will use VSAN100 for our testing.

MDS1# conf tEnter configuration commands, one per line. End with CNTL/Z.MDS1(config)# fcip profile 1MDS1(config-profile)# ip address 192.168.10.1MDS1(config-profile)# exitMDS1(config)# exitMDS1(config)# int fcip1MDS1(config-if)# use-profile 1MDS1(config-if)# peer-info ipaddr 192.168.10.2MDS1(config-if)# switchport trunk allowed vsan 100MDS1(config-if)# exitMDS1(config)# exitMDS2# conf tEnter configuration commands, one per line. End with CNTL/Z.MDS2(config)# fcip profile 1MDS2(config-profile)# ip address 192.168.10.2MDS2(config-profile)# exitMDS2(config)# exitMDS2(config)# int fcip1MDS2(config-if)# use-profile 1MDS2(config-if)# peer-info ipaddr 192.168.10.1MDS2(config-if)# switchport trunk allowed vsan 100MDS2(config-if)# exitMDS2(config)# exitConfiguration of IPS Network Simulator The Gigabit Ethernet and FCIP configurations are mostly complete. We will add some additional parameters later, but enough has been configured for basic connectivity. Now we must configure the actual IPS Network Simulator. A few key points about the IPS Network Simulator first:

1. You must enable san-ext-tuner

2. Parameters are configured ingress and can be configured on either of the simulators two ports, one for each direction

3. IPS netsim configuration is not saved to NVRAM

MDS1(config)# san-ext-tuner enableMDS1# ips netsim enable interface g2/3 g2/4MDS1# ips netsim delay-ms 100 ingress g2/3MDS1# ips netsim delay-ms 100 ingress g2/4MDS1# ips netsim max-bandwidth-mbps 10 ingress g2/3MDS1# ips netsim max-bandwidth-mbps 10 ingress g2/4MDS1# ips netsim qsize 250 ingress g2/3MDS1# ips netsim qsize 250 ingress g2/4MDS1# ips netsim drop nth 200 burst 1 ingress g2/3 At this point the FCIP tunnels should be up and operational. Configuration of SAN Extension Tuner The SAN Extension Tuner allows us to generate traffic between two virtual endpoints. A few key points about SET configuration:

1. You must enable san-ext-tuner (we have already done this for IPS Network Simulator configuration)

2. You must enable iSCSI

3. You must create an arbitrary nWWN and pWWN for the endpoints to use for each side of the SET

4. You must zone the two virtual endpoints (easiest thing to do is just use zone default permit)

5. SET configuration is not saved to NVRAM

MDS1(config)# san-ext-tuner enableMDS1(config)# iscsi enableMDS1(config)# iscsi enable module 2MDS1(config)# zone default-zone permit vsan 100MDS1(config)# int iscsi 2/2MDS1(config-if)# no shutMDS1# san-ext-tunerMDS1(san-ext)# nwwn 10:00:00:00:00:00:00:00MDS1(san-ext)# nport pwwn 11:11:11:11:11:11:11:11 vsan 100 interface g2/2MDS1(san-ext-nport)# exitMDS1(san-ext)# exitMDS2(config)# san-ext-tuner enableMDS2(config)# iscsi enableMDS2(config)# iscsi enable module 2MDS2(config)# zone default-zone permit vsan 100MDS2(config)# int iscsi 2/2MDS2(config-if)# no shutMDS2# san-ext-tunerMDS2(san-ext)# nwwn 20:00:00:00:00:00:00:00MDS2(san-ext)# nport pwwn 22:22:22:22:22:22:22:22 vsan 100 interface g2/2MDS2(san-ext-nport)# exitMDS2(san-ext)# exitMDS1# show san-ext-tuner nports ----------------------------------------------------------------------------Interface NODE NAME PORT NAME VSAN----------------------------------------------------------------------------GigabitEthernet2/2 10:00:00:00:00:00:00:00 11:11:11:11:11:11:11:11 100MDS2# show san-ext-tuner nports ----------------------------------------------------------------------------Interface NODE NAME PORT NAME VSAN----------------------------------------------------------------------------GigabitEthernet2/2 20:00:00:00:00:00:00:00 22:22:22:22:22:22:22:22 100 At this point the SET is not really doing anything but its setup and in place for us to start generating some tests. You can test your connectivity by using fcping:

MDS1# fcping pwwn 22:22:22:22:22:22:22:22 vsan 10028 bytes from 22:22:22:22:22:22:22:22 time = 699973 usec28 bytes from 22:22:22:22:22:22:22:22 time = 335159 usec28 bytes from 22:22:22:22:22:22:22:22 time = 670161 usec28 bytes from 22:22:22:22:22:22:22:22 time = 201197 usec28 bytes from 22:22:22:22:22:22:22:22 time = 249109 usec5 frames sent, 5 frames received, 0 timeoutsRound-trip min/avg/max = 201197/431119/699973 usec Notice the ridiculously high ping time we get. This is because with IPS Network Simulator we have created 200ms of RTT, packet drops, manipulated the qsize and reduced the bandwidth to 1% (10Mbps) of the actual link speed. Lets generate some traffic:

MDS1# san-ext-tuner MDS1(san-ext)# nport pwwn 11:11:11:11:11:11:11:11 vsan 100 int g2/2MDS1(san-ext-nport)# read command-id 1 target 22:22:22:22:22:22:22:22 transfer-size 256000 outstanding-ios 2 continuousMDS2# san-ext-tuner MDS2(san-ext)# nport pwwn 22:22:22:22:22:22:22:22 vsan 100 int g2/2MDS2(san-ext-nport)# read command-id 1 target 11:11:11:11:11:11:11:11 transfer-size 256000 outstanding-ios 2 continuous We can view statistics from both IPS Network Simulator as well as SET:

MDS1# show san-ext-tuner interface g2/2 nport pwwN 11:11:11:11:11:11:11:11 vsan 100 counters Statistics for nportNode name 10:00:00:00:00:00:00:00 Port name 11:11:11:11:11:11:11:11 I/Os per sec : 5 Reads : 100% Writes : 0% Egress throughput : 0.75 MBs/sec (Max - 2.50 MBs/sec) Ingress throughput : 0.69 MBs/sec (Max - 2.50 MBs/sec) Average response time : Read - 279561 us, Write - 0 us Minimum response time : Read - 404 us, Write - 0 us Maximum response time : Read - 3112761 us, Write - 0 us Errors : 10MDS1# show ips stats netsim ingress g2/3 Network Simulator Configuration for Ingress on GigabitEthernet2/3 Delay : 100000 microseconds Rate : 10000 kbps Max_q : 250000 bytes Max_qdelay : 150000000 clocks Drop nth pkt : 200Network Simulator Statistics for Ingress on GigabitEthernet2/3 Dropped (tot) = 35875 Dropped (netsim) = 3592 Reordered (netsim) = 0 Max Qlen(pkt) = 542 Qlen (pkt) = 83 Max Qlen (byte) = 5602 Qlen (byte) = 0 Mintxdel(poll) = 39600 Mintxdel(ethtx) = 39600 empty = 233 txdel = 603235 late = 111330 Average speed = 1586 Kbps Now we will enable compression and see the effect is has on our traffic:

MDS1# conf tEnter configuration commands, one per line. End with CNTL/Z.MDS1(config)# int fcip1MDS1(config-if)# ip-compression mode3MDS1(config-if)# exitMDS1(config)# exitMDS2# conf tEnter configuration commands, one per line. End with CNTL/Z.MDS2(config)# int fcip1MDS2(config-if)# ip-compression mode3MDS2(config-if)# exitMDS2(config)# exitMDS1# show san-ext-tuner interface g2/2 nport pwwN 11:11:11:11:11:11:11:11 vsan 100 counters Statistics for nportNode name 10:00:00:00:00:00:00:00 Port name 11:11:11:11:11:11:11:11 I/Os per sec : 16 Reads : 100% Writes : 0% Egress throughput : 2.00 MBs/sec (Max - 2.50 MBs/sec) Ingress throughput : 2.00 MBs/sec (Max - 2.50 MBs/sec) Average response time : Read - 134971 us, Write - 0 us Minimum response time : Read - 404 us, Write - 0 us Maximum response time : Read - 3112761 us, Write - 0 us Errors : 14Network Simulator Statistics for Ingress on GigabitEthernet2/3 Dropped (tot) = 36375 Dropped (netsim) = 500 Reordered (netsim) = 0 Max Qlen(pkt) = 542 Qlen (pkt) = 0 Max Qlen (byte) = 2236 Qlen (byte) = 0 Mintxdel(poll) = 36000 Mintxdel(ethtx) = 36000 empty = 523 txdel = 70351 late = 28586 Average speed = 914 Kbps You can see that adding compression has greatly improved the speed on the link. What is shown in the netsim statistics is the actual links speed. What is shown in the SET statistics is the compressed data being moved. FCIP Interface TCP Parameters When configuring FCIP parameters, you want to do so based on the network performance. SET can help you find these things. In our example its 10MB bandwidth and 200ms round trip time:

MDS1(config)# fcip profile 1MDS1(config-profile)# tcp max-bandwidth-mbps 10 min-available-bandwidth-mbps 10 round-trip-time-ms 200MDS2(config)# fcip profile 1MDS2(config-profile)# tcp max-bandwidth-mbps 10 min-available-bandwidth-mbps 10 round-trip-time-ms 200