Can't ping new PCI LAN card x4270_m2

Hi,

I've recently moved my pci LAN card from Slot2 Slot5 on my sun x4270_m2 server (solaris 10).

I've done the

touch / reconfigure

and

devfsadm

, however my issue is that im able to configure the e1000g7 port with an ip address (192.168.0.1) but if i plug my laptop (set with static ip address of 192.168.0.10) to the back of the server on port e1000g7 with a straight cable, i am not able to ping that IP address...i get 'unreachable host'

Does anyone know what I'm missing??

/Kerry

please post the output of "dladm show-dev".

Hi DukeNuke2,

Here is the output:

root@4b>dladm show-dev
igb0            link: up        speed: 1000  Mbps       duplex: full
igb1            link: up        speed: 1000  Mbps       duplex: full
igb2            link: down      speed: 0     Mbps       duplex: half
igb3            link: down      speed: 0     Mbps       duplex: half
e1000g4         link: unknown   speed: 0     Mbps       duplex: half
e1000g5         link: unknown   speed: 0     Mbps       duplex: half
e1000g6         link: down      speed: 0     Mbps       duplex: half
e1000g7         link: down      speed: 0     Mbps       duplex: half
root@4b>

Any ideas?

was the output with cable to the laptop to the port? also the output of "ifconfig -a" might be helpfull...

Hi Duke,
With my laptop connected, here is the output:

root@4b>dladm show-dev
igb0            link: up        speed: 1000  Mbps       duplex: full
igb1            link: up        speed: 1000  Mbps       duplex: full
igb2            link: down      speed: 0     Mbps       duplex: half
igb3            link: down      speed: 0     Mbps       duplex: half
e1000g4         link: unknown   speed: 0     Mbps       duplex: half
e1000g5         link: unknown   speed: 0     Mbps       duplex: half
e1000g6         link: down      speed: 0     Mbps       duplex: half
e1000g7         link: up        speed: 1000  Mbps       duplex: full
root@4b>

and the ifconfig:

root@4b>ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000 
aggr1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 192.168.0.2 netmask ffffff00 broadcast 192.168.0.255
        ether 0:21:28:8e:86:ef 
e1000g6: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 3
        inet 10.180.1.40 netmask ffffffe0 broadcast 10.180.1.63
        ether 0:15:17:f0:62:1b 
e1000g7: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
        inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
        ether 0:15:17:f0:62:1a 
igb0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
        inet 10.151.50.74 netmask fffffc00 broadcast 10.151.51.255
        ether 0:21:28:8e:86:ee 
igb2: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 5
        inet 10.180.1.9 netmask ffffffe0 broadcast 10.180.1.31
        ether 0:21:28:8e:86:f0 
root@4b>

I'm sure it must be some small thing that im missing, but I still cant ping 192.168.0.10 (my laptop) from the server, or ping 192.168.0.1 from my laptop.
Hope you can help :slight_smile:

/Kerry

try a "ifconfig aggr1 down" and after that, try again with the ping. you have two interfaces in the same net/subnet. so the ping might go out through the other interface.

aggr1 is btw a link aggregation which you can have a look at with "dladm show-aggr".

1 Like

Hi Duke,

Excellent! It worked that time.
I see the problem now, from the ''dladm show -aggr'', it shows:

root@4b>dladm show-aggr
key: 1 (0x0001) policy: L4      address: 0:21:28:8e:86:ef (auto)
           device       address                 speed           duplex  link    state
           igb1         0:21:28:8e:86:ef          1000  Mbps    full    up      attached
           igb3         0:21:28:8e:86:f1          0     Mbps    half    down    standby
root@4b>

so igb3 is the standby in my current config, whereas i need to have e1000g7 as my standby.

I suppose I can use the 'dladm create-aggr' and create the correct interface?

this is link aggregation! your switch has to supoort this! if you want network failover features you have to use ipmp!

Link Aggregation vs IP Multipathing (Nicolas Droux' Blog)