|
|
NetworkNightmare.net/Support
|
|
| Optional Support
|
- We do NOT provide FREE "howto support"
- due to the nature of the wansim product, it is assumed the user knows enough about network simulations and network emulations and associated wansim technology
- However, for those that require handholding, we provide Professional Consulting as required
( see our entry for Linux-Consulting.com )
|
| gigEnn Support ( FAQ )
|
- Latest gigEnn release is 2010.0222 == fixed asymetric code
- gigEnn-T3 users should do an online upgrade
- gigEnn-OC12 users should call us for swapping your disks
- Latest gigEnn kernel is 2009.1117 == fixed smbfs problem
- gigEnn-T3 release 2009.1106 == fixed smbfs
- gigEnn-T3 w/ html-gui release is 2009.0622
- gigEnn-OC12 w/ html-gui release is 2009.0519
- Official gigEnn-T3 release is 2008.0229
- Official gigEnn-OC12 release is 2008.0311
- alpha and beta gigEnn-OC12 users prior to Feb 2008
- alpha and beta gigEnn-OC12 users should ask for the newest wansim menu interface to fix the queue size bug
- 2009.0522 == Minor tweeks and patches to gigEnn-T3 ( 2008.0229 )
- we have a patch for 3-way wansim ... 2008.0229 forgets the user defined ip#
- we have added an error warning of incorrect default gateway setting
- gigEnn-T3 users
- default gateway doesn't work
- the default gateway ip# must be in the same ip# range/mask as used for mgmt0, net1 or net2
- gigEnn-T3 users might encounter the "disappearing user defined parameters" ( /usr.rw )
#
# this usually occurs when the power plug is pulled as opposed to a proper shutdown from the wansim menu
#
# unfortunately, in order to support some new features such as:
reset to factory defaults, saving user test parameters, saving resulting runtime test data, the user can no longer just pull the power plug which is a bad practice in the first place
- To Fix the problem
- Check if /usr.rw is displayed
- drop to shell from the main wansim gui menu
- > df
#
# if /usr.rw is listed, you have a different problem
# if /usr.rw is NOT listed, you will need to fix the disk corruption ( see below )
- Fix the corrupted disk partition
( scandisk in microsoft terminology )
- > sudo fsck /dev/ad0s2a
#
# answer "y" to the question fsck is asking to fix itself
#
- Reboot for the quick and dirty test for the impatient
- Mount and verify the fix
#
# mount the previously corrupted disk partition that was fixed
- > sudo mount /dev/ad0s2a /usr.rw
#
# check that /usr.rw is mounted
- > sudo df
# -- if /usr.rw is listed ... the problem is solved ..
# -- if /usr.rw is NOT listed ... you have a different problem ..
#
# check your data
- > cat /usr.rw/etc/wansimconf/net-config
#
# all done, just reboot properly
- > sudo reboot
|
NN-Plus - NN-Minus Support
|
|
|
|
