On Sat, May 23, 2015 at 9:07 AM, Momonth <momonth@gmail.com> wrote:

Hi All,

I never used e0M on FAS32xx as it was limited to 100Mb, but decided to
give a try on FAS8040.

So, I've configured SP via DHCP (10.193.12.0/24), it's up and running
and I can login onto it:

na102::> sp show -node na102labnode-1a -instance

Node: na102labnode-1a
Type of Device: SP
Status: online
Is Network Configured: true
Public IP Address: 10.193.12.31
MAC Address: 00:a0:98:68:00:18
Firmware Version: 3.1P1
Part Number: unknown
Serial Number: unknown
Device Revision: Not Applicable
Is Firmware Autoupdate Enabled: true

However having assigned an IP to e0M (from cluster management
interface) doesn't make the e0M "ping-able". Here is my config (the
same 10.193.12.0/24 is used):

na102::> network interface show -vserver na102 -lif
na102labnode-1a_mgmt1 -instance

Vserver Name: na102
Logical Interface Name: na102labnode-1a_mgmt1
Role: node-mgmt
Data Protocol: -
Home Node: na102labnode-1a
Home Port: e0M
Current Node: na102labnode-1a
Current Port: e0M
Operational Status: up
Extended Status: -
Is Home: true
Network Address: 10.193.12.44
Netmask: 255.255.255.0
Bits in the Netmask: 24
IPv4 Link Local: -
Subnet Name: -
Administrative Status: up
Failover Policy: local-only
Firewall Policy: mgmt
Auto Revert: true
Fully Qualified DNS Zone Name: none
DNS Query Listen Enable: false
Failover Group Name: Default
FCP WWPN: -
Address family: ipv4
Comment: -
IPspace of LIF: Default

It feels like e0M needs default gateway? How do I set it up then?

Or Am I missing the whole idea here?

Thanks,
Vladimir
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters