•
|
OMCR — Oversubscribed Multi-Chassis Redundancy
|
•
|
Warm-Standby Node or Protecting Node — Refers to the oversubscribed node that offers the protection of subscriber hosts spread over multiple BNGs. During the normal operation, the protecting node maintains the subscriber host in the form of an MCS record (Multi-Chassis Synchronization Record) in the control plane. Only when the failure occurs and the protecting node becomes active, are the subscriber-hosts fully instantiated in the data and control plane. This node is sometimes referred to as N:1 node.
|
•
|
Active/Active (1:1) Model — This mode of operation refers to the model where subscribers host are fully synchronized between two chassis, regardless of the state of the undelaying SRRP instance (Master/Standby). Each node can have MCS peering sessions with four another nodes where each peering session represent 1 to 1 mapping set of active subscriber hosts.
|
The number of the subscriber hosts that failed to instantiate, can also be determined via the operational show redundancy multi-chassis omcr all command. This command will show the number of subscribers that failed to instantiate along with SRRP instances on which the subscriber host are relaying for successful connectivity.
The Available Memory gives an indication about how much memory remains.
*A:right-21# show system memory-pools
===============================================================================
Memory Pools
===============================================================================
Name Max Allowed Current Size Max So Far In Use
-------------------------------------------------------------------------------
BFD No limit 6,291,456 6,291,456 5,509,872
BGP No limit 5,242,880 5,242,880 3,635,976
CFLOWD No limit 1,048,576 1,048,576 26,576
Cards & Ports No limit 24,117,248 27,262,976 18,010,424
DHCP Server No limit 2,097,152 2,097,152 173,680
ETH-CFM No limit 6,291,456 9,437,184 4,016,128
ICC 25,165,824 7,340,032 25,165,824 2,880,008
IGMP/MLD No limit 1,048,576 1,048,576 166,216
IMSI Db Appl No limit 1,048,576 1,048,576 793,984
IOM No limit 8,388,608 8,388,608 6,894,360
IP Stack No limit 29,360,128 35,651,584 13,565,120
IS-IS No limit 2,097,152 2,097,152 1,095,360
ISA No limit 3,145,728 3,145,728 1,217,464
LDP No limit 6,291,456 6,291,456 5,607,240
Logging 411,041,792 6,291,456 6,291,456 3,473,024
MBUF 1,073,741,824 2,097,152 2,097,152 299,976
MCS No limit 454,033,408 454,033,408 416,753,472
MPLS/RSVP No limit 49,283,072 69,206,016 42,947,776
MSCP No limit 2,097,152 2,097,152 1,022,848
MSDP No limit 0 0 0
Management No limit 19,922,944 26,214,400 5,689,112
OAM No limit 1,048,576 1,048,576 86,080
OSPF No limit 8,388,608 8,388,608 4,975,824
OpenFlow No limit 1,048,576 1,048,576 391,880
PIM No limit 19,922,944 19,922,944 15,755,792
PTP No limit 1,048,576 1,048,576 1,408
RIP No limit 0 0 0
RTM/Policies No limit 9,437,184 9,437,184 7,002,648
Redundancy No limit 9,437,184 424,673,280 703,160
SIM No limit 3,145,728 12,582,912 648
Services No limit 25,165,824 25,165,824 18,128,056
Stats No limit 1,048,576 1,048,576 9,456
Subscriber Mgmt No limit 24,117,248 41,943,040 14,846,512
System No limit 794,820,608 856,686,592 776,394,656
Traffic Eng No limit 1,048,576 1,048,576 444,744
VRRP No limit 2,097,152 3,145,728 393,808
WEB Redirect 16,777,216 1,048,576 1,048,576 128,640
-------------------------------------------------------------------------------
Current Total Size : 1,540,358,144 bytes
Total In Use : 1,373,041,928 bytes
Available Memory : 5,778,702,336 bytes
===============================================================================
*A:right-21# show system cpu
===============================================================================
CPU Utilization (Sample period: 1 second)
===============================================================================
Name CPU Time CPU Usage Capacity
(uSec) Usage
-------------------------------------------------------------------------------
BFD 0 0.00% 0.00%
BGP 2,504 0.03% 0.05%
BGP PE-CE 0 0.00% 0.00%
CFLOWD 25 ~0.00% ~0.00%
Cards & Ports 14,501 0.18% 0.13%
DHCP Server 30 ~0.00% ~0.00%
ETH-CFM 614 ~0.00% 0.06%
ICC 1,803 0.02% 0.18%
IGMP/MLD 538 ~0.00% 0.05%
IMSI Db Appl 37 ~0.00% ~0.00%
IOM 0 0.00% 0.00%
IP Stack 4,578 0.05% 0.24%
IS-IS 423 ~0.00% 0.02%
ISA 2,690 0.03% 0.10%
LDP 78 ~0.00% ~0.00%
Logging 13 ~0.00% ~0.00%
MBUF 0 0.00% 0.00%
MCS 2,718 0.03% 0.27%
MPLS/RSVP 1,137 0.01% 0.08%
MSCP 0 0.00% 0.00%
MSDP 0 0.00% 0.00%
Management 6,571 0.08% 0.19%
OAM 1,532 0.01% 0.09%
OSPF 18,397 0.23% 0.08%
OpenFlow 18 ~0.00% ~0.00%
PIM 0 0.00% 0.00%
PTP 24 ~0.00% ~0.00%
RIP 0 0.00% 0.00%
RTM/Policies 0 0.00% 0.00%
Redundancy 3,618 0.04% 0.19%
SIM 10,959 0.13% 1.08%
SNMP Daemon 0 0.00% 0.00%
Services 1,037 0.01% 0.03%
Stats 0 0.00% 0.00%
Subscriber Mgmt 835 0.01% 0.03%
System 29,863 0.37% 1.32%
Traffic Eng 0 0.00% 0.00%
VRRP 970 0.01% 0.07%
WEB Redirect 26 ~0.00% ~0.00%
-------------------------------------------------------------------------------
Total 7,975,383 100.00%
Idle 7,869,844 98.67%
Usage 105,539 1.32%
Busiest Core Utilization 33,264 3.33%
===============================================================================
*A:right-21#
configure
redundancy
multi-chassis
peer 1.1.1.1
warm-standby
The warm-standby keyword configures the chassis to be in the central standby mode of operation. Although the configuration option is configured per peer, the
warm-standby functionality is applied per chassis.
Synchronization of IPoE subscribers (config>redundancy>multi-chassis>peer>sync>sub-mgmt ipoe) on the protecting node is only possible if all peers are configured for
warm-standby or none are.
Persistency in the multi-chassis environment must be disabled since redundant nodes are protecting each other and they maintain up-to-date lease states. Otherwise, race conditions resulting in stale lease states caused by contention between MCS data and persistency data may occur.
Case 1 — SRRP-Aware routing where subnets can be assigned per group-interfaces (SRRP instances). In a steady state, the redundant interface is not needed since the downstream traffic is attracted to the master node. During switchover periods (routing convergence transitioning periods), redundant interface can be used only for the subscriber hosts that are instantiated in the data plane (from the moment that they are instantiated in the dataplane when protecting node is assuming activity, or up the moment when they are withdrawn from the data plane when the protecting node is relinquishing activity). See
Figure 141.
Case 2 — SRRP-Aware routing where subnets spawn (are aggregated) over multiple group-interfaces (SRRP instances). In case of a switchover, /32 IPv4 addresses and /64 IPv6 addresses/prefixes are advertised from the protecting node. In a steady state, the redundant interface is not needed since the downstream traffic is attracted via more specific routes (/32s and /64s) to the master node. During switchover periods (routing convergence transitioning periods), the redundant interface can be used only for the subscriber-hosts that are instantiated in the data plane (from the moment that they are instantiated in the dataplane when protecting node is assuming activity, or up the moment when they are withdrawn from the data plane when the protecting node is relinquishing activity). To reduce the number of routes on the network side, /32s and /64s should only be activated on the protecting node.
In case that failure is repaired on the original active node (non-central standby node) while SRRP preemption (preempt) is configured, the corresponding active subscribers on the protecting node will be withdrawn from the data plane and the activity (mastership) will be switched to the original node.
•
|
For all protected SRRP instances, the protected node should be the preferred Master. To achieve this, the SRRP priority should be higher in the protected node than in the protecting node. SRRP preemption is recommended in the protecting node to force it to become Master when possible. Note that an SRRP switch from nonMaster to Master in the protected node does not suffer the slow convergence observed when the nonMaster -> Master transition takes place in the protecting node. This is because the protected node always has the hosts instantiated in the data plane.
|
•
|
It is recommended that the capture-sap configuration include the track-srrp statement (at least for the protecting node). With this configuration the CPM will not process trigger packets when the leases cannot be created because the SRRP is not in the Master state. Configuring SRRP tracking at the capture-sap will offload the CPM from performing false authentication and MSAP creation attempts.
|
•
|
In order to minimize traffic impact in the event of node reboot, it is recommended to use delayed-enable seconds command under the subscriber-interface and allow enough time for the MCS database to reconcile. This is particularly important in the protected node. If the SRRP becomes master in the protected node before the database has been reconciled, the protecting node will remove the leases (non-Master state) which have not been synchronized. This would create partial outage.
|
*A:right-21# show redundancy multi-chassis omcr all
===============================================================================
Domain Table
===============================================================================
Domain Domain SRRP SRRP Domain Instan. Failed Failed Reason
name state ID State Color Failed Hosts
-------------------------------------------------------------------------------
N/A N/A 201 Standby N/A not-act 0
N/A N/A 202 Standby N/A not-act 0
N/A N/A 203 Standby N/A not-act 0
N/A N/A 204 Standby N/A not-act 0
N/A N/A 301 Standby N/A not-act 0
N/A N/A 302 Standby N/A not-act 0
N/A N/A 303 Standby N/A not-act 0
N/A N/A 304 Standby N/A not-act 0
N/A N/A 401 Standby N/A not-act 0
N/A N/A 402 Standby N/A not-act 0
N/A N/A 403 Standby N/A not-act 0
N/A N/A 404 Standby N/A not-act 0
N/A N/A 501 Standby N/A not-act 0
N/A N/A 601 Standby N/A not-act 0
N/A N/A 701 Standby N/A not-act 0
N/A N/A 801 Standby N/A not-act 0
N/A N/A 901 Standby N/A not-act 0
N/A N/A 1001 Standby N/A not-act 0
N/A N/A 1101 Standby N/A not-act 0
-------------------------------------------------------------------------------
No. of Entries: 19
===============================================================================
*A:right-21#
*A:right-21# show srrp 1001 detail
===============================================================================
SRRP Instance 1001
===============================================================================
Description : (Not Specified)
Admin State : Up Oper State : backupRouting
Oper Flags : subnetMismatch
Preempt : yes One GARP per SAP : no
Monitor Oper Group : None
System IP : 10.20.1.1
Service ID : IES 2
Group If : grp.Dut-J.1 MAC Address : 00:00:61:ac:ac:0a
Grp If Description : N/A
Grp If Admin State : Up Grp If Oper State: Up
Subscriber If : ies-sub-if-svc-2
Sub If Admin State : Up Sub If Oper State: Up
Address : 102.1.0.1/16 Gateway IP : 102.1.0.3
Address : 102.2.0.1/16 Gateway IP : 102.2.0.3
Msg Path SAP : 8/2/2:2.4094
Admin Gateway MAC : 00:00:51:ac:0a:01 Oper Gateway MAC : 00:00:51:ac:0a:01
Config Priority : 1 In-use Priority : 1
Master Priority : 100
Keep-alive Interval : 10 deci-seconds Master Since : 02/11/2014 11:38:52
Master Down Interval: 3.000 sec (Expires in 2.700 sec)
Fib Population Mode : all
VRRP Policy 1 : None VRRP Policy 2 : None
OMCR Client status : Sub-mgmt-ipoe
Instantiation failed: not-act Failed IPOE Hosts: 0
OMCR Reason :
*A:right-21# show redundancy multi-chassis sync peer 10.20.1.6 detail
===============================================================================
Multi-chassis Peer Table
===============================================================================
Peer
-------------------------------------------------------------------------------
Peer IP Address : 10.20.1.6
Description : (Not Specified)
Authentication : Disabled
Source IP Address : 10.20.1.1
Admin State : Enabled
Warm standby : Yes
Remote warm standby : No
-------------------------------------------------------------------------------
Sync-status
-------------------------------------------------------------------------------
Client Applications : SUBMGMT-IPOE SRRP
Sync Admin State : Up
Sync Oper State : Up
Sync Oper Flags :
DB Sync State : inSync
Num Entries : 64026
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 64000
OMCR Alarm Entries : 0
Rem Num Entries : 64026
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
===============================================================================
MCS Application Stats
===============================================================================
Application : igmp
Num Entries : 0
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 0
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 0
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Application : igmpSnooping
Num Entries : 0
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 0
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 0
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Application : subMgmtIpoe
Num Entries : 64000
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 64000
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 64000
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Application : srrp
Num Entries : 26
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 0
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 26
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Application : mcRing
Num Entries : 0
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 0
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 0
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Application : mldSnooping
Num Entries : 0
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 0
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 0
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Application : dhcpServer
Num Entries : 0
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 0
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 0
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Application : subHostTrk
Num Entries : 0
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 0
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 0
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Application : subMgmtPppoe
Num Entries : 0
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 0
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 0
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Application : mcIpsec
Num Entries : 0
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 0
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 0
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Application : mld
Num Entries : 0
Lcl Deleted Entries : 0
Alarm Entries : 0
OMCR Standby Entries : 0
OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
Rem Num Entries : 0
Rem Lcl Deleted Entries : 0
Rem Alarm Entries : 0
Rem OMCR Standby Entries: 0
Rem OMCR Alarm Entries : 0
-------------------------------------------------------------------------------
===============================================================================
===============================================================================
Ports synced on peer 10.20.1.6
===============================================================================
Port/Encap Tag
-------------------------------------------------------------------------------
4/2/2
2.1-2.4094 Dut-F.1
===============================================================================
===============================================================================
DHCP Server instances synced on peer 10.20.1.6
===============================================================================
Router-Name Server-Name
Tag
-------------------------------------------------------------------------------
No instances found
===============================================================================
===============================================================================
*A:right-21#
*A:right-21# tools dump redundancy multi-chassis sync-database application sub-mgmt-ipoe peer 10.20.1.6
The following totals are for:
peer ip 10.20.1.6, port/lag ALL, sync-tag ALL, application SUBMGMT-IPOE
Valid Entries: 64000
Locally Deleted Entries: 0
Locally Deleted Alarmed Entries: 0
Pending Global Delete Entries: 0
Omcr Alarmed Entries: 0
Omcr Standby Entries: 64000
*A:right-21#