> Source: [sk31499](https://support.checkpoint.com/results/sk/sk31499)

# sk31499 - How to find out the Multicast MAC Addresses that are associated with Cluster Virtual interfaces

| Property | Value |
|----------|-------|
| Solution ID | sk31499 |
| Date Created | 2006-02-09 |
| Last Modified | 2018-01-09 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Solution

By default, Cluster Control Protocol (CCP) works in Multicast mode (for more details, refer to [sk93306 - ATRG: ClusterXL R6x and R7x](http://supportcontent.checkpoint.com/solutions?id=sk93306)).

Run the following commands on each cluster member to get the list of the Multicast MAC addresses that were associated with Cluster Virtual interfaces:

1. Start the cluster configuration debug in the background:   

   *Note* : this debug does not consume any CPU resources and does not cause any impact on the performance.   

   **`[Expert@HostName]# fw ctl zdebug -m cluster + conf > /var/log/data.txt &`**   

2. Generate the list of the cluster interfaces and their configuration:   

   **`[Expert@HostName]# cphaconf debug_data`**   

3. Bring the cluster configuration debug into the foreground:   

   **`[Expert@HostName]# fg`**   

4. Stop the debug by pressing CTRL+C.   

5. In the output file '`/var/log/data.txt`', look for this section:   

   **`;---- Multicast table ----`**

*** ** * ** ***

Example of the complete debug output (relevant section appears in bold text):

```
;24Oct2012 17:52:20.449806;[cpu_0];[fw_0];================================================;
;24Oct2012 17:52:20.449808;[cpu_0];[fw_0];=====   ClusterXL   debug   information      ===;
;24Oct2012 17:52:20.449809;[cpu_0];[fw_0];================================================
;
;24Oct2012 17:52:20.449809;[cpu_0];[fw_0];----  Sync ----
;
;24Oct2012 17:52:20.449812;[cpu_0];[fw_0];fwlddist_state is (1a): Receiving, Not Saving, Sending;
;24Oct2012 17:52:20.449813;[cpu_0];[fw_0];fwlddist_dobcast is: 1;
;24Oct2012 17:52:20.449814;[cpu_0];[fw_0];fw_has_nondefault_filter is: 1;
;24Oct2012 17:52:20.449814;[cpu_0];[fw_0];fw_syncn_is_configured is: 1;
;24Oct2012 17:52:20.449815;[cpu_0];[fw_0];fwlddist_policy_in_ready_state is: 1;
;24Oct2012 17:52:20.449816;[cpu_0];[fw_0];----   VMAC mode:   ----
;
;24Oct2012 17:52:20.449816;[cpu_0];[fw_0];VMAC: vmac mode is enabled;
;24Oct2012 17:52:20.449817;[cpu_0];[fw_0];VMAC: the vmac of each interface:;
;24Oct2012 17:52:20.449821;[cpu_0];[fw_0];Interface: 1) eth4, vmac: 00:1C:7F:00:42:28;
;24Oct2012 17:52:20.449822;[cpu_0];[fw_0];Interface: 2) eth2, vmac: 00:1C:7F:00:40:28;
;24Oct2012 17:52:20.449824;[cpu_0];[fw_0];Interface: 3) eth3, vmac: 00:1C:7F:00:41:28;
;24Oct2012 17:52:20.449824;[cpu_0];[fw_0];VMAC: priomisc mode interfaces (by the VMAC mechanism) are:;
;24Oct2012 17:52:20.449826;[cpu_0];[fw_0];Interface: 1) eth4, vmac_index=0x42;
;24Oct2012 17:52:20.449826;[cpu_0];[fw_0];Interface: 2) eth2, vmac_index=0x40;
;24Oct2012 17:52:20.449827;[cpu_0];[fw_0];Interface: 3) eth3, vmac_index=0x41;
;24Oct2012 17:52:20.449830;[cpu_0];[fw_0];------------------------

;
;24Oct2012 17:52:20.449831;[cpu_0];[fw_0];================================================;
;24Oct2012 17:52:20.449831;[cpu_0];[fw_0];=====   ClusterXL   debug   end              ===;
;24Oct2012 17:52:20.449832;[cpu_0];[fw_0];================================================
;
;24Oct2012 17:52:20.449834;[cpu_0];[fw_1];================================================;
;24Oct2012 17:52:20.449835;[cpu_0];[fw_1];=====   ClusterXL   debug   information      ===;
;24Oct2012 17:52:20.449835;[cpu_0];[fw_1];================================================
;
;24Oct2012 17:52:20.449836;[cpu_0];[fw_1];------------------------

;
;24Oct2012 17:52:20.449837;[cpu_0];[fw_1];=====   Cluster instance information      ===;
;24Oct2012 17:52:20.449837;[cpu_0];[fw_1];------------------------

;
;24Oct2012 17:52:20.449838;[cpu_0];[fw_1];----   Selection table  ----
;
;24Oct2012 17:52:20.449839;[cpu_0];[fw_1];Effective selection table size: 2
;
;24Oct2012 17:52:20.449841;[cpu_0];[fw_1];------------------------

;
;24Oct2012 17:52:20.449841;[cpu_0];[fw_1];----  Multicast table ----
;
;24Oct2012 17:52:20.449844;[cpu_0];[fw_1];eth0:  Address:   172.30.41.221;
;24Oct2012 17:52:20.449846;[cpu_0];[fw_1];Cluster/default multicast IP:  172.30.0.250,  MAC address: 01:00:5E:1E:00:FA;
;24Oct2012 17:52:20.449848;[cpu_0];[fw_1];eth4:  Address:   40.40.40.221;
;24Oct2012 17:52:20.449849;[cpu_0];[fw_1];Cluster/default multicast IP:  40.40.40.224,  MAC address: 01:00:5E:28:28:E0;
;24Oct2012 17:52:20.449851;[cpu_0];[fw_1];eth2:  Address:   20.20.20.221;
;24Oct2012 17:52:20.449852;[cpu_0];[fw_1];Cluster/default multicast IP:  20.20.20.224,  MAC address: 01:00:5E:14:14:E0;
;24Oct2012 17:52:20.449854;[cpu_0];[fw_1];eth3:  Address:   30.30.30.221;
;24Oct2012 17:52:20.449855;[cpu_0];[fw_1];Cluster/default multicast IP:  30.30.30.224,  MAC address: 01:00:5E:1E:1E:E0;
;24Oct2012 17:52:20.449856;[cpu_0];[fw_1];eth1:  Address:   10.10.10.221;
;24Oct2012 17:52:20.449858;[cpu_0];[fw_1];Cluster/default multicast IP:  10.10.10.250,  MAC address: 01:00:5E:0A:0A:FA;
;24Oct2012 17:52:20.449860;[cpu_0];[fw_1];------------------------

;
;24Oct2012 17:52:20.449861;[cpu_0];[fw_1];---- Status subscribers ----
;
;24Oct2012 17:52:20.449862;[cpu_0];[fw_1];Subscriber: 0 pid 3307 sig 3 desc cprd PID 3307;
;24Oct2012 17:52:20.449863;[cpu_0];[fw_1];------------------------

;
;24Oct2012 17:52:20.449864;[cpu_0];[fw_1];=====   Cluster instance information end     ===;
;24Oct2012 17:52:20.449864;[cpu_0];[fw_1];------------------------

;
;24Oct2012 17:52:20.449865;[cpu_0];[fw_1];----  Sync ----
;
;24Oct2012 17:52:20.449867;[cpu_0];[fw_1];fwlddist_state is (1a): Receiving, Not Saving, Sending;
;24Oct2012 17:52:20.449867;[cpu_0];[fw_1];fwlddist_dobcast is: 1;
;24Oct2012 17:52:20.449868;[cpu_0];[fw_1];fw_has_nondefault_filter is: 1;
;24Oct2012 17:52:20.449869;[cpu_0];[fw_1];fw_syncn_is_configured is: 1;
;24Oct2012 17:52:20.449870;[cpu_0];[fw_1];fwlddist_policy_in_ready_state is: 1;
;24Oct2012 17:52:20.449870;[cpu_0];[fw_1];----   VMAC mode:   ----
;
;24Oct2012 17:52:20.449871;[cpu_0];[fw_1];VMAC: vmac mode is enabled;
;24Oct2012 17:52:20.449872;[cpu_0];[fw_1];VMAC: the vmac of each interface:;
;24Oct2012 17:52:20.449873;[cpu_0];[fw_1];Interface: 1) eth4, vmac: 00:1C:7F:00:42:28;
;24Oct2012 17:52:20.449875;[cpu_0];[fw_1];Interface: 2) eth2, vmac: 00:1C:7F:00:40:28;
;24Oct2012 17:52:20.449876;[cpu_0];[fw_1];Interface: 3) eth3, vmac: 00:1C:7F:00:41:28;
;24Oct2012 17:52:20.449877;[cpu_0];[fw_1];VMAC: priomisc mode interfaces (by the VMAC mechanism) are:;
;24Oct2012 17:52:20.449878;[cpu_0];[fw_1];Interface: 1) eth4, vmac_index=0x42;
;24Oct2012 17:52:20.449878;[cpu_0];[fw_1];Interface: 2) eth2, vmac_index=0x40;
;24Oct2012 17:52:20.449879;[cpu_0];[fw_1];Interface: 3) eth3, vmac_index=0x41;
;24Oct2012 17:52:20.449882;[cpu_0];[fw_1];------------------------

;
;24Oct2012 17:52:20.449882;[cpu_0];[fw_1];================================================;
;24Oct2012 17:52:20.449883;[cpu_0];[fw_1];=====   ClusterXL   debug   end              ===;
;24Oct2012 17:52:20.449884;[cpu_0];[fw_1];================================================
```

*** ** * ** ***

**Related solutions:**

* [sk31782 (ClusterXL association between cluster Virtual IP addresses and MAC Addresses)](http://supportcontent.checkpoint.com/solutions?id=sk31782)
* [sk50840 (How to enable ClusterXL Virtual MAC (VMAC) mode)](http://supportcontent.checkpoint.com/solutions?id=sk50840)
* [sk93306 (ATRG: ClusterXL R6x and R7x)](http://supportcontent.checkpoint.com/solutions?id=sk93306)

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
