Custom Query (16363 matches)
Results (169 - 171 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1196 | fixed | vnic_setup.sh fails with more than 1 active NIC | ||
| Description |
If one has more than 1 active NIC, vnic_setup.sh patch to fix attached ... |
|||
| #1498 | fixed | vnic_setup.sh doesn't work on OpenSolaris => Fixed in 2.0.2 | ||
| Description |
On a system with OpenSolaris build 88 the vnic_setup.sh script fails # ./vnic_setup.sh 08:00:27:c1:71:1f Invalid link name: LINK |
|||
| #11534 | fixed | vnic VID property is misteriously zeroed on Solaris 11.1 after VM start | ||
| Description |
I use VB 4.2.8 On Solaris 11.1 SRU1.4 VID property for vnic interface is zeroed after VM start. ORACLE VB uses that vnic interface. vnic created on the base of dot1Q trunk. The same problem was observed for vlan interfaces too. How to reproduce:
Workaround: After VM start restore VID setting: dladm modify-vnic -v 998 v4vid998link0 That helps to restore IP connectivity for that VM. NOTE 1: the issue appears for the first time after VM started. VM reboot process doesn't affect IP connectivity. Only VM poweroff makes the issue to appear again. NOTE 2: vlan interfaces are affected by the issue too. NOTE 3: Seen the problem in 4.1.x and 4.2.x builds. |
|||

