netflow:config
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| netflow:config [2025/04/01 17:35] – [Diagram] veera | netflow:config [2025/04/01 17:44] (current) – [DRAC] veera | ||
|---|---|---|---|
| Line 31: | Line 31: | ||
| </ | </ | ||
| + | |||
| + | |||
| + | Create and apply the ACL to these IP subnets - these would represent the customers subnets and support IPs of vendor. | ||
| + | |||
| + | < | ||
| + | |||
| + | ip access-list extended RestrictedAccess | ||
| + | | ||
| + | | ||
| + | | ||
| + | deny ip any way | ||
| + | |||
| + | </ | ||
| + | |||
| + | |||
| + | On the Trisul NetFlow server set the other IP in the ''/ | ||
| + | |||
| + | < | ||
| + | |||
| + | ip addr add 203.0.118.33/ | ||
| + | ip route add default via 203.0.118.0 dev eth0 | ||
| + | |||
| + | </ | ||
| + | |||
| + | |||
| + | ===== DRAC ===== | ||
| + | |||
| + | |||
| + | If you wish to use DRAC for remote access then you can configure a second link using the same method. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | |||
| + | ===== Other options - Management VLAN ===== | ||
| + | |||
| + | If you have a separate management VLAN , then you can replace the public IP Address with private IP addresses in the management VLAN instead. | ||
| + | |||
| + | |||
netflow/config.1743509112.txt.gz · Last modified: 2025/04/01 17:35 by veera