Tips and Pitfalls: VSAN’s, Ports and FC Routing

This is the first of a series of posts where I am collectively mentioning some of the pitfalls I have ran into while studying for the lab. These are things that I try to keep top of mind as I work through configurations and can catch you off guard if you do not pay careful attention. I start off listing the commands that I am constantly using and then list some of the Key Points and Pitfalls.

This is not an exhaustive list of commands. You need to know every command there is, literally. But these are some that I find I am using alot, and I am sure I left a bunch of stuff out so i will try to go back and update these posts.

These are just tidbits. This is nothing like having actual study materials like those available from IEmentor.com.

These tips will likely migrate over to the CCIE Storage Wiki once I have time to clean it up.

Common Commands

show int brief

show vsan member

show int | inc iso

show int trunk van xx

show int fcx/y bbcredit

show fcdomain domain-list vsan vsan

show fspf internal route vsan vsan

show fcroute unicast vsan vsan

show flog data vsan

show fcns data vsan

show topology vsan

Key Points / Pitfalls

  • fcroutes do not show up in the normal FSPF routing table
  • src-dst-ox-id is the default loadbalancing
  • DPVM should only be used on F ports
  • FC Static Routing
This entry was posted in CCIE Storage, FSPF and tagged , . Bookmark the permalink.

4 Responses to Tips and Pitfalls: VSAN’s, Ports and FC Routing

  1. Arun says:

    Hey Brian,
    Is “src-dst-id is the default loadbalancing”? I think you need to correct this to “src-dst-ox-id”.

    Other than that, I really appreciate your effort to share your experiences. And congratulations on passing the CCIE Storage Lab exam.

    Thanks
    Arun

    • brian says:

      Yes I replied to your post, here is the reply as well:

      Although static routes may be an option, I have seen bugs with static routes and would not use them myself. Specifically I have seen very strange behavior with domain services and other fabric services.

      The way to accomplish what you are trying to do is using IVR Service Groups, this allows you to carve specific paths for IVR connectivity. Have a look at the configuration guide for IVR Service Groups.

Leave a Reply