Figure 82 shows the topology used as an example of a basic SPBM configuration.
*A:PE-63# configure service vpls 10 spb ?
- no spb
- spb [<isis-instance>] [fid <fid>] [create]
<isis-instance> : [1024..2047]
<fid> : [1..4095]
level + Configure SPB level information
[no] lsp-lifetime - Configure LSP lifetime
[no] lsp-wait - Configure ISIS LSP wait times
[no] overload - Configure the local router so that it appears to be overloaded
[no] overload-on-bo* - Configure the local router so that it appears to be overloaded at boot up
[no] shutdown - Administratively enable or disable the operation of ISIS
[no] spf-wait - Configure ISIS SPF wait times
*A:PE-63# configure service vpls 10 spoke-sdp 35:10 spb ?
- no spb
- spb [create]
<create> : keyword
level + Configure SPB level information
[no] lsp-pacing-int* - Configure the interval between LSP packets are sent from the interface
[no] retransmit-int* - Configure the minimum interval between LSP packets retransmission for the given interface
[no] shutdown - Administratively Enable/disable the interface
*A:PE-63# configure service vpls 10 spoke-sdp 35:10 spb level 1 ?
- level <[1..1]>
[no] hello-interval - Configure hello-interval for this interface
[no] hello-multipli* - Configure hello-multiplier for this level
[no] metric - Configure IS-IS interface metric for IPv4 unicast
|
→
|
<fid> or forwarding identifier identifies the standard SPBM B-VID which is signaled in IS-IS with each advertised BMAC. Each B-VPLS has a single configurable FID.
|
*A:PE-63>config>service# info
----------------------------------------------
pbb
source-bmac 00:00:00:ca:fe:63
mac-name "PE-63" 00:00:00:ca:fe:63
mac-name "PE-64" 00:00:00:ca:fe:64
mac-name "PE-65" 00:00:00:ca:fe:65
mac-name "PE-66" 00:00:00:ca:fe:66
mac-name "PE-67" 00:00:00:ca:fe:67
mac-name "PE-69" 00:00:00:ca:fe:69
exit
...
vpls 10 customer 1 b-vpls create
service-mtu 2000
stp
shutdown
exit
spb 1024 fid 10 create
overload-on-boot timeout 60
spf-wait 2 50 100
lsp-wait 8 0 1
no shutdown
exit
spoke-sdp 35:10 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 36:10 create
spb create
no shutdown
exit
no shutdown
exit
no shutdown
exit
vpls 11 customer 1 i-vpls create
pbb
backbone-vpls 10
exit
exit
stp
shutdown
exit
sap 1/1/1:11 create
exit
no shutdown
exit
epipe 12 customer 1 create
pbb
tunnel 10 backbone-dest-mac "PE-64" isid 12
exit
sap 1/1/1:12 create
exit
no shutdown
exit
As discussed, the bridge-priority will influence the election of the Multicast Designated Bridge. By making PE-65’s bridge-priority zero, it ensures that PE-65 becomes the root of all the STs for B-VPLS 10 as long as the priority for the rest of the PEs is larger than zero. In case of a tie, the PE owning the lowest system BMAC will be elected as Multicast Designated Bridge.
Figure 82 shows the ST for I-VPLS 11 (see a thicker continuous line representing the ST). Note that PE-65 is the root of the ST tree.
*A:PE-65>config>service# info
----------------------------------------------
pbb
source-bmac 00:00:00:ca:fe:65
mac-name "PE-63" 00:00:00:ca:fe:63
mac-name "PE-64" 00:00:00:ca:fe:64
mac-name "PE-65" 00:00:00:ca:fe:65
mac-name "PE-66" 00:00:00:ca:fe:66
mac-name "PE-67" 00:00:00:ca:fe:67
mac-name "PE-69" 00:00:00:ca:fe:69
exit
...
vpls 10 customer 1 b-vpls create
service-mtu 2000
stp
shutdown
exit
spb 1024 fid 10 create
level 1
bridge-priority 0
exit
overload-on-boot timeout 60
spf-wait 2 50 100
lsp-wait 8 0 1
no shutdown
exit
spoke-sdp 53:10 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 56:10 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 57:10 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 59:10 create
spb create
no shutdown
exit
no shutdown
exit
no shutdown
exit
*A:PE-63# show service id 10 spb base
===============================================================================
Service SPB Information
===============================================================================
Admin State : Up Oper State : Up
ISIS Instance : 1024 FID : 10
Bridge Priority : 8 Fwd Tree Top Ucast : spf
Fwd Tree Top Mcast : st
Bridge Id : 80:00.00:00:00:ca:fe:63
Mcast Desig Bridge : 00:00.00:00:00:ca:fe:65
===============================================================================
ISIS Interfaces
===============================================================================
Interface Level CircID Oper State L1/L2 Metric
-------------------------------------------------------------------------------
sdp:35:10 L1 65536 Up 10/-
sdp:36:10 L1 65537 Up 10/-
-------------------------------------------------------------------------------
Interfaces : 2
===============================================================================
FID ranges using ECT Algorithm
-------------------------------------------------------------------------------
1-4095 low-path-id
===============================================================================
*A:PE-63# show service id 10 spb fdb
==============================================================================
User service FDB information
==============================================================================
MAC Addr UCast Source State MCast Source State
------------------------------------------------------------------------------
00:00:00:ca:fe:64 35:10 ok 35:10 ok
00:00:00:ca:fe:65 35:10 ok 35:10 ok
00:00:00:ca:fe:66 36:10 ok 35:10 ok
00:00:00:ca:fe:67 35:10 ok 35:10 ok
00:00:00:ca:fe:69 35:10 ok 35:10 ok
------------------------------------------------------------------------------
Entries found: 5
==============================================================================
|
•
|
show service id 10 spb routes provides a detailed view of the unicast and multicast routes computed by SPF. As shown below, the SPB unicast and multicast routes match on PE-65 since this node is the Multicast Designated Bridge. Unicast and multicast routes will differ on most other nodes.
|
|
•
|
show service id 10 spb mfib and show service id 10 mfib shows information of the MFIB entries generated in the B-VPLS as well as the outgoing interface (OIF) associated with those MFIB entries.
|
*A:PE-65# show service id 10 spb routes
================================================================
MAC Route Table
================================================================
FID MAC Addr Ver. Metric
NextHop If SysID
----------------------------------------------------------------
Fwd Tree: unicast
----------------------------------------------------------------
10 00:00:00:ca:fe:63 3 10
sdp:53:10 PE-63
10 00:00:00:ca:fe:64 9 20
sdp:57:10 PE-67
10 00:00:00:ca:fe:66 4 10
sdp:56:10 PE-66
10 00:00:00:ca:fe:67 8 10
sdp:57:10 PE-67
10 00:00:00:ca:fe:69 12 10
sdp:59:10 PE-69
Fwd Tree: multicast
----------------------------------------------------------------
10 00:00:00:ca:fe:63 3 10
sdp:53:10 PE-63
10 00:00:00:ca:fe:64 9 20
sdp:57:10 PE-67
10 00:00:00:ca:fe:66 15 10
sdp:56:10 PE-66
10 00:00:00:ca:fe:67 8 10
sdp:57:10 PE-67
10 00:00:00:ca:fe:69 12 10
sdp:59:10 PE-69
----------------------------------------------------------------
No. of MAC Routes: 10
================================================================
================================================================
ISID Route Table
================================================================
FID ISID Ver.
NextHop If SysID
----------------------------------------------------------------
10 11 16
sdp:53:10 PE-63
sdp:56:10 PE-66
sdp:57:10 PE-67
----------------------------------------------------------------
No. of ISID Routes: 1
================================================================
*A:PE-65# show service id 10 spb mfib
===============================================================================
User service MFIB information
===============================================================================
MAC Addr ISID Status
-------------------------------------------------------------------------------
01:1E:83:00:00:0B 11 Ok
-------------------------------------------------------------------------------
Entries found: 1
===============================================================================
A:PE-65# show service id 10 mfib
===============================================================================
Multicast FIB, Service 10
===============================================================================
Source Address Group Address Sap/Sdp Id Svc Id Fwd/Blk
-------------------------------------------------------------------------------
* 01:1E:83:00:00:0B b-sdp:53:10 Local Fwd
b-sdp:56:10 Local Fwd
b-sdp:59:10 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 1
===============================================================================
SPB Multicast Trees (STs) are pruned for each particular I-VPLS ISID, based on the advertisement of I-VPLS ISIDs in SPB IS-IS by each individual PE. Multicast B-VPLS traffic not belonging to any particular I-VPLS follows the Default Tree. The Default Tree is an ST for the B-VPLS which is not pruned and therefore reaches all the PE nodes in the B-VPLS. For instance, Ethernet-CFM CCM messages sent from vMEPs configured on the SPB B-VPLS will use the default tree. The default tree does not consume MFIB entries and can be checked in each node through the use of the following command:
*A:PE-69# tools dump service id 10 spb default-multicast-list
saps : { }
spoke-sdps : { 95:10 }
*A:PE-63# tools dump service id 10 spb fid 10 forwarding-path destination PE-64 forwarding-tree unicast
Hop BridgeId Metric From Src
0 PE-63 0
1 PE-65 10
2 PE-67 20
3 PE-64 30
*A:PE-63# tools dump service id 10 spb fid 10 forwarding-path destination PE-64 forwarding-tree multicast
Hop BridgeId Metric From Src
0 PE-63 0
1 PE-65 10
2 PE-67 20
3 PE-64 30
*A:PE-65# tools dump service vpls-mfib-stats
Service Manager VPLS MFIB info at 004 09:44:57.010:
Statistics last cleared at 000 00:00:00.000
Statistic | Count
---------------------------------+-------------
HW limit SG entries | 40959 # total number of MFIB entries
Current SG entries | 2
Limit Non PBB SG entries | 16383 # IP Multicast MFIB limit
Current Non PBB SG entries | 0
...
*A:PE-65# tools dump service vpls-pbb-mfib-stats detail
Service Manager VPLS PBB MFIB statistics at 004 09:45:13.860:
Usage per Service
ServiceId MFIB User Count
------------+--------------+-------
10 spb 1
30 spb 1
------------+--------------+-------
Total 2
MMRP
Current Usage : 0
System Limit : 8191 Full, 40959 ESOnly
Per Service Limit : 2048 Full, 8192 ESOnly
SPB
Current Usage : 2
System Limit : 8191
Per Service Limit : 8191
Figure 83 illustrates the control B-VPLS (B-VPLS 20) and user B-VPLS (B-VPLS 21) concept (in this case there is only one user B-VPLS but there might be many B-VPLS sharing fate with the same control B-VPLS). Note that both B-VPLS must share the same topology and both B-VPLS must share exactly the same interfaces. The user B-VPLS, which is linked to the control B-VPLS by its FID, follows (that is, inherits the state of) the control B-VPLS but may use a different ECT path in case of equal metric paths, like in this example: FID 20, that is, the control B-VPLS, follows the low-path-id ECT, whereas FID 21, for example, the user B-VPLS, follows the high-path-id ECT.
The configurations of B-VPLSs 20 and 21, on PE-63 and PE-65, are shown below. The spbm-control-vpls 20 fid 21 in B-VPLS 21 command associates FID 21 to the user B-VPLS and links the B-VPLS to its control B-VPLS 20.
*A:PE-63>config>service# info
----------------------------------------------
...
vpls 20 customer 1 b-vpls create
service-mtu 2000
stp
shutdown
exit
spb 1025 fid 20 create
level 1
ect-algorithm fid-range 21-4095 high-path-id
exit
no shutdown
exit
spoke-sdp 35:20 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 36:20 create
spb create
no shutdown
exit
no shutdown
exit
no shutdown
exit
vpls 21 customer 1 b-vpls create
service-mtu 2000
stp
shutdown
exit
spbm-control-vpls 20 fid 21
spoke-sdp 35:21 create
no shutdown
exit
spoke-sdp 36:21 create
no shutdown
exit
no shutdown
exit
epipe 211 customer 1 create
pbb
tunnel 21 backbone-dest-mac "PE-64" isid 211
exit
sap 1/1/1:211 create
exit
no shutdown
exit
...
*A:PE-65>config>service# info
----------------------------------------------
...
vpls 20 customer 1 b-vpls create
service-mtu 2000
stp
shutdown
exit
spb 1025 fid 20 create
level 1
ect-algorithm fid-range 21-4095 high-path-id
exit
no shutdown
exit
spoke-sdp 53:20 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 56:20 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 57:20 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 59:20 create
spb create
no shutdown
exit
no shutdown
exit
no shutdown
exit
vpls 21 customer 1 b-vpls create
service-mtu 2000
stp
shutdown
exit
spbm-control-vpls 20 fid 21
spoke-sdp 53:21 create
no shutdown
exit
spoke-sdp 56:21 create
no shutdown
exit
spoke-sdp 57:21 create
no shutdown
exit
spoke-sdp 59:21 create
no shutdown
exit
no shutdown
exit
*A:PE-63# show service id 21 spb fate-sharing
===============================================================================
User service fate-shared sap/sdp-bind information
===============================================================================
Control Control Sap/ FID User User Sap/
SvcId SdpBind SvcId SdpBind
-------------------------------------------------------------------------------
20 35:20 21 21 35:21
20 36:20 21 21 36:21
===============================================================================
|
•
|
send-flush-on-failure works as expected when SPB is used at the B-VPLS. When configured, a flush-all-from-me event is triggered upon a SAP or spoke-sdp failure in the I-VPLS.
|
|
•
|
send-bvpls-flush works as expected when SPB is used at the B-VPLS. Two variants are configurable: all-from-me/all-but-mine. Any I-VPLS SAP/spoke-sdp failure is propagated to the I-VPLS on the peers to flush their respective customer MACs (CMACs). It works only in conjunction with send-flush-on-failure configuration on I-VPLS. The associated ISID list is passed along with the LDP mac-flush message, which is flushed/retained according to the all-from-me/all-but-me flag.
|
|
•
|
send-flush-on-bvpls-failure works as expected when SPB is used at the B-VPLS. A local B-VPLS failure is propagated to the I-VPLS, which then triggers a LDP mac-flush if it has any spoke-sdp on it.
|
|
•
|
propagate-mac-flush-from-bvpls does no work when SPB is used at the B-VPLS (since failures within the B-VPLS are handled by SPB) and its configuration is blocked.
|
*A:PE-65>config>redundancy# info
----------------------------------------------
multi-chassis
peer 192.0.2.66 create
mc-lag
lag 1 lacp-key 1 system-id 00:00:00:00:65:66
system-priority 65535 source-bmac-lsb use-lacp-key
no shutdown
exit
no shutdown
exit
exit
----------------------------------------------
*A:PE-65>config>service# info
----------------------------------------------
pbb
source-bmac 00:00:00:ca:fe:65
mac-name "PE-63" 00:00:00:ca:fe:63
mac-name "PE-64" 00:00:00:ca:fe:64
mac-name "PE-65" 00:00:00:ca:fe:65
mac-name "PE-66" 00:00:00:ca:fe:66
mac-name "PE-67" 00:00:00:ca:fe:67
mac-name "PE-69" 00:00:00:ca:fe:69
exit
...
vpls 30 customer 1 b-vpls create
service-mtu 2000
pbb
use-sap-bmac
exit
stp
shutdown
exit
spb 1026 fid 30 create
level 1
bridge-priority 0
exit
no shutdown
exit
spoke-sdp 53:30 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 56:30 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 57:30 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 59:30 create
spb create
no shutdown
exit
no shutdown
exit
no shutdown
exit
epipe 31 customer 1 create
pbb
tunnel 30 backbone-dest-mac "PE-63" isid 31
exit
sap lag-1:31 create
exit
no shutdown
exit
...
*A:PE-66# show service id 30 spb fdb
==============================================================================
User service FDB information
==============================================================================
MAC Addr UCast Source State MCast Source State
------------------------------------------------------------------------------
00:00:00:ca:00:01 65:30 ok 65:30 ok
00:00:00:ca:fe:63 63:30 ok 65:30 ok
00:00:00:ca:fe:65 65:30 ok 65:30 ok
00:00:00:ca:fe:67 67:30 ok 65:30 ok
00:00:00:ca:fe:69 69:30 ok 65:30 ok
------------------------------------------------------------------------------
Entries found: 5
==============================================================================
A:PE-64>config>service>vpls# info
----------------------------------------------
stp
shutdown
exit
endpoint "CORE" create
no suppress-standby-signaling
exit
sap 1/1/1:32 create
exit
spoke-sdp 47:32 endpoint "CORE" create
stp
shutdown
exit
precedence primary
no shutdown
exit
spoke-sdp 49:32 endpoint "CORE" create
stp
shutdown
exit
no shutdown
exit
no shutdown
----------------------------------------------
*A:PE-67>config>service# info
----------------------------------------------
...
vpls 30 customer 1 b-vpls create
service-mtu 2000
stp
shutdown
exit
spb 1026 fid 30 create
no shutdown
exit
spoke-sdp 75:30 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 76:30 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 79:30 create
spb create
no shutdown
exit
no shutdown
exit
no shutdown
exit
vpls 32 customer 1 i-vpls create
send-flush-on-failure
pbb
backbone-vpls 30
exit
send-bvpls-flush all-from-me
send-flush-on-bvpls-failure
exit
stp
shutdown
exit
spoke-sdp 74:32 create
no shutdown
exit
no shutdown
exit
As discussed, send-flush-on-failure and
send-bvpls-flush all-from-me are configured in the I-VPLS. When the active spoke-sdp goes down on PE-67, a flush-all-from-me message will be propagated through the backbone and will flush the corresponding CMACs associated to the I-VPLS 32 in node PE-63. MAC flush-all-from-me messages are automatically propagated in the core up to the remote I-VPLS 32 on node PE-63 (there is no need for any propagate-mac-flush in the intermediate nodes). Note that the
send-flush-on-bvpls-failure command works as expected. The command
propagate-mac-flush-from-bvpls is never used when the B-VPLS is SPB-enabled (the command is not allowed).
*A:PE-67# configure service vpls 40 static-mac mac ?
- mac <ieee-address> [create] sap <sap-id> [monitor {fwd-status}]
- no mac <ieee-address>
- mac <ieee-address> [create] spoke-sdp <sdp-id:vc-id> [monitor {fwd-status}]
*A:PE-67# configure service vpls 40 sap lag-1:40 static-isid range
- no range <range-id>
- range <range-id> isid <isid-value> [to <isid-value>] [create]
<range-id> : [1..8191]
<isid-value> : [1..16777215]
<create> : keyword
Note that the monitor fwd-status attribute identifies this to be a conditional MAC and is mandatory for static BMACs. This parameter instructs the 7x50 to advertise the BMAC only if the corresponding SAP/spoke-sdp is in forwarding state.
*A:PE-67>config>service # info
----------------------------------------------
...
vpls 40 customer 1 b-vpls create
service-mtu 2000
stp
shutdown
exit
spb 1027 fid 40 create
spf-wait 10 10 1000
no shutdown
exit
sap lag-1:40 create
static-isid
range 1 create isid 41
exit
exit
spoke-sdp 75:40 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 76:40 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 79:40 create
spb create
no shutdown
exit
no shutdown
exit
static-mac
mac 00:00:00:ca:fe:63 create sap lag-1:40 monitor fwd-status
exit
no shutdown
exit
----------------------------------------------
*A:PE-69>config>service# info
...
vpls 40 customer 1 b-vpls create
service-mtu 2000
stp
shutdown
exit
spb 1027 fid 40 create
spf-wait 10 10 1000
no shutdown
exit
sap lag-1:40 create
static-isid
range 1 create isid 41
exit
exit
spoke-sdp 95:40 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 96:40 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 97:40 create
spb create
no shutdown
exit
no shutdown
exit
static-mac
mac 00:00:00:ca:fe:63 create sap lag-1:40 monitor fwd-status
exit
no shutdown
exit
----------------------------------------------
*A:PE-67# show lag 1
===============================================================================
Lag Data
===============================================================================
Lag-id Adm Opr Port-Threshold Up-Link-Count MC Act/Stdby
-------------------------------------------------------------------------------
1 up up 0 1 active
===============================================================================
*A:PE-67# show service id 40 fdb pbb
=======================================================================
Forwarding Database, b-Vpls Service 40
=======================================================================
MAC Source-Identifier iVplsMACs Epipes Type/Age
-----------------------------------------------------------------------
00:00:00:ca:fe:63 sap:lag-1:40 0 0 CStatic
00:00:00:ca:fe:65 sdp:75:40 0 0 Spb
00:00:00:ca:fe:66 sdp:76:40 0 0 Spb
00:00:00:ca:fe:69 sdp:79:40 0 0 Spb
=======================================================================
*A:PE-69# show lag 1
===============================================================================
Lag Data
===============================================================================
Lag-id Adm Opr Port-Threshold Up-Link-Count MC Act/Stdby
-------------------------------------------------------------------------------
1 up down 0 0 standby
===============================================================================
*A:PE-69# show service id 40 fdb pbb
=======================================================================
Forwarding Database, b-Vpls Service 40
=======================================================================
MAC Source-Identifier iVplsMACs Epipes Type/Age
-----------------------------------------------------------------------
00:00:00:ca:fe:63 sdp:97:40 0 0 Spb
00:00:00:ca:fe:65 sdp:95:40 0 0 Spb
00:00:00:ca:fe:66 sdp:96:40 0 0 Spb
00:00:00:ca:fe:67 sdp:97:40 0 0 Spb
=======================================================================
*A:PE-66# show service id 40 spb fdb
==============================================================================
User service FDB information
==============================================================================
MAC Addr UCast Source State MCast Source State
------------------------------------------------------------------------------
00:00:00:ca:fe:63 67:40 ok 65:40 ok
00:00:00:ca:fe:65 65:40 ok 65:40 ok
00:00:00:ca:fe:67 67:40 ok 65:40 ok
00:00:00:ca:fe:69 69:40 ok 65:40 ok
------------------------------------------------------------------------------
Entries found: 4
==============================================================================
*A:PE-66# show service id 40 spb mfib
===============================================================================
User service MFIB information
===============================================================================
MAC Addr ISID Status
-------------------------------------------------------------------------------
01:1E:83:00:00:29 41 Ok
-------------------------------------------------------------------------------
Entries found: 1
===============================================================================
*A:PE-66# show service id 40 mfib
===============================================================================
Multicast FIB, Service 40
===============================================================================
Source Address Group Address Sap/Sdp Id Svc Id Fwd/Blk
-------------------------------------------------------------------------------
* 01:1E:83:00:00:29 b-sdp:65:40 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 1
===============================================================================
*A:PE-69># show service id 40 sap lag-1:40 static-isids
===================================
Static Isid Entries
===================================
Entry Range
-----------------------------------
1 41-100
===================================
*A:PE-67>config>service>vpls# isid-policy entry ?
- entry <range-entry-id> [create]
- no entry <range-entry-id>
<range-entry-id> : [1..8191]
<create> : keyword
[no] advertise-local - Configure local advertisement of the range
[no] range - Configure ISID range for the entry
[no] use-def-mcast - Use default multicast tree to propogate ISID range
|
•
|
advertise-local defines whether the local ISIDs (I-VPLS ISIDs linked to the B-VPLS) or static ISIDs contained in the configured range are advertised in SPBM.
|
|
•
|
use-def-mcast controls whether the ISIDs contained in the range use MFIB entries (if no use-def-mcast is used) or just the default tree which does not use any MFIB entry.
|
The isid-policy becomes active as soon as it is defined, as opposed to other policies in SR OS, which require the policy itself to be applied within the configuration.
The following configuration example will use the test topology in Figure 85. In this case, the objective of the
isid-policy will be to use the default tree for all the I-VPLS services with ISIDs between 41 and 100, excluding the range 80-90. The following example shows the policy configuration in PE-67. Note that the same policy will be configured in the rest of the SPB nodes, that is, PE-65, PE-66 and PE-69.
*A:PE-67>config>service# vpls 40
*A:PE-67>config>service>vpls# info
----------------------------------------------
service-mtu 2000
stp
shutdown
exit
spb 1027 fid 40 create
spf-wait 10 10 1000
no shutdown
exit
isid-policy
entry 10 create
range 80 to 90
exit
entry 20 create
use-def-mcast
no advertise-local
range 41 to 79
exit
entry 30 create
use-def-mcast
no advertise-local
range 91 to 100
exit
exit
sap lag-1:40 create
static-isid
range 1 create isid 41 to 100
exit
exit
spoke-sdp 75:40 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 76:40 create
spb create
no shutdown
exit
no shutdown
exit
spoke-sdp 79:40 create
spb create
no shutdown
exit
no shutdown
exit
static-mac
mac 00:00:00:ca:fe:63 create sap lag-1:40 monitor fwd-status
exit
no shutdown
----------------------------------------------
Note that the no advertise-local option can only be configured if the
use-def-mcast option is also configured.
*A:PE-67>config>service>vpls>isid-policy>entry# no advertise-local
MINOR: SVCMGR #7855 Cannot set AdvLocal for entry - advertise-local or use-def-mcast option must be specified
*A:PE-67>config>service>vpls>isid-policy>entry# use-def-mcast
MINOR: SVCMGR #7854 Cannot set UseDefMctree for entry - Conflicting Actions with Entry-20
*A:PE-65# show service id 40 spb database detail
===============================================================================
ISIS Database
===============================================================================
Displaying Level 1 database
-------------------------------------------------------------------------------
LSP ID : PE-65.00-00 Level : L1
...
-------------------------------------------------------------------------------
LSP ID : PE-66.00-00 Level : L1
...
-------------------------------------------------------------------------------
LSP ID : PE-67.00-00 Level : L1
…
MT Capability :
TLV Len : 56
MT ID : 0
SPBM Service ID:
Sub TLV Len : 52
BMac Addr : 00:00:00:ca:fe:67
Base VID : 40
ISIDs :
80 Flags:TR
81 Flags:TR
82 Flags:TR
83 Flags:TR
84 Flags:TR
85 Flags:TR
86 Flags:TR
87 Flags:TR
88 Flags:TR
89 Flags:TR
90 Flags:TR
...
-------------------------------------------------------------------------------
LSP ID : PE-69.00-00 Level : L1
...
Level (1) LSP Count : 4
===============================================================================
The mfib parameter in the
show service id 40 sap static-isids mfib command can help understand the state of the MFIB entries added (or not) by the configured static-isid. The following possible states can be shown:
*A:PE-69# show service id 40 sap lag-1:40 static-isids mfib
===================================
ISID Detail
===================================
ISID Status
-----------------------------------
<<snip>>
80 ok
81 ok
<<snip>>
41 useDefMCTree
42 useDefMCTree
<<snip>>
8292 sysMFibLimit
8293 sysMFibLimit
<<snip>>
9253 addPending
9254 addPending
<<snip>>
===================================
