I think I can help. Import and export of nodes is very ticklish.

When you export the node, you must issue a q fi nodename f=d to get the
numbers of the filespaces. Then, in the export command use the fsid=1,2,3
etc option, and replace the 1,2,3 with the numbers associated with the
filespaces you're exporting. Make note of the numbers (in sequence) and the
associated unicode filespace names (filespaces that begin with a \\ as
opposed to a drive letter). When you execute the command, use filespace=*
fsid=1,2,3 etc and unifilespace=\\whatever\whatever,\\whatever\whatever etc,
and the rest of the command as presented below.

The same care must be taken on an import. After you move the EXP files to
the new server, you must import them. When you import, the nodename should
be associated with the desired management class. If your management class
dictates which storage pools to use, you should change the default
management class to the one you want the imported node to be part of, and
then import it. You can set the default management class back to normal
after you've completed the import operation.

Here's a command to import a normal node.

import node foo filespace=* filedata=all unifilespace=\\alpha\c$ preview=no
devclass=foodev1 volumenames=/tsm/07062600.exp,/tsm/07066336.exp etc.

you MUST import the exp files in the order they were exported. Make sure you
have the same estimated max capacity in the two device classes (which must
be the same on the two servers) so volume creation will coincide and be
easier to track. The order they were exported should be parallel to the
order imported, which must be in the same order as the unifilespace= command
above. This order can be maintained by using the order presented by the q fi
nodename f=d command. Remember to only include the unicode filespace (stuff
with a \\ in front of it) in the command above.

Let me know if this helps,

Kevin.