Live partitioning requirements, additional NSP components
Live NSP Flow Collector Controller partitioning scheme
|
CAUTION Service Disruption |
Each disk partition described in this section must be a mounted partition, and not a symbolic link. The use of symbolic links to represent partitions is not supported.
Do not use a symbolic link to represent an NSP partition under any circumstances.
The following table lists the disk partitions required for the deployment of an NSP Flow Collector Controller in a live network environment.
Table 2-15: Live partitioning scheme, NSP Flow Collector Controller
|
Disks required: two 300 Gbyte (RAID 0) | ||
|---|---|---|
|
Partition |
Content |
Size (Gbytes) |
|
swap |
Swap space |
16 |
|
/ |
Root |
26 |
|
/home |
User home directories |
0.5 |
|
/tmp |
Temporary files |
4 |
|
/var |
System data |
64 |
|
/var/log |
System logs |
6 |
|
/var/log/audit |
System audit logs |
6 |
|
/opt/nsp |
NSP Flow Collector Controller software, operating data |
20 |
|
/opt/nsp/flow/fcc/data/extraction |
Extracted NFM-P network data model |
50 |
|
/extra |
NSP software storage |
50 |
Live auxiliary database partitioning scheme
The following table lists the partitions required for the live deployment of an auxiliary database.
For a multi-station auxiliary database, or a single-station database that has a high data rate, the /opt/nsp/nfmp/auxdb/backup partition has the following special requirements:
-
It is strongly recommended that the partition is a remote mount point or directly attached storage connected by a minimum 10 Gbyte/s link.
-
Each auxiliary database station requires a separate backup volume that is mounted as /opt/nsp/nfmp/auxdb/backup on the auxiliary database station.
For example, if the specified auxiliary database backup location is /opt/nsp/nfmp/auxdb/backup, the auxiliary database stations require the following mount points: -
The supported file systems for the backup location are ext3, ext4, and NFS.
Note: The /opt/nsp/nfmp/auxdb/backup partition can be a local mount point in a single-station database that has a low to moderate data rate.
Table 2-16: Live partitioning scheme, auxiliary database
|
Disks required: two 300 Gbyte (RAID 1), plus data storage and database backup storage capacity described in table |
Size (Gbytes) | ||
|---|---|---|---|
|
Partition |
Content |
Single-station |
Multi-station |
|
swap |
Swap space |
16 | |
|
/ |
Root |
26 | |
|
/home |
User home directories |
0.5 | |
|
/opt |
NSP auxiliary database software |
100 | |
|
/tmp |
Temporary files |
4 | |
|
/var |
System data |
64 | |
|
/var/log |
System logs |
6 | |
|
/var/log/audit |
System audit logs |
6 | |
|
/extra |
NSP and NFM-P software storage |
50 | |
|
Data storage disks required, RAID 1+0: |
Four 1.2-Tbyte |
Twelve 600 Gbyte | |
|
/opt/nsp/nfmp/auxdb/data |
Auxiliary database data |
2200 |
3300 |
|
Database backup storage disks required, RAID 5: |
Four 1.2-Tbyte |
Five 1.2-Tbyte | |
|
/opt/nsp/nfmp/auxdb/backup 1 |
Auxiliary database backup data |
3300 |
4400 |
Notes:
Auxiliary database backups are optional but strongly recommended to protect against complete data loss due to disk failure, data corruption, or upgrade failure. The backups can be stored on a separate volume, as indicated in the table above, or on a remote mount point reachable over a minimum 10 Gbyte/s link. The listed capacity is sufficient for at least one persisted backup.
Live NSP Flow Collector partitioning scheme
|
|
CAUTION Service Disruption |
Each disk partition described in this section must be a mounted partition, and not a symbolic link. The use of symbolic links to represent partitions is not supported.
Do not use a symbolic link to represent an NSP partition under any circumstances.
The following table lists the disk partitions required for the deployment of an NSP Flow Collector in a live network environment.
Table 2-17: Live partitioning scheme, NSP Flow Collector
|
Disks required: two 300 Gbyte (RAID 0) | ||
|---|---|---|
|
Partition |
Content |
Size (Gbytes) |
|
swap |
Swap space |
16 |
|
/ |
Root |
26 |
|
/home |
User home directories |
0.5 |
|
/tmp |
Temporary files |
4 |
|
/var |
System data |
64 |
|
/var/log |
System logs |
6 |
|
/var/log/audit |
System audit logs |
6 |
|
/opt/nsp |
NSP Flow Collector software, operating data |
50 |
|
/opt/nsp/flow/fc/data/results |
Collected statistics data files |
200 |
|
/extra |
NSP software storage |
50 |
Live collocated NSP Flow Collector Controller / Flow Collector partitioning scheme
|
|
CAUTION Service Disruption |
Each disk partition described in this section must be a mounted partition, and not a symbolic link. The use of symbolic links to represent partitions is not supported.
Do not use a symbolic link to represent an NSP partition under any circumstances.
The following table lists the disk partitions required for the deployment of an NSP Flow Collector Controller and Flow Collector that are collocated on one station in a live network environment.
Table 2-18: Live partitioning scheme, collocated NSP Flow Collector Controller and Flow Collector
|
Disks required: two 300 Gbyte | ||
|---|---|---|
|
Partition |
Content |
Size (Gbytes) |
|
swap |
Swap space |
16 |
|
/ |
Root |
26 |
|
/home |
User home directories |
0.5 |
|
/tmp |
Temporary files |
4 |
|
/var |
System data |
64 |
|
/var/log |
System logs |
6 |
|
/var/log/audit |
System audit logs |
6 |
|
/opt/nsp |
NSP Flow Collector software, operating data |
70 |
|
/opt/nsp/flow/fcc/data/extraction |
Extracted NFM-P network data model |
50 |
|
/opt/nsp/flow/fc/data/results |
Collected statistics data files |
200 |
|
/extra |
NSP software storage |
50 |