-
Suggestion
-
Resolution: Won't Fix
-
None
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
To check on network interface assigned to cluster, we could have a simple tool that list the association as attached.
<property name="confluence.cluster.interface">eth1</property>
Use the attached list-interfaces
Run it by java -jar list-interfaces.jar
Example output:
C:\>java -jar list-interfaces.jar interfaces.size() = 4 networkInterface[0] = name:lo (MS TCP Loopback interface) index: 1 addresses: /127.0.0.1; networkInterface[1] = name:eth0 (VMware Virtual Ethernet Adapter for VMnet8) index: 2 addresses: /192.168.133.1; networkInterface[2] = name:eth1 (VMware Virtual Ethernet Adapter for VMnet1) index: 3 addresses: /192.168.68.1; networkInterface[3] = name:eth2 (Broadcom NetXtreme 57xx Gigabit Controller - Packet Scheduler Miniport) index: 4 addresses: /192.168.0.101;
- is incorporated by
-
CONFCLOUD-10980 Cluster debugging/troubleshooting tools
- Closed
- is related to
-
CONFCLOUD-10953 Support unicast addressing in cluster when well-known-addresses WKA are defined
- Closed
-
CONFCLOUD-10977 Generate new Multicast address from a "new" cluster name
- Closed
-
CONFSERVER-10979 List confluence cluster interface
- Closed
[CONFCLOUD-10979] List confluence cluster interface
Workflow | Original: JAC Suggestion Workflow [ 3417643 ] | New: JAC Suggestion Workflow 3 [ 3630043 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2254971 ] | New: JAC Suggestion Workflow [ 3417643 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2151781 ] | New: Confluence Workflow - Public Facing v3 [ 2254971 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1906844 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2151781 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1806398 ] | New: Confluence Workflow - Public Facing v3 [ 1906844 ] |
Description |
Original:
To check on network interface assigned to cluster, we could have a simple tool that list the association as attached. {code:xml} <property name="confluence.cluster.interface">eth1</property> {code} Use the attached {{list-interfaces}} Run it by {{java -jar list-interfaces.jar}} Example output: {noformat} C:\>java -jar list-interfaces.jar interfaces.size() = 4 networkInterface[0] = name:lo (MS TCP Loopback interface) index: 1 addresses: /127.0.0.1; networkInterface[1] = name:eth0 (VMware Virtual Ethernet Adapter for VMnet8) index: 2 addresses: /192.168.133.1; networkInterface[2] = name:eth1 (VMware Virtual Ethernet Adapter for VMnet1) index: 3 addresses: /192.168.68.1; networkInterface[3] = name:eth2 (Broadcom NetXtreme 57xx Gigabit Controller - Packet Scheduler Miniport) index: 4 addresses: /192.168.0.101; {noformat} |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *Confluence Cloud*. Using *Confluence Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFSERVER-10979]. {panel} To check on network interface assigned to cluster, we could have a simple tool that list the association as attached. {code:xml} <property name="confluence.cluster.interface">eth1</property> {code} Use the attached {{list-interfaces}} Run it by {{java -jar list-interfaces.jar}} Example output: {noformat} C:\>java -jar list-interfaces.jar interfaces.size() = 4 networkInterface[0] = name:lo (MS TCP Loopback interface) index: 1 addresses: /127.0.0.1; networkInterface[1] = name:eth0 (VMware Virtual Ethernet Adapter for VMnet8) index: 2 addresses: /192.168.133.1; networkInterface[2] = name:eth1 (VMware Virtual Ethernet Adapter for VMnet1) index: 3 addresses: /192.168.68.1; networkInterface[3] = name:eth2 (Broadcom NetXtreme 57xx Gigabit Controller - Packet Scheduler Miniport) index: 4 addresses: /192.168.0.101; {noformat} |
Link |
New:
This issue is related to |
Project Import | New: Sat Apr 01 14:06:06 UTC 2017 [ 1491055566265 ] |