http://defect.opensolaris.org/bz/show_bug.cgi?id=8790





--- Comment #1 from Anurag S. Maskey <Anurag.Maskey at Sun.COM>  2009-05-08 
06:19:58 ---
In the User NCP, when new phys NCUs are added as new links are discovered, they
have manual activation-mode with enabled turned on.  Only when upgrading from
Phase 0/0.5 will phys NCUs in User NCP have prioritized activation-mode.

Also, when the NCUs are created, both phys and ip NCUs are created.

bash-3.2# dladm show-link
LINK        CLASS    MTU    STATE    OVER
bge0        phys     1500   up       --
bge1        phys     1500   up       --
bash-3.2# nwamcfg list ncp User
NCUs:
        ip      bge0
        phys    bge0
bash-3.2# svcadm restart nwam
bash-3.2# nwamcfg list ncp User
NCUs:
        ip      bge0
        phys    bge0
        ip      bge1
        phys    bge1
bash-3.2# nwamcfg
nwamcfg> select ncp User
nwamcfg:ncp:User> list ncu phys bge1
NCU:bge1
        type            link
        class           phys
        parent          "User"
        enabled         true
        activation-mode manual
nwamcfg:ncp:User> list ncu ip bge1
NCU:bge1
        type            ip
        class           ip
        parent          "User"
        enabled         true
        ip-version      ipv4,ipv6
        ipv4-addrsrc    dhcp
        ipv6-addrsrc    dhcp,autoconf
nwamcfg:ncp:User>

If at least one NCU for a given interface already exists, then the missing NCUs
are not created.  In other words, if phys NCU bge1 exists, then ip NCU bge1 is
not created.

bash-3.2# dladm show-link
LINK        CLASS    MTU    STATE    OVER
bge0        phys     1500   up       --
bge1        phys     1500   up       --
bash-3.2# nwamcfg list ncp User
NCUs:
        ip      bge0
        phys    bge0
        phys    bge1
bash-3.2# svcadm restart nwam
bash-3.2# nwamcfg list ncp User
NCUs:
        ip      bge0
        phys    bge0
        phys    bge1
bash-3.2#

-- 
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

Reply via email to