hi maestro expert 🙂
i am making my first step to implemant maetro then i have some question about it :
Q1 : If i am correct there is no need to configure Sync interface for the gateway and in the maestro object in management server and in the mho security group . It will be automaticly use network 192.0.2.X on a virtual interface named Sync like in my lab :
Virtual cluster interfaces: 10
eth1-05 10.20.0.1 VMAC address: 00:1C:7F:81:05:C1
eth1-06 81.255.188.1 VMAC address: 00:1C:7F:81:06:C1
eth1-07 192.168.4.4 VMAC address: 00:1C:7F:81:07:C1
eth1-08 81.255.188.253 VMAC address: 00:1C:7F:81:08:C1
eth1-09 10.10.0.254 VMAC address: 00:1C:7F:81:09:C1
eth1-10 10.0.50.1 VMAC address: 00:1C:7F:81:0A:C1
eth1-Mgmt1 217.109.182.193
eth1-CIN 198.51.101.2
eth2-CIN 198.51.101.202
Sync 192.0.2.2
[Expert@OIF-ch01-02:0]# ifconfig Sync
Sync Link encap:Ethernet HWaddr 00:1C:7F:02:04:FE
inet addr:192.0.2.2 Bcast:192.0.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:136664 errors:0 dropped:0 overruns:0 frame:0
TX packets:62063 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:30427407 (29.0 MiB) TX bytes:5948091 (5.6 MiB)
Q2 : all members are in active state and the first gateway in the security group will be the pivot like in A/A with cluster XL or how traffic is handle when you have 3 gateway or more in the security group ?
Cluster Mode: HA Over LS
ID Unique Address Assigned Load State
1 (local) 192.0.2.1 33% ACTIVE
2 192.0.2.2 33% ACTIVE
3 192.0.2.3 33% ACTIVE
Q3 : on the Smartcenter there is no way to check the HA status for the gateway in the secutiry group on the MHO config ?
Q4 : if i am correct with maestro there is only a virtual ip address configure in the smartcenter on the network management and no need to configure reel ip per node and define the interface as a cluster interface
Q5 : What is interface eth1-CIN and eth2-CIN with and adress IP in : 198.51.101.X ? none of this interface are set up on the mho security group :
In clish they not appear :
[Global] OIF-ch01-01 > show interface
eth1-05 eth1-06 eth1-07 eth1-08 eth1-09 eth1-10
eth1-11 eth1-12 eth1-Mgmt1 lo BPEth0 BPEth1
In Expert :
eth1-CIN Link encap:Ethernet HWaddr 00:1C:7F:81:42:01
inet addr:198.51.101.1 Bcast:198.51.101.127 Mask:255.255.255.128
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:741356 errors:0 dropped:0 overruns:0 frame:0
TX packets:894418 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:226692007 (216.1 MiB) TX bytes:99844561 (95.2 MiB)
eth2-CIN Link encap:Ethernet HWaddr 00:1C:7F:82:42:01
inet addr:198.51.101.201 Bcast:198.51.101.255 Mask:255.255.255.128
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:67704 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:2843568 (2.7 MiB)
[Expert@OIF-ch01-01:0]# ethtool eth2-CIN
Settings for eth2-CIN:
Supported ports: [ FIBRE ]
Supported link modes: 10000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Current message level: 0x00000000 (0)
thank you for reading
