Comentários (14)

1 KiwiSan comentou às Link permanente

Great article answering 95% of my questions but ... you talk about configuring VEX ports but use the portCfgEXPort command rather than portCfgVEXPort. By using just EX ports won't you end up with merged fabrics? Or does having the separate fabric id's keep things apart? <div>&nbsp;</div> Cheers

2 talor comentou às Link permanente

Hi, <div>&nbsp;</div> Thanks for that. <div>&nbsp;</div> The diagram should be EX ports, not VEX ports, I'll fix that up shortly, thanks for pointing that out. <div>&nbsp;</div> Using EX ports won't merge the fabrics, the only time fabrics will merge is if you are using an E port or a VE port. <div>&nbsp;</div> We do have VE ports across the backbone fabric, as that fabric is merged, however the other four fabrics are kept separate. <div>&nbsp;</div> Having unique fabric IDs and EX ports will stop fabrics from merging. If you have EX ports and duplicate fabric IDs somewhere, that will cause a fabric ID conflict, and it will shut the EX port down. <div>&nbsp;</div> In the diagram, there are five separate fabrics. The backbone fabric, two fabrics at the "production site" and two fabrics at the "dr site". <div>&nbsp;</div> Hope this answers your question, I'm happy to provide more detail if you need it. <div>&nbsp;</div> Talor.

3 tabin comentou às Link permanente

Hi <div>&nbsp;</div> Thanks for this article. I have very similar situation but with one difference - I don't want to have one backbone fabric so I have set a VEX port on the one SAN06-B router. I can't see imported proxy devices, local V7000 ports are shown as EXIST but I can't see the remote V7000 ports as Imported - they are all as Configured. I don't want to change from VEX port to VE port. I tried to configure lsan zones and configs on both routers but it didn't work. Do You have any idea where might be the problem?

4 Gareth_W comentou às Link permanente

Hi Talor, <div>&nbsp;</div> Excellent Post, I have found your info very helpful and have successfully implemented Brocade FCIP routers for V7000 global Mirror however we are suffering from V7000 1720 errors the cause seems to be one of our the wan links pausing/dropping overnight, we are looking to fail the circuit when this happens as we are using two circuits in the tunnel over separate links, currently by default the circuit has a keep alive set to the default of 10 seconds we are looking to drop it down to 1 second, have you come across something similar the only information I can find regarding keep live for the V7000 is the document 80ms for global mirror, <br />

5 talor comentou às Link permanente

Hi Gareth, <div>&nbsp;</div> Thanks for that. The 1720 error is going to occur when there is excessive latency or a large number of errors between the partnership so it makes sense that this is happening if your link is dropping out, so the V7000 is working as it's supposed to. <div>&nbsp;</div> The below link has some information that might be of use to you, hope this helps. <div>&nbsp;</div> <div>&nbsp;</div> How often is your tunnel dropping out, and what is the size of the link / the round trip latency? <br />

6 GertvanKempen comentou às Link permanente

I am managing a project that looks similar to what you describe here. An important thing that the implementation partner says is required is that they need a layer2 network link between the two locations. That can be delivered, but requires hardware and a lot of work in our environment. In this article I don't see that requirement. Is it true that you need a layer2 connection, or should it also work on layer3?

7 talor comentou às Link permanente

Hi, <div>&nbsp;</div> The configuration described here is for a specific scenario where there is an IP (layer 3) link between the sites. The FCoIP tunnel is configured to enable fiber channel traffic to be sent over a regular IP link. In this specific case there is only a layer 3 requirement, however it is important to ensure that the round trip latency is no greater than 80 milliseconds across the link and the bandwidth is sufficient for your write requirements. <div>&nbsp;</div> See this link: <div>&nbsp;</div> <div>&nbsp;</div> What I have mentioned here is based on the assumption that you have IBM/Brocade SAN router devices (such as IBM SAN06B-R) with the integrated routing feature at either site to achieve what's described here. <div>&nbsp;</div> Hope this helps.

8 5S4P_冠智_曾 comentou às Link permanente

Hi I have very similar project to help customer build a V7000 Globla Mirroring (without change volumes) with FCoIP between SAN Router (SAN60B-R). We have two lun Global Mirroring releationship to DR site. <br /> And we do not have setup consistent group. Each lun releationship is independent syncing to DR site. <div>&nbsp;</div> Here is the situaction we face.... <div>&nbsp;</div> Each time we start the Global Mirroring and wait the status become to "Consistent Synchronized " , after 1 day or few days, the status become "Consistent Stopped" by itself. And then we have to start the Global Mirroring again. <div>&nbsp;</div> And our setting is like these. <br /> SAN router`s FCoIP channel QoS = 1Gbps (as 125 MB/s) <br /> Both side`s V7000 partnership `s bandwidth = 100MB/s <br /> Both side`s V7000 relationship`s bandwidth = 90MB/s <div>&nbsp;</div> Any suggestion ? Thank you !

9 talor comentou às Link permanente

Hi, <div>&nbsp;</div> When the remote copy relationship stops, do you see 1920 errors under events on the source V7000? There is some useful information in the following article, that you might want to have a look at as this may help you solve the problem: <div>&nbsp;</div> <div>&nbsp;</div> Hope this is of use to you.

10 5S4P_冠智_曾 comentou às Link permanente

Hi <br /> Thank you ! <br /> We found 1630 and 1720. <div>&nbsp;</div> And I check the Redbook <br /> "1720 error : In practice, the source of this error is most often a fabric problem or a problem the network path between your partners" <div>&nbsp;</div> and we will check SAN switch and Router`s log. <div>&nbsp;</div> Thank you !

11 JimmyChien comentou às Link permanente

Hi Talor, <br /> Our Customer use 2 V7000, and Global Mirror to Synced a 4TB LUN to DR Site, and they use two (100Mb download / 40Mb upload Line) to build a Connection between Production &amp; DR Site. And the FCIP Link lays in this connection.(The line is for personal use usually, they use it because of Budget,but not a leased line : <div>&nbsp;</div> Their environment is VMs store in V7000’s LUN <br /> Our customer response that they sometimes found the file system on their Server is become read only, and they will have to reboot to fix it. And their end user feel laggy when use their application to input data, When stop Global Mirror ,it become normal again <div>&nbsp;</div> It seems the Bandwidth affect the Storage to become laggy <br /> May I ask a question about how to sizing a Bandwidth , Where I use v7000 Global Mirror? <br /> Does Global Mirror cost the cache only when the bandwidth is not enough, and data is congested in the source side? <div>&nbsp;</div> thank you very much

12 talor comentou às Link permanente

Hi Jimmy, <div>&nbsp;</div> When you size the bandwidth for global mirror, if you have TPC typically work out what the peak writes are from the source. If you don't have TPC, you will have to look at each host that is accessing the storage, and work out the write requirements for the link. If you have a slow or unreliable link it might be worth considering using global mirror with change volumes.

13 JimmyChien comentou às Link permanente

Thanks talor, Our customer have their FCIP link build on an IPSEC encryption tunnel , the link could not become status up at the first time. finally they disable the IPSEC encryption, the FCIP link comes up,do you know whether FCIP support build on encryption tunnel or not.?

14 talor comentou às Link permanente

Hi Jimmy, <div>&nbsp;</div> I didn't find anything suggesting that IPSEC was not supported, however if it adds latency and/or reduces available bandwidth then it could potentially be an issue. <div>&nbsp;</div> On an unrelated note, I noticed that this month native IP replication was announced for V7000, so potentially using the brocade devices for FCoIP may no longer be required going forward.