Cloud CM-IPMP Guía para resolver problemas Pagina 188
- Pagina / 201
- Tabla de contenidos
- MARCADORES
Valorado. / 5. Basado en revisión del cliente
rhinohost1:
# ifconfig -a
...
/jointfilesconvert/447134/bge0: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 3
inet 192.168.1.101 netmask ffffff00 broadcast 192.168.1.255
groupname savanna
ether 0:3:ba:3c:9c:d3
/jointfilesconvert/447134/bge0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
/jointfilesconvert/447134/bge1: flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STANDBY,INACTIVE> mtu 1500 index 4
inet 192.168.1.102 netmask ffffff00 broadcast 192.168.1.255
groupname savanna
ether 0:3:ba:3c:9c:d4
Note that the virtual interface
/jointfilesconvert/447134/bge0:1
. This has the public, highly-available address. If there is a link failure on
/jointfilesconvert/447134/bge0
(for
example, when the network cable is pulled out), then the failure will be detected by the
in.mpathd daemon
and it will create
the virtual interface
/jointfilesconvert/447134/bge1:1
and move the IP address across.
We now have a basic active/standby group. Next we need to tune some settings to make it suitable for use in a Rhino cluster.
B.1.3 Tune failure detection time
The default time for IPMP to detect a link failure and perform a failover is 10 seconds. This is higher than Rhino SLEE’s default
8 second timeout, so it is possible that we could get unnecessary node failures while IPMP is busy failing over.
To reduce the IPMP failure detection time, edit /etc/default/mpathd and change the line:
FAILURE_DETECTION_TIME=10000
to:
FAILURE_DETECTION_TIME=1000
1000ms usually works well for failing over.
After editing the file, make the in.mpathd daemon reload its configuration:
# pkill -HUP in.mpathd
B.1.4 Configure probe addresses
IPMP will dynamically select some remote IP addresses to use as probe addresses. These will be other hosts on the same
network, and IPMP frequently pings these addresses to help determine if any link failures have occured. If you snoop the
interfaces you will see many pings emanating from the test addresses on the two interfaces.
In this configuration with just two hosts on the network, it is likely that IPMP will pick the other host’s public address as a
probe address. This seems to work except in the case where both active interfaces fail at the same time. Because each host will
temporarily be unable to ping the other’s public address, IPMP will decide that all the interfaces have gone down and not permit
any traffic on either interface.
To get around this problem, IPMP needs to be forced to use specific IP addresses as probe addresses. There should be more
than one probe address, and these should be on separate hosts. For example, in a Rhino cluster, each node could use the test
addresses of one or more other nodes (or a quorum node or management server etc) as probe addresses.
To specify probe addresses, add static host routes to the routing table:
rhinohost1:
# route add rhinohost2-/jointfilesconvert/447134/bge0 rhinohost2-/jointfilesconvert/447134/bge0 -static
# route add rhinohost2-/jointfilesconvert/447134/bge1 rhinohost2-/jointfilesconvert/447134/bge1 -static
IPMP will automatically start using these addresses as probe addresses. Now if both active interfaces fail, the standby interfaces
will still be able to ping some of their probe addresses, so IPMP will still be able to failover to the standby interface.
Open Cloud Rhino 1.4.3 Administration Manual v1.1 179
- Open Cloud Rhino SLEE 1.4.3 1
- Administration Manual 1
- November 2, 2006 (1838) 2
- Contents 3
- Introduction 10
- The Rhino SLEE Platform 12
- 2.3 Integration 13
- 2.4 Service Development 14
- 2.5 Functional Testing 15
- 2.6 Performance Testing 15
- 2.7 Software Development Kit 16
- JAIN SLEE Overview 17
- 3.3 Event Driven Applications 18
- 3.4 Components 18
- 3.5 Provisioned Data 18
- 3.6 Facilities 18
- 3.7 Activities 19
- 4.2.3 Firewalls 22
- 4.2.4 Unpacking 22
- 4.2.5 Installation 22
- 4.2.6 Unattended Installation 23
- 4.2.7 Configuring a Cluster 23
- 4.2.9 Configuring the Cluster 25
- 4.3 Cluster Lifecycle 26
- 4.3.2 Starting a Node 27
- 4.3.3 Starting a Quorum Node 27
- 4.3.4 Automatic Node Restart 27
- 4.3.5 Starting the SLEE 27
- 4.4 Management Interface 28
- 4.5 Setting the system clock 29
- 4.6 Optional Configuration 30
- 4.7 Installed Files 31
- 4.8 Runtime Files 32
- 4.8.2 Logging output 33
- Management 35
- 5.2 Management Tutorials 36
- 5.3 Building the Examples 37
- 5.5 Installing a Service 40
- 5.6 Uninstalling a Service 43
- 5.8 Creating a Profile 46
- 5.9 SLEE Lifecycle 50
- 5.9.4 The Stopping State 51
- 5.9.2 The Starting State 51
- 5.9.3 The Running State 51
- Administrative Maintenance 52
- 6.2.2 Removing Activities 54
- 6.2.3 Inspecting SBBs 55
- 6.2.4 Removing SBB Entities 56
- 6.2.5 Removing All 56
- 6.3 Upgrading a Cluster 57
- 6.3.3 Deploying State 58
- 6.4 Backup and Restore 59
- Export and Import 60
- 7.2 Exporting State 61
- 7.3 Importing State 62
- 7.4 Partial Imports 63
- Statistics and Monitoring 65
- 8.2 Performance Implications 66
- 8.3 Console Mode 66
- 8.3.1 Useful output options 67
- 8.4 Graphical Mode 68
- Web Console 73
- 9.2.2 Managed Objects 74
- 9.2.3 Navigation Shortcuts 74
- 9.3 Deployment Architecture 75
- 9.3.2 Standalone Web Console 76
- 9.4 Configuration 77
- 9.5 Security 77
- 9.5.2 Declarative Security 78
- 9.5.3 JAAS 78
- Log System Configuration 79
- 10.3 Logging Configuration 80
- 10.3.2 Web Console Logging 81
- Chapter 11 84
- 11.2.2 Web Console 85
- Threshold Alarms 87
- 12.5 Types of Rule Conditions 88
- 12.6 Creating Rules 89
- 12.6.2 Command Console 90
- Chapter 13 92
- 13.3.1 Configuration 93
- Licensing 94
- 14.2 Alarms 95
- 14.2.4 Management Interface 96
- 14.2.5 Audit Logs 96
- Security Configuration 97
- 15.3 Network Connections 98
- 15.4 Signing Deployable Units 99
- 15.5 Key Stores 100
- 15.6 Transport Layer Security 100
- 15.7 JAAS Configuration 101
- Performance Tuning 103
- 16.2.3 Tuning Recommendations 104
- 16.2.1 Configuration 104
- 16.2.2 Stage Tuning 104
- 16.3 Object Pool Configuration 105
- 16.4 Fault Tolerance 106
- Clustering 109
- 17.3 Scenarios 110
- 17.4 Configuration Parameters 111
- Application Environment 113
- 18.2.2 Concurrency Control 114
- 18.3 Application Configuration 115
- 18.5.4 Example 119
- 18.6 Application Fail-Over 120
- 18.6.2 Management Interface 121
- Database Connectivity 122
- 19.3 Configuration Example 123
- 19.4 SBB use of JDBC 124
- 19.4.1 SQL Programming 125
- J2EE SLEE Integration 127
- PostgreSQL Configuration 131
- 21.4 TCP/IP Connections 132
- 21.5 Access Control 132
- SIP Example Applications 138
- 22.2 System Requirements 139
- 22.3 Directory Contents 139
- 22.4 Quick Start 139
- 22.4.2 Building and Deploying 140
- 22.5 Manual Installation 144
- 22.6 Using the Services 152
- 22.6.4 Enabling Debug Output 156
- JCC Example Application 157
- 23.2.1 Resource Adaptor 158
- 23.2.3 Service Logic 160
- 23.3 Directory Contents 163
- 23.4 Installation 163
- 23.6.1 Trace Components 170
- 23.6.3 Creating a Call 171
- 23.7 Call Duration Service 172
- Customising the SIP Registrar 178
- 24.4 Extending with Profiles 181
- Hardware and Systems Support 182
- A.2.4 Application Example 184
- Redundant Networking 186
- Entities 191
- C.3 Configuration Properties 192
- C.4 Entity Binding 193
- Transactions 194
- D.3.3 Summary 195
- D.4.3 Commit Protocols 196
- Audit Logs 197
- E.2 Example Audit Logfile 199
- Glossary 200
© 2020, manymanuals.es. Todos los derechos reservados | 0.044 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales