Solaris + Switches + VLANs = wtf?
Timothy Hildred
timhildred-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Mon Nov 8 19:24:19 UTC 2010
Hey guys!
I am attempting to put a solaris box that is currently on 2 subnets using
two interfaces and one switch onto a third subnet using a second switch and
a second nic. However, I cannot for the life of me bring it online in the
third subnet.
i have the first nic (two interfaces: e1000g0 and e1000g1) online in two
subnets; 192.168.XX5.13 and 192.168.XX6.13, netmask 255.255.255.0. This is
plugged into an HP switch with the appropriate vlans assigned to the ports
on the switch where the ethernet is plugged in.
i have the second nic (bnx0) plugged into the second switch, the appropriate
vlan set, and the ip statically set to 172.XX.237.21 with a netmask of
255.255.254.0
Here is the routing table from another box with a similar arrangement that
works that i would like to emulate:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.X15.0 * 255.255.255.0 U 0 0 0 eth0
172.XX.236.0 * 255.255.254.0 U 0 0 0 eth1
172.XX.0.0 172.XX.236.1 255.255.0.0 UG 0 0 0 eth1
169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
default woot.local 0.0.0.0 UG 0 0 0 eth0
Here is the routing table from the solaris box i am having trouble with:
IRE Table: IPv4
Destination Mask Gateway Device Mxfrg Rtt
Ref Flg Out In/Fwd
-------------------- --------------- -------------------- ------ ----- -----
--- --- ----- ------
default 0.0.0.0 192.168.X15.1 1500*
0 1 UG 5 0
172.XX.236.0 255.255.254.0 172.XX.236.21 bnx0 1500*
0 1 U 0 0
192.168.X15.0 255.255.255.0 192.168.X15.13 e1000g0 1500*
0 1 U 28 0
192.168.X16.0 255.255.255.0 192.168.X16.13 e1000g1 1500*
0 1 U 28 0
224.0.0.0 240.0.0.0 192.168.X15.13 e1000g0 1500*
0 1 U 0 0
127.0.0.1 255.255.255.255 127.0.0.1 lo0 8232*
0 5 UH 118 0
Any networking gurus that can weigh in on this one? Please?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20101108/4ced5e8c/attachment.html>
More information about the Legacy
mailing list