[c-nsp] SVI based Xconnect / How to Limit Unknown Unicast Flooding

[vikas hazrati]

Hello

We have been testing the config for an EoMPLS service for our network.
The client will be able to send traffic to the 7609 through
an xconnect circuit. In the egress 7609 the xconnect will be SVI
based. This choise is made to minimize the number of xconnect
cirtuits (one will service multiple physical interfaces connecting to
the client). In this way once EoMPLS traffic reaches the 7609,
it will switched, based on destination MAC,  to the appropriate egress
interface (x1, x2 ... xn) .


int x1--------|--------------------------|
int x2--------|                          |
int x3--------| (ES-Card)7609_1|
int x4--------|    int VLAN 100   |===EoMPLS=== (7609_2)
....            |  xconnect 1.1.1.1|
int xn--------|_______________|

We need to find though a way to minimize unknown multicast flooding on
the egress interfaces but our range of choices seem to
be very limited.

- The interfaces are part of ES cards
- We are using EVCs so "Unknown Traffic Flood Control" is not
available (no switchport)

Apart from rate policying total outgoing traffic per physical
interface in the egress 7609 what
mechanisms are available for unknown unicast flooding reduction in the
case when:
the outgoing interfaces are not switch-ports.


I am looking for a command option similar to the (for ASR9K)

(config-l2vpn)# bridge group 1

(config-l2vpn-bg)# bridge-domain 1

(config-l2vpn-bg-bd)# flooding disable

Does any one have any idea how can we limit Unknown Unicast Flooding
for traffic arriving though an SVI-Based xconnect in 7600/ES?

Thanx for the help