|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris 11.1 Release Notes Oracle Solaris 11.1 Information Library|
This section describes the network-related issues in Oracle Solaris 11.1.
On SPARC T2 and T3 platforms, the IPsec packet might be dropped if one or more CPUs on the domain are not associated with any control word queue (CWQ). The following error message might be displayed:
Thread[3000b87c000] is already bound to CPU which is not associated with any CWQ
Workaround: Choose one of the following workarounds:
Use the dladm command to bind the data-links to CPUs that are associated with a CWQ.
# dladm set-linkprop -p cpus=comma-separated-list-of-processor-IDs link-name
Reconfigure the domain so that all the CPUs on the system are associated with a CWQ.
Check for virtual CPUs (VCPU ) and crypto units (MAU) that are on the domain by using the ldm command.
% ldm ls -l domain-name
For more information, see the ldm(1) man page.
If CPUs are not associated with a crypto unit, turn the CPU offline by using the psradm command.
% psradm -f processor-ID
For more information, see the psradm(1) man page.
The system might hang when you run the tshark command on an interface with network traffic.
Workaround: Use the snoop command instead of tshark or wireshark command.
During the process of configuring your network after installing Oracle Solaris 11.1, if you switch from the Automatic network configuration profile (NCP) to the DefaultFixed NCP, the network might become unreachable. This behavior occurs upon a system reboot after the installation, during the first switch from the Automatic NCP to the DefaultFixed NCP. The network might be unreachable though the DefaultFixed NCP network configuration is valid.
Note - The behavior can occur in both global and non-global zones.
When you run the ping command, the following message is displayed:
# ping 192.168.10.3 ping: send to Network is unreachable
The network is not reachable if the system fails to disable the IP Filter service when the default network configuration mode is switched from a reactive NCP to the DefaultFixed NCP. You can run the following commands to check the status of the IP Filter service:
# svcs ipfilter STATE STIME FMRI online Oct_17 svc:/network/ipfilter:default
# ipfstat -io block out log all pass out quick on lo0 all pass out quick proto udp from any to any port = bootps block in log all pass in quick on lo0 all pass in quick proto udp from any to any port = bootpc
# ipfstat -io6 block out log all pass out quick on lo0 all pass out quick proto udp from ::/0 to ::/0 port = dhcpv6-server pass out quick proto ipv6-icmp from ::/0 to ::/0 block in log all pass in quick on lo0 all pass in quick proto udp from ::/0 to ::/0 port = dhcpv6-client pass in quick proto ipv6-icmp from ::/0 to ::/0
Workaround: Refresh the svc:/network/location:default SMF service.
# svcadm refresh svc:/network/location:default