How is ingress rate control handled for customer SLAs?
Each port is assigned a provisioned flow rate from 1Mbps to the full line rate (e.g. 100Mbps for 100BaseFX port) and a burst rate from 0Mbps to the line rate. Strict traffic policing is used to maintain the provisioned flow rate. Packets entering the port over the provisioned flow rate are dropped. Higher layer protocols (e.g. TCP) will retransmit the packet depending on the end user’s application. Traffic into a port is allowed to exceed the provisioned flow rate if a burst rate has been provisioned and the port had previously been transmitting under the provisioned flow rate. The port will maintain a record of the amount of under-utilized traffic and allow the port to burst up to its provisioned burst rate. For example, a customer has a 100BaseFX port provisioned at a 50Mbps flow rate with a burst rate at 100Mbps. If the customer transmits only 25Mbps for 2 seconds then they have accrued 50Mbits to use over and above the 50Mbps-provisioned rate. They can now burst to 100Mbps for 1 se
Related Questions
- How do you think RM professionals have handled critical issues - customer rate resistance, contract renegotiations, competition or price wars – over the past year or so?
- How often should we anticipate rate changes and how are renewals handled?
- How can I make the Ingress Rate control to work with NIC cards?
