Introduction
G.8032v2 specifies support for a network of interconnected rings. This helps to add new ring on a already existing ring with G.8032 without much configuration changes.
Description:-
The recommendation defines basic terminology for interconnected rings.
See the topology below:-
Interconnection nodes –are the ring nodes that are common to both interconnected rings (SASX1 and SASX2) in the below figure. In this scenario the interconnected nodes should be a SASX running 4.0 R1 however there are plans to introduce this feature in SASM’s also in later 4.0 mantenance releases . The other nodes can be a combination of SASM and SASX and can run 3.0 or 4.0 versions.
Major Ring –An Ethernet ring that controls a full physical ring and is connected to the Interconnection nodes on two ports, the ring SASM3, SASM4, SASX1,SASX2 in the below figure. The R-APS messages from the major ring passes through the sub-ring however the reverse is not true. R-APS messages for the sub-ring are encapsulated and transmitted over a virtual channel on the Major ring.
Sub-Ring – An Ethernet ring that is connected to a Major Ring at the Interconnection Nodes. By itself, the Sub-Ring does not constitute a closed ring. A Sub-Ring is connected to the Interconnection nodes on only one port. The ring SASM1,SASM2, SASX1 and SASX2 in the figure. Sub-Ring does not control or directly transfer R-APS messages over the link between the Interconnection Nodes (this is under the control of the Major Ring) however it uses a a identical protection mechanism as the the major ring.
ð Major ring and sub-ring can also be connected without the virtual channel in this case the R-APS messages from the sub-ring does not travel to the sub-ring, R-APS messages are not blocked at RPL of the Sub-Ring.
ð Allows Multi-Chassis access (termination into multi-homed VPLS).
ð Offers less redundancy since R-APS messages are not propagated across the Major Ring.
Configuration:-
First we need to configure Y.1731 on the SASM and the SASX devices as given below.
*A:SASM3>config>eth-cfm# info
----------------------------------------------
domain 1 format none level 1
association 5 format icc-based name "major12345678"
exit
ccm-interval 100ms
remote-mepid 11
exit
association 6 format icc-based name "major87654321"
exit
ccm-interval 100ms
remote-mepid 13
exit
exit
----------------------------------------------
Please Note:- Association 5 is connected between SASM3 and SASM4 and association 6 is configured between SASM3 and SASX1. The minimum CCM interval supported in y.1731 is 100ms.
*A:SASM4>config>eth-cfm# info
----------------------------------------------
domain 1 format none level 1
association 5 format icc-based name "major12345678"
exit
ccm-interval 100ms
remote-mepid 10
exit
association 7 format icc-based name "major-minor12"
exit
ccm-interval 100ms
remote-mepid 15
exit
exit
----------------------------------------------
Please Note:- Association 7 is between SASM4 and SASX2.
*A:x2>config>eth-cfm# info
----------------------------------------------
domain 1 format none level 1
association 3 format icc-based name "samratdutta12"
exit
ccm-interval 100ms
remote-mepid 5
exit
association 4 format icc-based name "SAS1234567890"
exit
ccm-interval 100ms
remote-mepid 4
exit
association 7 format icc-based name "major-minor12"
exit
ccm-interval 100ms
remote-mepid 14
exit
exit
----------------------------------------------
*A:x1>config>eth-cfm#
Please Note:- Association 3 is between SASX1 and SASX2 and association 4 is between SASX2 and SASM2.
*A:SASX1>config>eth-cfm# info
----------------------------------------------
domain 1 format none level 1
association 2 format icc-based name "minor12345678"
exit
ccm-interval 100ms
remote-mepid 3
exit
association 3 format icc-based name "samratdutta12"
exit
ccm-interval 100ms
remote-mepid 6
exit
association 6 format icc-based name "major87654321"
exit
ccm-interval 100ms
remote-mepid 12
exit
exit
----------------------------------------------
Please Note:- Association 2 is between SASX1 and SASM1.
*A:sasm1>config>eth-cfm# info
----------------------------------------------
domain 1 format none level 1
association 1 format icc-based name "minor87654321"
exit
ccm-interval 100ms
remote-mepid 2
exit
association 2 format icc-based name "minor12345678"
exit
ccm-interval 100ms
remote-mepid 4
exit
exit
----------------------------------------------
*A:x3>config>eth-cfm#
Please Note:- Association 1 is between SASM1 and SASM2.
*A:sasm2>config>eth-cfm# info
----------------------------------------------
domain 1 format none level 1
association 1 format icc-based name "minor87654321"
exit
ccm-interval 100ms
remote-mepid 1
exit
association 4 format icc-based name "SAS1234567890"
exit
ccm-interval 100ms
remote-mepid 7
exit
exit
--------------------------------------------
Please Note:- All the domains configured in all the above scenarios is domain 1.
Verification:-
Verify that the Y.1731 neighbors are all up.
*A:SASM3>config>eth-ring# show eth-cfm mep 10 domain 1 association 5
-------------------------------------------------------------------------------
Mep Information
-------------------------------------------------------------------------------
Md-index : 1 Direction : Down
Ma-index : 5 Admin : Enabled
MepId : 10 CCM-Enable : Enabled
IfIndex : 35880960 PrimaryVid : 10
FngState : fngReset ControlMep : True
LowestDefectPri : macRemErrXcon HighestDefect : none
Defect Flags : None
Mac Address : 00:25:ba:06:8f:38 CcmLtmPriority : 7
CcmTx : 0 CcmSequenceErr : 0
Eth-1Dm Threshold : 3(sec)
Eth-Ais: : Disabled
Eth-Tst: : Disabled
CcmLastFailure Frame:
None
XconCcmFailure Frame:
None
The above command should be executed in all the nodes and the highest defect should be none.
Next we should configure the eth-ring, the major eth-ring configured is 4 and the minor eth-ring configured is 2.
*A:SASM3>config# eth-ring 2
*A:SASM3>config>eth-ring# info
----------------------------------------------
rpl-node owner
path a 1/1/7 raps-tag 10
rpl-end
eth-cfm
mep 10 domain 1 association 5
ccm-enable
control-mep
no shutdown
exit
exit
no shutdown
exit
path b 1/1/8 raps-tag 10
eth-cfm
mep 12 domain 1 association 6
ccm-enable
control-mep
no shutdown
exit
exit
no shutdown
exit
no shutdown
----------------------------------------------
*A:SASM3>config>eth-ring#
Please Note:- This node is the rpl owner in the major ring hence the path a 1/1/7 will be blocked.
*A:SASM4# configure eth-ring 2
*A:SASM4>config>eth-ring# info
----------------------------------------------
path a 1/1/7 raps-tag 10
eth-cfm
mep 11 domain 1 association 5
ccm-enable
control-mep
no shutdown
exit
exit
no shutdown
exit
path b 1/1/9 raps-tag 10
eth-cfm
mep 14 domain 1 association 7
ccm-enable
control-mep
no shutdown
exit
exit
no shutdown
exit
no shutdown
----------------------------------------------
*A:SASM4>config>eth-ring#
Same needs to be configured on the interconnection nodes SASX1 and SASX2.
----------------------------------------------
*A:SASX1>config# eth-ring 2
*A:SASX1>config>eth-ring# info
----------------------------------------------
path a 1/1/8 raps-tag 10
eth-cfm
mep 13 domain 1 association 6
ccm-enable
control-mep
no shutdown
exit
exit
no shutdown
exit
path b 1/1/7 raps-tag 10
eth-cfm
mep 5 domain 1 association 3
ccm-enable
control-mep
no shutdown
exit
exit
no shutdown
exit
no shutdown
----------------------------------------------
*A:SASX1>config>eth-ring#
*A:x2# configure eth-ring 2
*A:x2>config>eth-ring# info
----------------------------------------------
path a 1/1/7 raps-tag 10
eth-cfm
mep 6 domain 1 association 3
ccm-enable
control-mep
no shutdown
exit
exit
no shutdown
exit
path b 1/1/9 raps-tag 10
eth-cfm
mep 15 domain 1 association 7
ccm-enable
control-mep
no shutdown
exit
exit
no shutdown
exit
no shutdown
----------------------------------------------
*A:x1>config>eth-ring#
A vpls service should be configured for the control traffic for the major ring.
*A:SASM3# configure service vpls 100
*A:SASM3>config>service>vpls# info
----------------------------------------------
description "control traffic for major ring"
stp
shutdown
exit
sap 1/1/7:10 eth-ring 2 create
stp
shutdown
exit
exit
sap 1/1/8:10 eth-ring 2 create
stp
shutdown
exit
exit
no shutdown
----------------------------------------------
Please Note:- The raps tag value and the dot1q value in the control service should match.
This needs to configured on all the routers in the major ring as well as the minor ring.
*A:SASM4>config>service>vpls# info
----------------------------------------------
description "control traffic for major ring"
stp
shutdown
exit
sap 1/1/7:10 eth-ring 2 create
stp
shutdown
exit
exit
sap 1/1/9:10 eth-ring 2 create
stp
shutdown
exit
exit
no shutdown
----------------------------------------------
*A:SASM4>config>service>vpls#
*A:SASX1>config>service# vpls 100
*A:SASX1>config>service>vpls# info
----------------------------------------------
description " control traffic for major ring"
stp
shutdown
exit
sap 1/1/7:10 eth-ring 2 create
stp
shutdown
exit
exit
sap 1/1/8:10 eth-ring 2 create
stp
shutdown
exit
exit
no shutdown
----------------------------------------------
*A:SASX1>config>service>vpls#
*A:x2>config>service# vpls 100
*A:x2>config>service>vpls# info
----------------------------------------------
description "Control traffic for major ring"
stp
shutdown
exit
sap 1/1/7:10 eth-ring 2 create
stp
shutdown
exit
exit
sap 1/1/9:10 eth-ring 2 create
stp
shutdown
exit
exit
no shutdown
----------------------------------------------
*A:x2>config>service>vpls#
Configuring Sub-rings:-
No comments:
Post a Comment