Unsolved
This post is more than 5 years old
13 Posts
0
643
March 17th, 2008 10:00
FOS 6.0.0b Traffic Isolation zones
I implemented the Traffic Isolation zone feature which became available with FOS 6.0.0b but had to back out. TI zones will not work because FSPF routing rules take precedence. This defeats the purpose why I wanted to implement TI zones in the first place. I wanted to dedicate the ISL regardless of its link cost but FSPF rule says all traffic must use the lowest cost path. If the dedicated ISL is not the lowest cost path the TI zone path is broken and TI zone traffic uses other non-dedicated ISL that has the lowest cost path (if failover is enabled) or the TI zone traffic is blocked (if failover is disabled). I made the dedicated ISL the lowest cost path with the 'linkcost' command but other non-TI zone traffic started using the ISL which I didn't want. This appears to be a Traffic Isolation design flaw or at least I disagree with the FSPF lowest cost rule for TI zones . Any idea how I can bypass the lowest cost path rule?
No Events found!
Ed Schulte
2 Intern
•
151 Posts
0
March 19th, 2008 10:00
Let me try to find an answer to this. I might need more information later on, but I'll get back to you.
regards,
ed
Ed Schulte
2 Intern
•
151 Posts
0
March 25th, 2008 02:00
I checked with Brocade. FSPF rules will overrule TI Zones, this is not a bug. TI Zones is really designed for multiple equal-cost paths.
Using the test above, if the TI zone did not have failover enabled and the TI path had the lowest cost path, then all other traffic would not be able to traverse the fabric.
So, it looks that what you want is not possible. You can always put in an enhancement request. But that will take some work on your side, by opening a service request. And then it will take some time to get this verified. Up to you,
regards,
ed
jyCG1
13 Posts
0
March 25th, 2008 16:00
jyCG1
13 Posts
0
March 25th, 2008 16:00
It turns out that there is a firmware bug with FOS 6.0.0b when the portcfglongdistance distance_level is set to LD. Brocade support suggested that it is set to LS. This fixed the issues I was having with Traffic zones. Everything is working as I expected now.