Changes between Version 11 and Version 12 of Internal/OpenFlow/QuickStart


Ignore:
Timestamp:
Jun 16, 2011, 10:36:37 PM (13 years ago)
Author:
akoshibe
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/OpenFlow/QuickStart

    v11 v12  
    3131  [#flash 4.5 Flashing the switch] [[BR]]
    3232  [#ofcom 4.6 OpenFlow Commands] [[BR]]
    33  
     33  [#orbitof 4.7 Relevant to ORBIT] [[BR]]
    3434   
    3535----
    … …  
    859859
    860860The most surefire way to fix this is to get a new card, or reformat the problematic one. The easiest way to do it is to use a Windows machine. When the card shows up under "Devices", right click and go to 'Format'. A window saying "Format Secure Digital Storage Device" should pop up. Set "Allocation Unit size" to "default allocation size", and click 'Start'. You may need to confirm that you want to reformat the card. The card should be good to go in about a minute or so.
     861
     862Another known bug is a reported checksum error when booting from the SD card, despite having the proper license and an error-free kernel image. In this case the switch will boot from on-board flash (dev0):
     863
     864{{{
     865ROM 00.03.52
     866.............................
     867Checksum error.
     868............................
     869
     870BOOT 00.03.00
     871Loading from dev0 100%
     872
     873
     874login:
     875}}} 
     876
     877This can allegedly be fixed by re-flashing the card, but I have yet to see it boot properly once the error shows up.
    861878
    862879[[BR]]
    … …  
    10241041[#ofindex return to section index] [[BR]]
    10251042[#index return to main index]
     1043=== 4.7. OF mode IP8800 and ORBIT === #orbitof
     1044This section is meant for the odds-and-ends with respect to ORBIT deployments of the IP8800 in !OpenFlow mode.
     1045
     1046* ''kvm-big'': some of the VLANs on the IP8800 can be pointed to the Big Switch controller, at 172.16.0.14:6633. If doing so, don't forget to add the trunk as one of the virtual switch ports, e.g:
     1047{{{
     1048sw-sb-01> setvsi 22 37,38,48.22 tcp 172.16.0.14:6633 dpid 0x001010223232
     1049}}}
     1050
     1051* even when disabled with `disablevsi [vlan]`, virtual switches created on control VLANs will break Frisbee (e.g. imaging will time out). This is shown to be the case with all controllers present in ORBIT.   
    10261052===== -- ===== #bottom
    10271053