I agree with Tim. Honestly it seems that the KB article has the wrong command listed, or maybe just not enough info listed about using said command. I imagine if you were to add a disk count that would put the aggr over 16TB then the command in the KB might work.
Here is a test from my lab box where the check was performed.
FAS3270A> priv set advanced
Warning: These advanced commands are potentially dangerous; use
them only when directed to do so by NetApp
personnel.
FAS3270A*>
FAS3270A*>
FAS3270A*> aggr 64bit-upgrade start aggrtest -mode check
Checking for additional space required to upgrade all writable 32-bit
volumes in aggregate aggrtest (Ctrl-C to interrupt)......
Upgrading a volume to 64-bit consumes additional free space in the volume. The
following table shows the space usage after each volume is upgraded to 64-bit:
Volume Name Total Used Available Capacity
----------- ----- ---- --------- --------
voltest 100MB 5448KB 94MB 5%
To initiate the 64-bit upgrade of aggregate aggrtest, run this
command with the "normal", "grow-reserved", or "grow-all" option.
If you use the "grow-reserved" or "grow-all" option, volume sizes
will be increased automatically as needed during the upgrade.
If I ran the commands from the KB I got the same output you did. Running the command as seen above was the only way I could get the check to run.