Brocade Mobility RFS Controller System Reference Guide (Supporting software release 5.5.0.0 and later) - Manual (Page 699)

Brocade Mobility RFS Controller System Reference Guide 687
53-1003099-01
12
folder,localhost,FloorTLab,,Floor,3,US/Southeast/Alpharetta/Sanctuary Park/The Falls
1125/Queens
In the CSV file, configure specific tree node properties.
Index 1 : Record Type. This value is always 'folder'. Import/export allows the configuration
of folder nodes only. Leaf nodes cannot be configured like devices.
Index 2 : Server Name. This value is always 'localhost' as we are supporting the
import/export from localhost only.
Index 3 : Name. This configures the name/label of the tree node. This is the value which is
visible to the user in Tree node.
Index 4 : Description. This configures the additional information in form, which user wants
to store with the Tree node.
Index 5 : Type. This configures the type of the Tree node. Type can take one of the value
"country, region, city, campus, rfdomain, area, floor".
Index 6 : Floor Number. This is configures the floor number. This is applicable only for the
floor node.
Index 7 : Path. This is /'(slash delimited) from the 'root'.
Index 8 : add|delete. Allows manipulation of the node. If no value is specified, the default
is 'add' . If value is 'delete' then reference node is removed.
Select Import Tree Structure to optionally import a .csv file with pre-defined the containers and RF
Domain. Importing an existing tree saves an administrator from creating a new one from the
beginning.
Once the tree topology is defined to your satisfaction, select Export Tree Structure to archive the
tree topology (in .csv file format) to a defined location.
The exported tree topology can be re-imported and automatically displayed within the Tree
Setup screen at any time.
Select OK to update the tree setup configuration. Select Reset to revert to the last saved
configuration.
NOTE
Since the tree is set as a configuration, it follows standard configuration methods, and requires a
Commit before it takeing effect and A Save to become persistent across reboots.
Management Access Deployment Considerations
Before defining a access control configuration as part of a Management Access policy, refer to the
following deployment guidelines to ensure the configuration is optimally effective:
• Unused management protocols should be disabled to reduce a potential attack against
managed resources. For example, if a device is only being managed by the Web UI and SNMP,
there is no need to enable CLI interfaces.