Optimizes cross-cluster replication for the type of network that servers in the clusters use for administrative communication. To enhance the reliability of HTTP sessions, you can configure servers in one cluster to replicate the session data to servers in a different cluster. In such an environment, configure the clusters to be one of the following types: man if the clustered servers can send their data through a metro area network (man) in which latency is negligible. With this ClusterType value, servers replicate session state synchronously and in memory only. For example, when serverA in cluster1 starts an HTTP session, its backup server, serverB in cluster2, immediately replicates this session in memory to Server B. wan if the clusters are far apart or send their data through a wide area network (wan) that experiences significant network latency. With this ClusterType value, a server replicates session state synchronously to the backup server in the same cluster and asynchronously to a server in the remote cluster. For example, when serverA in cluster1 starts an HTTP session, it sends the data to serverB in cluster1 and then asynchronously sends data to serverX in cluster 2. ServerX will persist the session state in the database. If you persist session data in a replicating database, and if you prefer to use the database to replicate the data instead of WebLogic Server, choose a cluster type of wan and leave the remote cluster address undefined. WebLogic Server saves the session data to the local database and assumes that the database replicates data as needed.
Parsed from file BEA-WEBLOGIC-MIB.mib.txt
Company: None
Module: BEA-WEBLOGIC-MIB
Optimizes cross-cluster replication for the type of network that servers in the clusters use for administrative communication. To enhance the reliability of HTTP sessions, you can configure servers in one cluster to replicate the session data to servers in a different cluster. In such an environment, configure the clusters to be one of the following types: man if the clustered servers can send their data through a metro area network (man) in which latency is negligible. With this ClusterType value, servers replicate session state synchronously and in memory only. For example, when serverA in cluster1 starts an HTTP session, its backup server, serverB in cluster2, immediately replicates this session in memory to Server B. wan if the clusters are far apart or send their data through a wide area network (wan) that experiences significant network latency. With this ClusterType value, a server replicates session state synchronously to the backup server in the same cluster and asynchronously to a server in the remote cluster. For example, when serverA in cluster1 starts an HTTP session, it sends the data to serverB in cluster1 and then asynchronously sends data to serverX in cluster 2. ServerX will persist the session state in the database. If you persist session data in a replicating database, and if you prefer to use the database to replicate the data instead of WebLogic Server, choose a cluster type of wan and leave the remote cluster address undefined. WebLogic Server saves the session data to the local database and assumes that the database replicates data as needed.
Parsed from file BEA-WEBLOGIC-MIB.mib
Module: BEA-WEBLOGIC-MIB
Vendor: Independence Technologies, Inc.(ITI)
Module: BEA-WEBLOGIC-MIB
[Automatically extracted from oidview.com]
clusterClusterType OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "Optimizes cross-cluster replication for the type of network that servers in the clusters use for administrative communication. To enhance the reliability of HTTP sessions, you can configure servers in one cluster to replicate the session data to servers in a different cluster. In such an environment, configure the clusters to be one of the following types: man if the clustered servers can send their data through a metro area network (man) in which latency is negligible. With this ClusterType value, servers replicate session state synchronously and in memory only. For example, when serverA in cluster1 starts an HTTP session, its backup server, serverB in cluster2, immediately replicates this session in memory to Server B. wan if the clusters are far apart or send their data through a wide area network (wan) that experiences significant network latency. With this ClusterType value, a server replicates session state synchronously to the backup server in the same cluster and asynchronously to a server in the remote cluster. For example, when serverA in cluster1 starts an HTTP session, it sends the data to serverB in cluster1 and then asynchronously sends data to serverX in cluster 2. ServerX will persist the session state in the database. If you persist session data in a replicating database, and if you prefer to use the database to replicate the data instead of WebLogic Server, choose a cluster type of wan and leave the remote cluster address undefined. WebLogic Server saves the session data to the local database and assumes that the database replicates data as needed." ::= { clusterEntry 73 }
clusterClusterType OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "Optimizes cross-cluster replication for the type of network that servers in the clusters use for administrative communication. To enhance the reliability of HTTP sessions, you can configure servers in one cluster to replicate the session data to servers in a different cluster. In such an environment, configure the clusters to be one of the following types: man if the clustered servers can send their data through a metro area network (man) in which latency is negligible. With this ClusterType value, servers replicate session state synchronously and in memory only. For example, when serverA in cluster1 starts an HTTP session, its backup server, serverB in cluster2, immediately replicates this session in memory to Server B. wan if the clusters are far apart or send their data through a wide area network (wan) that experiences significant network latency. With this ClusterType value, a server replicates session state synchronously to the backup server in the same cluster and asynchronously to a server in the remote cluster. For example, when serverA in cluster1 starts an HTTP session, it sends the data to serverB in cluster1 and then asynchronously sends data to serverX in cluster 2. ServerX will persist the session state in the database. If you persist session data in a replicating database, and if you prefer to use the database to replicate the data instead of WebLogic Server, choose a cluster type of wan and leave the remote cluster address undefined. WebLogic Server saves the session data to the local database and assumes that the database replicates data as needed." ::= { clusterEntry 73 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.140.625.510.1.1 | clusterIndex | 0 | 0 | Unique value directed from ObjectName which is used as table index |
| 1.3.6.1.4.1.140.625.510.1.5 | clusterObjectName | 0 | 0 | JMX-standard MBean name |
| 1.3.6.1.4.1.140.625.510.1.10 | clusterType, multicastAddress | 0 | 0 | BEA-proprietary MBean type |
| 1.3.6.1.4.1.140.625.510.1.15 | clusterName, defaultLoadBalancingAlgorithm | 0 | 0 | BEA-proprietary MBean name |
| 1.3.6.1.4.1.140.625.510.1.20 | clusterParent, serverList | 0 | 0 | Comma separated list of servers in the Cluster. |
| 1.3.6.1.4.1.140.625.510.1.25 | clusterServers | 0 | 0 | The servers which have declared membership in this cluster. |
| 1.3.6.1.4.1.140.625.510.1.30 | clusterClusterAddress | 0 | 0 | The address to be used by clients to connect to this cluster. This address may be either a DNS host name that maps to multiple IP… |
| 1.3.6.1.4.1.140.625.510.1.35 | clusterMulticastAddress | 0 | 0 | The multicast address used by cluster members to communicate with each other. |
| 1.3.6.1.4.1.140.625.510.1.40 | clusterMulticastTTL | 0 | 0 | The number of network hops that a cluster multicast message is allowed to travel. 1 restricts the cluster to one subnet. The mini… |
| 1.3.6.1.4.1.140.625.510.1.45 | clusterMulticastSendDelay | 0 | 0 | The number of milliseconds to delay sending message fragments over multicast in order to avoid OS-level buffer overflow. The def… |
| 1.3.6.1.4.1.140.625.510.1.50 | clusterDefaultLoadAlgorithm | 0 | 0 | The algorithm to be used for load-balancing between replicated services if none is specified for a particular service. |
| 1.3.6.1.4.1.140.625.510.1.55 | clusterServiceAgeThresholdSeconds | 0 | 0 | he number of seconds by which the age of two conflicting services must differ before one is considered older than the other. |
| 1.3.6.1.4.1.140.625.510.1.56 | clusterMulticastBufferSize | 0 | 0 | Returns the multicast socket send/receive buffer size. |
| 1.3.6.1.4.1.140.625.510.1.57 | clusterMulticastPort | 0 | 0 | Defines the multicast port used by cluster members to communicate with each other. |
| 1.3.6.1.4.1.140.625.510.1.58 | clusterClientCertProxyEnabled | 0 | 0 | Gets the clientCertProxyEnabled attribute of the ClusterMBean object |
| 1.3.6.1.4.1.140.625.510.1.59 | clusterWeblogicPluginEnabled | 0 | 0 | Gets the weblogicPluginEnabled attribute of the ClusterMBean object |
| 1.3.6.1.4.1.140.625.510.1.60 | clusterHealthCheckIntervalMillis | 0 | 0 | Interval in milliseconds at which Migratable Servers and Cluster Masters prove their liveness via the database. |
| 1.3.6.1.4.1.140.625.510.1.61 | clusterHealthCheckPeriodsUntilFencing | 0 | 0 | Maximum number of periods that a cluster member will wait before timing out a Cluster Master and also the maximum number of per… |
| 1.3.6.1.4.1.140.625.510.1.62 | clusterSessionFlushInterval | 0 | 0 | Interval in seconds until HTTP Sessions are periodically flushed to the backup cluster to dump session state on disk. |
| 1.3.6.1.4.1.140.625.510.1.63 | clusterAdditionalAutoMigrationAttempts | 0 | 0 | A migratable server could fail to come up on every possible configured machine. This attribute controls how many further attemp… |
| 1.3.6.1.4.1.140.625.510.1.64 | clusterRemoteClusterAddress | 0 | 0 | Set the foreign cluster. Cluster infrastructure uses this address to connect to foreign cluster for HTTP Session WAN/MAN failov… |
| 1.3.6.1.4.1.140.625.510.1.65 | clusterFrontendHTTPPort | 0 | 0 | The name of the HTTP port to which all redirected URLs will be sent. Sets the FrontendHTTPPort for the default webserver (not … |
| 1.3.6.1.4.1.140.625.510.1.66 | clusterMulticastDataEncryption | 0 | 0 | Enables multicast data to be incrypted. Only the multicast data is encrypted. Multicast header information is not encrypted. |
| 1.3.6.1.4.1.140.625.510.1.67 | clusterSecureReplicationEnabled | 0 | 0 | Servers in a cluster replicates session data. If replication channel is defined then the session data will be sent using the re… |
| 1.3.6.1.4.1.140.625.510.1.68 | clusterJobSchedulerTableName | 0 | 0 | The table name to use for storing timers active with the job scheduler |
| 1.3.6.1.4.1.140.625.510.1.69 | clusterReplicationTimeoutEnabled | 0 | 0 | Indicates if timeout should be applied to session replication calls. |
| 1.3.6.1.4.1.140.625.510.1.70 | clusterAsyncSessionQueueTimeout | 0 | 0 | Interval in seconds until the producer thread will wait for the AsyncSessionQueue to become unblocked. Should be similar to th… |
| 1.3.6.1.4.1.140.625.510.1.71 | clusterInterClusterCommLinkHealthCheckInterval | 0 | 0 | If the cluster link between two clusters goes down, a trigger will run to periodically to see if the link is restored. The dura… |
| 1.3.6.1.4.1.140.625.510.1.72 | clusterSessionFlushThreshold | 0 | 0 | clusterSessionFlushthreshold |
| 1.3.6.1.4.1.140.625.510.1.74 | clusterGreedySessionFlushInterval | 0 | 0 | Interval in seconds until HTTP Sessions are periodically flushed to secondary server. |
| 1.3.6.1.4.1.140.625.510.1.75 | clusterPersistSessionsOnShutdown | 0 | 0 | When shutting down servers, sessions are not updated. If the primary and secondary servers of a session are shut down with no s… |
| 1.3.6.1.4.1.140.625.510.1.76 | clusterMigrationBasis | 0 | 0 | Controls the mechanism used for server migration. |
| 1.3.6.1.4.1.140.625.510.1.77 | clusterHttpTraceSupportEnabled | 0 | 0 | Returns the value of HttpTraceSupportEnabled. |
| 1.3.6.1.4.1.140.625.510.1.78 | clusterReplicationChannel | 0 | 0 | The channel name to be used for replication traffic. Cluster infrastructure uses this channel to send updates for HTTP sessions… |
| 1.3.6.1.4.1.140.625.510.1.79 | clusterFencingGracePeriodMillis | 0 | 0 | During automatic migration, if the Cluster Master determines a server to be dead, it waits for this period of time (in millisec… |
| 1.3.6.1.4.1.140.625.510.1.80 | clusterFrontendHost | 0 | 0 | The name of the host to which all redirected URLs will be sent. Sets the HTTP FrontendHost for the default webserver (not virt… |
| 1.3.6.1.4.1.140.625.510.1.81 | clusterMemberWarmupTimeoutSeconds | 0 | 0 | Maximum number of seconds that a cluster member will wait to discover and synchronize with other servers in the cluster. Normal… |
| 1.3.6.1.4.1.140.625.510.1.82 | clusterFrontendHTTPSPort | 0 | 0 | The name of the secure HTTP port to which all redirected URLs will be sent. Sets the FrontendHTTPSPort for the default webserv… |
| 1.3.6.1.4.1.140.625.510.1.83 | clusterClusterBroadcastChannel | 0 | 0 | Specifies the channel used to handle communications within a cluster. If no channel is specified the default channel is used. C… |
| 1.3.6.1.4.1.140.625.510.1.84 | clusterIdlePeriodsUntilTimeout | 0 | 0 | Maximum number of periods that a cluster member will wait before timing out a member of a cluster. Maximum number of periods t… |
| 1.3.6.1.4.1.140.625.510.1.85 | clusterNumberOfServersInClusterAddress | 0 | 0 | Number of servers to be listed from this cluster when generating a cluster address automatically. This setting has no effect if… |
| 1.3.6.1.4.1.140.625.510.1.86 | clusterClusterMessagingMode | 0 | 0 | Specifies the messaging type used in the cluster. Multicast messaging, the default, is provided for backwards compatibility. Un… |
| 1.3.6.1.4.1.140.625.510.1.87 | clusterMillisToSleepBetweenAutoMigrationAttempts | 0 | 0 | Controls how long of a pause there should be between the migration attempts described in getAdditionalAutoMigrationAttempts(). … |
| 1.3.6.1.4.1.140.625.510.1.88 | clusterAutoMigrationTableName | 0 | 0 | Return the name of the table to be used for server migration. |
| 1.3.6.1.4.1.140.625.510.1.89 | clusterWANSessionPersistenceTableName | 0 | 0 | Return the name of the table to be used for WAN session persistence. |