Its fixed. I can now ping the GW with same setup. I had to install all
the recommended patches and security patches and that fixed the issue.

I ran this command `pca -asi mrs' to install all the patches

You have to have to reboot w/ reconfigure few times as requirement by some
of the patches and then rerun the `pca' command to finish the left over
patches


On 8/31/07, Asif Iqbal <[EMAIL PROTECTED]> wrote:
> I still cannot ping default gw (same for global and both zones zone1
> and zone2) from zone2.
>
> Here is how my setup looks like. What I fixed was the broadcast
> address. The ping issue has not been fixed yet.
>
>
>
> lo0: flags=2001000848<LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 
> 1
>         inet 127.0.0.1 netmask ff000000
> lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
> mtu 8232 index 1
>         zone lab-mns-02
>         inet 127.0.0.1 netmask ff000000
> lo0:2: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
> mtu 8232 index 1
>         zone testzone
>         inet 127.0.0.1 netmask ff000000
> lo0:3: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
> mtu 8232 index 1
>         zone lab-mns2-01
>         inet 127.0.0.1 netmask ff000000
> e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
>         inet 36.15.189.55 netmask ffffff00 broadcast 36.15.189.255
>         ether 0:14:4f:3f:eb:30
> e1000g0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
>         zone lab-mns2-01
>         inet 36.15.189.77 netmask ffffff00 broadcast 36.15.189.255
> e1000g1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
>         inet 0.0.0.0 netmask 0
>         ether 0:14:4f:3f:eb:31
> e1000g1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
>         zone testzone
>         inet 36.15.189.21 netmask ffffff00 broadcast 36.15.189.255
> e1000g2: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 8
>         inet 10.0.0.11 netmask ff000000 broadcast 10.255.255.255
>         ether 0:14:4f:3f:eb:32
> e1000g3: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
>         inet 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
>         ether 0:14:4f:3f:eb:33
> e1000g3:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
>         zone lab-mns-02
>         inet 36.15.189.15 netmask ffffff00 broadcast 36.15.189.255
> e1000g3:2: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
>         zone lab-mns-02
>         inet 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
>
>
>
>
>
> On 8/31/07, Ihsan Zaghmouth <[EMAIL PROTECTED]> wrote:
> >
> >  Could you briefly explain what did you do to fix it and what actions did
> > you commit since then  ...?
> >
> >
> >  Asif Iqbal wrote:
> >
> > good catch! however I fixed then since then. That was the only thing that
> > was wrong
> >
> >  I still have same problem.
> >
> >
> >  On 8/31/07, Ihsan Zaghmouth < [EMAIL PROTECTED]> wrote:
> >
> > >
> > > Asif,
> > >
> > > e1000g1:2:
> > flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
> > index 6
> > > zone zone2
> > > inet
> > > 36.15.189.77 netmask ffffff00 broadcast 63.171.189.255
> > > Your broadcast address is wrong, shouldn't be  36.15.189.255 ?
> > >
> > >
> > >
> > >
> > > Asif Iqbal wrote:
> > > On 8/31/07, Steffen Weiberle <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > Can you ping it from 'testzone'? It is configured on the same
> > > interface, e1000g1.
> > >
> > > Exact same problem w/ testzone. I cannot ping the default gw
> > >
> > >
> > >
> > >
> > > Asif Iqbal wrote:
> > >
> > >
> > > Hi All
> > >
> > > I have a global zone and two non-global zones on same ip segment. I
> > > can ping the default gw from global zone and zone1. But I cannot ping
> > > the gw from zone2. Any idea what could be the problem?
> > >
> > >
> > > Here is my setup.
> > >
> > > ifconfig -a on global
> > >
> > > lo0:
> > flags=2001000848<LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
> > mtu 8232 index 1
> > > inet
> > > 127.0.0.1 netmask ff000000
> > > lo0:1:
> > flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
> > > mtu 8232 index 1
> > > zone zone1
> > > inet
> > > 127.0.0.1 netmask ff000000
> > > lo0:2:
> > flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
> > > mtu 8232 index 1
> > > zone testzone
> > > inet
> > > 127.0.0.1 netmask ff000000
> > > lo0:3:
> > flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
> > > mtu 8232 index 1
> > > zone zone2
> > > inet
> > > 127.0.0.1 netmask ff000000
> > > e1000g0:
> > flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
> > index 2
> > > inet
> > > 36.15.189.55 netmask ffffff00 broadcast 36.15.189.255
> > > ether 0:14:4f:3f:eb:30
> > > e1000g1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4>
> > mtu 1500 index 6
> > >
> > > inet 0.0.0.0 netmask 0
> > > ether 0:14:4f:3f:eb:31
> > > e1000g1:1:
> > flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
> > index 6
> > >
> > > zone testzone
> > > inet 36.15.189.21 netmask ffffff00 broadcast
> > > 36.15.189.255
> > > e1000g1:2:
> > flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
> > index 6
> > > zone zone2
> > > inet
> > > 36.15.189.77 netmask ffffff00 broadcast 63.171.189.255
> > > e1000g2: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4>
> > mtu 1500 index 8
> > >
> > > inet 10.0.0.11 netmask ff000000 broadcast
> > > 10.255.255.255
> > > ether 0:14:4f:3f:eb:32
> > > e1000g3: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4>
> > mtu 1500 index 7
> > > inet
> > > 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
> > > ether 0:14:4f:3f:eb:33
> > > e1000g3:1:
> > flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
> > index 7
> > >
> > > zone zone1
> > > inet 36.15.189.15 netmask ffffff00 broadcast
> > > 36.15.189.255
> > > e1000g3:2:
> > flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
> > index 7
> > > zone zone1
> > > inet
> > > 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
> > >
> > > netstat -nr on global
> > > Routing Table: IPv4
> > > Destination Gateway Flags Ref Use Interface
> > >
> > > -------------------- -------------------- ----- ----- ------ ---------
> > > 36.15.189.0
> > > 36.15.189.55 U 1 47174 e1000g0
> > > 224.0.0.0
> > > 36.15.189.55 U 1 0 e1000g0
> > > default 36.15.189.254 UG 1 67052
> > >
> > >
> > > netstat -nr on zone1
> > > Routing Table: IPv4
> > > Destination Gateway Flags Ref Use Interface
> > > -------------------- -------------------- ----- ----- ------ ---------
> > >
> > > 36.15.189.0 36.15.189.15 U 1 6328 e1000g3:1
> > >
> > > 224.0.0.0 36.15.189.15 U 1 0 e1000g3:1
> > > default
> > > 36.15.189.254 UG 1 67062
> > > 127.0.0.1
> > > 127.0.0.1 UH 3 8152 lo0:1
> > >
> > > netstat -nr on zone2
> > > Routing Table: IPv4
> > > Destination Gateway Flags Ref Use Interface
> > > -------------------- -------------------- ----- ----- ------ ---------
> > >
> > > 36.15.189.0
> > > 36.15.189.77 U 1 4 e1000g1:2
> > > 224.0.0.0
> > > 36.15.189.77 U 1 0 e1000g1:2
> > > default 36.15.189.254 UG 1 67178
> > >
> > > 127.0.0.1
> > > 127.0.0.1 UH 4 38 lo0:3
> > >
> > >
> > > I can ping the GW 36.15.189.254 from global zone and zone1, but not from
> > zone2
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > >
> > >
> >
> >
> >
> >  --
> >  Asif Iqbal
> >  PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> >
> >
> >
> >
> > --
> >
> >
>
>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>


-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to