+\subsubsection pf_cabinet <cabinet>
+
+\note
+ This tag is only available when the routing mode of the AS
+ is set to ``Cluster``.
+
+The ``<cabinet />`` tag is, like the \ref pf_cluster "<cluster>" tag,
+a meta-tag. This means that it is simply a shortcut for creating a set of (homogenous) hosts and links quickly;
+unsurprisingly, this tag was introduced to setup cabinets in data centers quickly. Unlike
+<cluster>, however, the <cabinet> assumes that you create the backbone
+and routers yourself; see our examples below.
+
+#### Attributes ####
+
+Attribute name | Mandatory | Values | Description
+--------------- | --------- | ------ | -----------
+id | yes | string | The identifier of the cabinet. Facilitates referring to this cluster.
+prefix | yes | string | Each node of the cabinet has to have a name. This name will be prefixed with this prefix.
+suffix | yes | string | Each node of the cabinet will be suffixed with this suffix
+radical | yes | string | Regexp used to generate cabinet nodes name. Syntax: "10-20" will give you 11 machines numbered from 10 to 20, "10-20;2" will give you 12 machines, one with the number 2, others numbered as before. The produced number is concatenated between prefix and suffix to form machine names.
+power | yes | int | Same as the ``power`` attribute of the \ref pf_host "<host>" tag.
+bw | yes | int | Bandwidth for the links between nodes and backbone (if any). See the \ref pf_link "link section" for syntax/details.
+lat | yes | int | Latency for the links between nodes and backbone (if any). See the \ref pf_link "link section" for syntax/details.
+
+\note
+ Please note that as of now, it is impossible to change attributes such as,
+ amount of cores (always set to 1), the initial state of hosts/links
+ (always set to ON), the sharing policy of the links (always set to \ref sharing_policy_fullduplex "FULLDUPLEX").
+
+#### Example ####
+
+The following example was taken from ``examples/platforms/meta_cluster.xml`` and
+shows how to use the cabinet tag.
+
+\verbatim
+ <AS id="my_cluster1" routing="Cluster">
+ <cabinet id="cabinet1" prefix="host-" suffix=".cluster1"
+ power="1Gf" bw="125MBps" lat="100us" radical="1-10"/>
+ <cabinet id="cabinet2" prefix="host-" suffix=".cluster1"
+ power="1Gf" bw="125MBps" lat="100us" radical="11-20"/>
+ <cabinet id="cabinet3" prefix="host-" suffix=".cluster1"
+ power="1Gf" bw="125MBps" lat="100us" radical="21-30"/>
+
+ <backbone id="backbone1" bandwidth="2.25GBps" latency="500us"/>
+ </AS>
+\endverbatim
+
+\note
+ Please note that you must specify the \ref pf_backbone "<backbone>"
+ tag by yourself; this is not done automatically and there are no checks
+ that ensure this backbone was defined.
+
+The hosts generated in the above example are named host-1.cluster, host-2.cluster1
+etc.
+
+