1 Reply Latest reply: Feb 1, 2012 2:05 PM by Ml Starkey-Oracle RSS

    SMCnsnmp in shared-ip non-global zone errors due to duplicate I/F index

    914691
      Hi all,
      I have Solaris 10 zones using the shared-ip model, with Net SMTP installed in the global and non-global zones.
      Smtpd starts normally in the global zone, but fails to start in the non-global zones, reporting this error ...

      $ sudo tail /zones/roots/uxNNNz4/root/var/log/snmpd.log
      error on subcontainer 'interface container' insert (-1)
      error on subcontainer 'interface container' insert (-1)
      error on subcontainer 'interface container' insert (-1)
      error on subcontainer 'interface container' insert (-1)
      error on subcontainer 'interface container' insert (-1)
      error on subcontainer 'interface container' insert (-1)
      error on subcontainer 'interface container' insert (-1)
      error on subcontainer 'interface container' insert (-1)
      error on subcontainer 'interface container' insert (-1)
      error on subcontainer 'interface container' insert (-1)

      This error was reported on OpenSolaris some time ago, reference ...
      (http://prefetch.net/blog/index.php/2009/05/10/net-snmp-should-now-work-in-an-opensolaris-non-global-zone) ...

      Net-snmp does not work in an opensolaris non-global zone:
      +"error on subcontainer ‘interface container’ insert (-1)"+
      These errors are caused by opensolaris bug #6640675, which causes all interfaces to be assigned an index value of 0 (this leads net-snmp to think there are duplicate interfaces). The fix was just integrated into Nevada, so hopefully the code will be back ported to Solaris 10.

      Example ifconfig in global zone (note index 2 for global and shared-ip VIPs)...

      lo0: flags=2001000849<UP,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 ux560z1
      inet 127.0.0.1 netmask ff000000
      lo0:2: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
      zone ux560z2
      inet 127.0.0.1 netmask ff000000
      lo0:3: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
      zone ux560z3
      inet 127.0.0.1 netmask ff000000
      lo0:4: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
      zone ux560z4
      inet 127.0.0.1 netmask ff000000
      nxge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
      inet 172.25.4.2 netmask fffffc00 broadcast 172.25.7.255
      ether 0:21:28:ba:9e:e4
      nxge0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
      zone ux560z1
      inet 172.25.4.3 netmask fffffc00 broadcast 172.25.7.255
      nxge0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
      zone ux560z2
      inet 172.25.4.4 netmask fffffc00 broadcast 172.25.7.255
      nxge0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
      zone ux560z3
      inet 172.25.4.5 netmask fffffc00 broadcast 172.25.7.255
      nxge0:4: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
      zone ux560z4
      inet 172.25.4.6 netmask fffffc00 broadcast 172.25.7.255


      QUESTIONS:
      1. Has the bug been reported for Solaris 10 ?
      2. Is a Solaris 10 patch available ?
      3. Is there a work-around or other ideas to get SMTP working in a Solaris shared-ip zoned.
      4. Exclusive-IP should fix it, but does that require a dedicated NIC per zone ?

      Thank You,
      KW