Cisco Systems 3.5 RepType, RepTransactionSyncInterval, RepTransactionArchiveLimit, Master, Slave

Page 44

Chapter 4 Understanding Replication

Replication Configuration Settings

RepType

RepType indicates the type of replication. The choices available are SMDBR and NONE.

When RepType is set to NONE, replication is disabled. To enable replication, set RepType to SMDBR for Single Master DataBase Replication. RepType must be set to SMDBR on both the master and slave servers.

RepTransactionSyncInterval

Master

On the master server, RepTransactionSyncInterval is the duration between periodic transmission of the TransactionSync message expressed in milliseconds. The default is 60000 or 1 minute.

The purpose of RepTransactionSyncInterval is to indicate how frequently to check for an out-of -sync condition between the master and slave servers. When the slave received the TransactionSync message, it uses its contents to determine if it needs to resynchronize with the master.

The larger the setting for RepTransactionSyncInterval, the longer the period of time between out-of-sync detection. However, if RepTransactionSyncInterval is set too small, the slave may frequently request resynchronization when it is not really out of sync. If the duration is too small, the slave cannot completely receive a transaction before it receives the TransactionSync message. In this case, the servers will remain synchronized, but there will be unnecessary excess traffic that could affect performance.

Slave

On the slave, RepTransactionSyncInterval is used to determine if the slave has lost contact with the master and to alert administrators of a possible loss of connectivity between the master an slave. If the elapsed time since the last received TransactionSync message exceeds the setting of RepTransactionSyncInterval, the slave writes a log message indicating that it may have lost contact with the master. This log message is repeated each TransactionSyncInterval until a TransactionSync message is received.

RepTransactionArchiveLimit

On both master and slave, the RepTransactionArchiveLimit setting determines how many transactions can be stored in the archive. The default setting is 100. When the limit is exceeded, the oldest transaction file is deleted. If a slave requires resynchronization and the last transaction it received is no longer in the archive, a full resynchronization will be necessary to bring the slave back in sync with the master.

Note The value set for RepTransactionArchiveLimit should be the same on the master and the slave.

An appropriate value for RepTransactionArchiveLimit depends upon how much hard disk space an administrator can provide for resynchronization. If this value is large, say 10,000, then the last 10,000 transactions will be stored in the archive. This is like saying the last 10,000 saves from aregcmd will be stored in the archive. Large values are best. The size of each transaction depends upon how many configuration changes were included in the transaction, so hard disk space usage is difficult to estimate.

Cisco Access Registrar 3.5 Concepts and Reference Guide

4-6

OL-2683-02

 

 

Page 43 Page 45
Image 44
Page 43 Page 45
Contents Cisco Access Registrar 3.5 Concepts and Reference Guide Corporate HeadquartersCisco Access Registrar 3.5 Concepts and Reference Guide N T E N T S IiiSession-Service Service Step and Radius-Session Service Replication’s Impact on Request Processing IPAddress Port Understanding Snmp Accounting Start Data Flow ViiViii Obtaining Documentation World Wide WebObtaining Technical Assistance Ordering DocumentationDocumentation Feedback Cisco.comContacting TAC by Telephone Contacting TAC by Using the Cisco TAC WebsiteTechnical Assistance Center Xii Overview Radius ProtocolSteps to Connection Packet Exchange Between User, NAS, and RadiusPacket Contents Types of Radius MessagesProxy Servers Attribute DictionaryBasic Authentication and Authorization Proxying to an Ldap Server for AuthenticationOverview Basic Authentication and Authorization Understanding Cisco Access Registrar Cisco Access Registrar HierarchyServices UserLists and GroupsProfiles ScriptsSession Management Using Resource Managers Subdirectory Description Cisco AR Directory StructureProgram Flow Scripting Points Client or NAS Scripting PointsCisco AR Server Action Explanation Action ExplanationAuthentication and/or Authorization Scripting Points Radius/Advanced/RequireNASsBehindProxyBeInClieSession Management Failover by the NAS and Session ManagementIncoming Scripts Authentication/Authorization ScriptsScript Processing Hierarchy Outgoing Scripts Cross Server Session and Resource ManagementOverview Session-Service Service Step and Radius-Session Service Configuring a Front Line Cisco Access RegistrarConfigure Central AR OL-2683-02 AltigaIncomingScript Using Cisco AR ScriptsACMEOutgoingScript AuthorizeService AltigaOutgoingScriptANAAAOutgoing AscendIncomingScriptAuthorizeTelnet CabletronIncomingCabletronOutgoing CiscoIncomingExecTimeRule ExecDNISRuleExecFilterRule ExecNASIPRuleLDAPOutage MapSourceIPAddressParseAAARealm ParseAAASRealmParseServiceAndAAARealmHints ParseServiceAndAAASRealmHintsParseServiceAndAARealmHints ParseServiceAndAASRealmHintsParseServiceHints ParseTranslationGroupsByCLIDParseTranslationGroupsByDNIS ParseTranslationGroupsByRealmUSROutgoingScript Understanding Replication Replication OverviewMaster Server How Replication WorksReplication Data Flow Security Replication ArchiveEnsuring Data Integrity Slave ServerAutomatic Resynchronization Transaction Data VerificationTransaction Order Replication Configuration Settings Understanding Hot-ConfigurationFull Resynchronization Replication’s Impact on Request ProcessingRepType RepTransactionSyncIntervalRepTransactionArchiveLimit MasterRepIPAddress RepPortRepSecret RepIPMasterRep Members Subdirectory Rep Members/Slave1Name IPAddressOverview Supported MIBsSnmp Traps RADIUS-AUTH-SERVER-MIBSupported Traps CarServerStartCarServerStop CarInputQueueFullCarOtherAccServerNotResponding CarOtherAuthServerNotRespondingCarOtherAuthServerResponding Configuring Traps CarOtherAccServerRespondingCarAccountingLoggingFailure Directories SearchedConfiguration File Types Switching Configuration Files in Mid-FileCommunity String OL-2683-02 Prepaid Billing Solution Measurements and Component Actions Configuring Prepaid Billing Generic Call Flow Call Flow DetailsAccess-Request Authentication Attribute Number Attribute Name DescriptionAccess-Accept Authorization Access-Accept AuthenticationAccess-Request Authorization Attribute Number Attribute Name Accounting StartData Flow Access-Request Quota Depleted Accept-Accept Quota DepletedAccounting Stop Session End Accounting Response Final StatusVendor-Specific Attributes Source VSA Name Type Call Flow DescriptionTotal Volume quota received by Crbprivate O S S a R Y GL-1Scalable wholesale access/open access solution GL-2GL-3 GL-4 GL-5 GL-6 GL-7 GL-8 GL-9 GL-10 Radius IN-1RFC IN-2IN-3 IN-4
Related manuals
Manual 180 pages 47.88 Kb

3.5 specifications

Cisco Systems 3.5 is an advanced version of Cisco's renowned networking and security solutions. This iteration showcases significant enhancements in performance, scalability, and security, making it a preferred choice for enterprises aiming to optimize their network operations and bolster their cybersecurity posture.

One of the main features of Cisco Systems 3.5 is its enhanced network automation capabilities. Automation streamlines network management, allowing organizations to apply consistent policies across their infrastructure while minimizing human error. This version employs advanced algorithms and machine learning to predict and rectify network issues proactively. With automation tools, network administrators can configure, monitor, and troubleshoot their networks with unprecedented efficiency.

Another notable characteristic of Cisco Systems 3.5 is its integration of artificial intelligence and machine learning into networking processes. The incorporation of AI enhances decision-making by analyzing vast amounts of network data, identifying patterns, and offering insights that help ensure optimal performance. This predictive analytics capability allows organizations to predict potential disruptions before they impact operations.

Security is a major focus in Cisco Systems 3.5. The platform introduces advanced threat detection and response systems that utilize deep learning to identify and mitigate emerging threats in real-time. Enhanced encryption protocols ensure that data transmitted over the network remains secure, protecting sensitive information from cyber threats. The integrated security features ensure compliance with various regulatory standards, a crucial requirement for businesses across multiple sectors.

The platforms' support for Software-Defined Networking (SDN) allows for dynamic resource allocation and traffic management. This flexibility enables organizations to adjust their network resources quickly in response to changing demands, leading to improved efficiency and reduced operational costs. Cisco Systems 3.5 also supports multicloud environments, facilitating seamless integration with cloud services such as AWS, Google Cloud, and Microsoft Azure.

Moreover, Cisco Systems 3.5 offers robust telemetry features, providing detailed real-time insights into network performance and health. This data-driven approach allows organizations to make informed decisions regarding capacity planning and resource optimization.

In summary, Cisco Systems 3.5 combines cutting-edge technologies such as AI, machine learning, and SDN to deliver a comprehensive networking solution. With its focus on automation, enhanced security, and multicloud support, this version is well-suited for modern enterprises looking to enhance their network infrastructure and security measures. As organizations continue to evolve in a digital-centric world, Cisco Systems 3.5 stands out as a critical tool to achieve connectivity and security goals effectively.
Top Page Image Contents