Network Bandwidth Limiting with NappIT / OI

[Zer022]

Quick question for anyone familiar with this. I have 2x OpenIndiana boxes running the full licensed version of Napp-it with all extensions. I use the replication features to mirror storage from other appliances to these for backup.

Is there a way to limit the amount of bandwidth that can be used for napp-it's replication process? Some of my replication jobs run over WAN links and I don't want to completely flood the links with storage replication traffic.

Is there a way to do this from the command line?

Better still is this a feature that could be added to napp-it GUI? It could either be set on each SOURCE or it could be set for each replication job on the TARGET server?

 

[MrD1234]

If replication is using zfs send / receive, it's conceivable that it can be wrapped with mbuffer.

 

[Zer022]

it is using ZFS send/receive for replication but I think with napp-it it's wrapped up so that the replication can be scheduled and automated with efficient data transfer, so it takes the snapshot, packages it up and syncs it over etc.

For limiting at the source it would probably be enough if it was possible to limit the bandwidth for all traffic to a specific remote IP, then there would be no need to understand the intimate details of how napp-it's replication scripts and stuff work.

 

[paret0]

You can limit and cap your bandwidth more ways than you want to know in OI. Flows, rings, lanes...

Here's a simple way with dlstat and dladm:

https://blogs.oracle.com/JeffV/entry/virtual_network_part_4

 

[_Gea]

Quick question for anyone familiar with this. I have 2x OpenIndiana boxes running the full licensed version of Napp-it with all extensions. I use the replication features to mirror storage from other appliances to these for backup.

Is there a way to limit the amount of bandwidth that can be used for napp-it's replication process? Some of my replication jobs run over WAN links and I don't want to completely flood the links with storage replication traffic.

Is there a way to do this from the command line?

Better still is this a feature that could be added to napp-it GUI? It could either be set on each SOURCE or it could be set for each replication job on the TARGET server?

maybee flowadm is what you are looking for:
http://docs.oracle.com/cd/E19963-01/html/821-1462/flowadm-1m.html

 

[Zer022]

Yep I was looking at flowadm as the most likely candidate although it only limits down to 1.5mbit I can't see many scenario's where we would go lower than that.

Is there any chance of having something built into the napp-it GUI for setting a limit based on either the target IP/hostname of the traffic or the source adapter?

 

[_Gea]

Yep I was looking at flowadm as the most likely candidate although it only limits down to 1.5mbit I can't see many scenario's where we would go lower than that.

Is there any chance of having something built into the napp-it GUI for setting a limit based on either the target IP/hostname of the traffic or the source adapter?

I see now way to do.
Other option may using a firewall/vpn solution that optionally offer such a functionality.

 

[Zer022]

Found a good flowadm example at the link below, have pasted the actual commands in here below for reference also. If we dropped the destination port and just used the remote_ip we could set a limit on traffic to this remote IP and check the flowadm status to see what current limit is applied if any.

If the remote IP is the address of the TARGET system for replication setting this would effectively rate limit replication traffic, which would be pretty useful. If napp-it replication is using a specific source or destination port then we could be even more specific and ensure that we don't affect other traffic between the two boxes.

If something like this could be added to the napp-it gui that would be very useful for my situation where I have replication over several WAN links to an offsite DR location and don't want to flood the links.

It would make WAN-Replication a viable feature to list on napp-it's list of achievements

http://serverfault.com/questions/141182/how-can-i-rate-limit-packet-shape-traffic-shape-on-solaris

flowadm add-flow -l xnf0 -a remote_ip=193.49.161.207,remote_port=43833 flow-tcp-app
flowadm set-flowprop -p maxbw=8M flow-tcp-app

 

[_Gea]

Found a good flowadm example at the link below, have pasted the actual commands in here below for reference also. If we dropped the destination port and just used the remote_ip we could set a limit on traffic to this remote IP and check the flowadm status to see what current limit is applied if any.

If the remote IP is the address of the TARGET system for replication setting this would effectively rate limit replication traffic, which would be pretty useful. If napp-it replication is using a specific source or destination port then we could be even more specific and ensure that we don't affect other traffic between the two boxes.

If something like this could be added to the napp-it gui that would be very useful for my situation where I have replication over several WAN links to an offsite DR location and don't want to flood the links.

It would make WAN-Replication a viable feature to list on napp-it's list of achievements

http://serverfault.com/questions/141182/how-can-i-rate-limit-packet-shape-traffic-shape-on-solaris

flowadm add-flow -l xnf0 -a remote_ip=193.49.161.207,remote_port=43833 flow-tcp-app
flowadm set-flowprop -p maxbw=8M flow-tcp-app

Each replication has its own port (same is used on both sides), see menu jobs

 

[Zer022]

So I ended up using a dedicated NIC for replication traffic and them used dladm to limit bandwidth for that NIC

#Show Current settings for e1000g0
dladm show-linkprop -p maxbw e1000g0

#Set a limit of 10Mbit for e1000g0
dladm set-linkprop -p maxbw=10 e1000g0

Just got the box to the remote site so now for a first replication run!