SAN-OS / NX-OS “which” command (Part 3)

As those of you who read this blog know, I am a big fan of the which command in SAN-OS.  I find it very useful, especially for something like CCIE Storage lab study.

There are many cases where you might have a clue to a problem you are trying to solve. For example, say you have to enable a buffer at the interface level, maybe the question says “Enable maximum amount of buffers for interface fc1/1” or something like that.  Well you don’t have to sort through 100,000 lines outputted by which, or even pipe it through various searching using “which | expression“.

The which command only returns what commands are available to you in the present context. This is why it returns exec level commands in EXEC mode, and configuration commands in config mode. It won’t return commands about iscsi until you enable iscsi. It won’t return commands about SSM modules, until you have an SSM module installed.

So back to the question at hand, say the problem is “Enable maximum amount of buffers for interface fc1/1”

MDS4(config-if)# which

[ 1]. channel-group
[ 2]. channel-group force[o]
[ 3]. channel-group auto
[ 4]. fcdomain rcf-reject vsan
[ 5]. fspf cost vsan
[ 6]. fspf dead-interval vsan
[ 7]. fspf hello-interval vsan
[ 8]. fspf passive vsan
[ 9]. fspf retransmit-interval vsan
[ 10]. link-state-trap

It only returned 50 lines, which is very manageable, and most importantly a few of these lines look very relevant to our problem, for example the following:

[ 21]. switchport fcrxbbcredit default
[ 22]. switchport fcrxbbcredit performance-buffers default
[ 23]. switchport fcrxbbcredit performance-buffers
[ 24]. switchport fcrxbbcredit
[ 25]. switchport fcrxbbcredit mode E
[ 26]. switchport fcrxbbcredit mode Fx
[ 27]. switchport fcrxbufsize

So once again, I am a big fan of this command, I think it can be very helpful when doing your studies.

This entry was posted in CCIE Storage, CLI and tagged , , , , . Bookmark the permalink.

Leave a Reply