beautypg.com

Scalability – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual

Page 60

background image

36

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide

53-1003031-02

RSVP soft preemption

1

Brocade(config-if-e1000-1/8)# show mpls int e1/7

Admin: Up Oper: Up

MTU: 1500 bytes

Maximum BW: 10000000 kbps, maximum reservable BW: 10000000 kbps

Admin group: 0x00000000

Reservable BW [priority] kbps:

[0] 10000000 [1] 10000000 [2] 10000000 [3] 10000000

[4] 10000000 [5] 10000000 [6] 10000000 [7] 10000000

Last sent reservable BW [priority] kbps:

[0] 10000000 [1] 10000000 [2] 10000000 [3] 10000000

[4] 10000000 [5] 10000000 [6] 10000000 [7] 10000000

Soft Preemption under provisioned BW [priority] kbps:

[0] 0 [1] 0 [2] 0 [3] 0

[4] 0 [5] 0 [6] 0 [7] 0

LDP tunnel count: 0

P2MP Capable : Yes

Scalability

With the default value (30 seconds) configured for the soft preemption wait timer, the following
scalability numbers have been collected under the following conditions:

System was running MPLS with few interfaces enabled with MPLS and OSPF as traffic
engineering

LSPs were configured on the routers

Soft preemption was triggered by decreasing the BW on transit router/high priority LSP

All the routers were soft preemption enabled with default wait timer configuration

Alternate paths were available for MBB of LSPs impacted

TABLE 3

Maximum soft preempted LSPs

Device Type

Maximum soft preempted LSPs

Brocade NetIron XMR (with MP++)

2000

Brocade MLX Series

1000

Brocade NetIron CES

128

Brocade NetIron CER

500

Behavioral impact on changing the wait timer value:

Timer value 0 means no soft preemption

Timer value 30 is minimum which can be configured other than 0, for which above data is
applicable

Timer value >30 config shows better performance in terms of number of LSPs which can get
successfully soft preempted provided other criteria are met for MBB. It is expected to be
almost directly proportional to the amount by which timer value is increased. For example, 60
second is double the number of LSPs/maximum configurable LSPs on device under test. The
user must verify for accuracy.