↑ Collapse Diff ↑
 
new file 100644
1
 

	
2
 
/*
3
 
 * DO NOT EDIT THIS FILE - IT IS GENERATED BY THE DRIVER BUILD.
4
 
 *
5
 
 * If you need to change the driver's name spaces, look in the scons
6
 
 * files for the driver's defineVmkDriver() rule.
7
 
 */
8
 

	
9
 
VMK_NAMESPACE_REQUIRED("com.vmware.usb", "9.2.2.0");
...
 
@@ -170,6 +170,9 @@ typedef vmk_uint32 vmk_LinkSpeed;
170 170
 
/** Uplink link speed 10000Mbps */
171 171
 
#define VMK_LINK_SPEED_10000_MBPS    10000
172 172
 

	
173
 
/** Uplink link speed 20000Mbps */
174
 
#define VMK_LINK_SPEED_20000_MBPS    20000
175
 

	
173 176
 
/** Uplink link speed 40000Mbps */
174 177
 
#define VMK_LINK_SPEED_40000_MBPS    40000
175 178
 

	
...
 
@@ -1354,6 +1354,31 @@ vmk_NmpSatpAPActivatePathsHelper (
1354 1354
 
   vmk_uint32 starStopUnitTimeoutMs, 
1355 1355
 
   vmk_Bool *pathsActivated);
1356 1356
 

	
1357
 
/*
1358
 
 ************************************************************************
1359
 
 *  vmk_NmpSatpSetProbeFailuresOptionFlag --                       */ /**
1360
 
 *
1361
 
 *  \ingroup NMP_SATP_API
1362
 
 *  \brief Sets the option to handle retry failures for probe commands.
1363
 
 *
1364
 
 *  Sets the SATP's preference on handling continuous RETRY failures
1365
 
 *  for probe sync commands. If set then the path will be marked dead
1366
 
 *  after a timeout else the path state will not be updated. If a SATP
1367
 
 *  uses NMP's default probing mechanism via
1368
 
 *  vmk_NmpSatpAPUpdatePathStatesHelper or
1369
 
 *  vmk_NmpSatpAAUpdatePathStatesHelper then this API must be called
1370
 
 *  from the SATP when the config option 'enable_action_OnRetryErrors'
1371
 
 *  or 'disable_action_OnRetryErrors' is set.
1372
 
 *
1373
 
 *  \param[in] nmpDevice   NMP device
1374
 
 *  \param[in] flag        VMK_TRUE indicates option is ON
1375
 
 *                         VMK_FALSE indicates option is OFF
1376
 
 *
1377
 
 ************************************************************************
1378
 
 */
1379
 
void
1380
 
vmk_NmpSatpSetProbeFailuresOptionFlag(vmk_NmpDevice *nmpDevice, vmk_Bool flag);
1381
 

	
1357 1382
 
#endif /* _VMK_NMP_SATP_H_ */
1358 1383
 
/** @} */
1359 1384
 
/** @} */
...
 
@@ -170,6 +170,9 @@ typedef vmk_uint32 vmk_LinkSpeed;
170 170
 
/** Uplink link speed 10000Mbps */
171 171
 
#define VMK_LINK_SPEED_10000_MBPS    10000
172 172
 

	
173
 
/** Uplink link speed 20000Mbps */
174
 
#define VMK_LINK_SPEED_20000_MBPS    20000
175
 

	
173 176
 
/** Uplink link speed 40000Mbps */
174 177
 
#define VMK_LINK_SPEED_40000_MBPS    40000
175 178
 

	
...
 
@@ -1354,6 +1354,31 @@ vmk_NmpSatpAPActivatePathsHelper (
1354 1354
 
   vmk_uint32 starStopUnitTimeoutMs, 
1355 1355
 
   vmk_Bool *pathsActivated);
1356 1356
 

	
1357
 
/*
1358
 
 ************************************************************************
1359
 
 *  vmk_NmpSatpSetProbeFailuresOptionFlag --                       */ /**
1360
 
 *
1361
 
 *  \ingroup NMP_SATP_API
1362
 
 *  \brief Sets the option to handle retry failures for probe commands.
1363
 
 *
1364
 
 *  Sets the SATP's preference on handling continuous RETRY failures
1365
 
 *  for probe sync commands. If set then the path will be marked dead
1366
 
 *  after a timeout else the path state will not be updated. If a SATP
1367
 
 *  uses NMP's default probing mechanism via
1368
 
 *  vmk_NmpSatpAPUpdatePathStatesHelper or
1369
 
 *  vmk_NmpSatpAAUpdatePathStatesHelper then this API must be called
1370
 
 *  from the SATP when the config option 'enable_action_OnRetryErrors'
1371
 
 *  or 'disable_action_OnRetryErrors' is set.
1372
 
 *
1373
 
 *  \param[in] nmpDevice   NMP device
1374
 
 *  \param[in] flag        VMK_TRUE indicates option is ON
1375
 
 *                         VMK_FALSE indicates option is OFF
1376
 
 *
1377
 
 ************************************************************************
1378
 
 */
1379
 
void
1380
 
vmk_NmpSatpSetProbeFailuresOptionFlag(vmk_NmpDevice *nmpDevice, vmk_Bool flag);
1381
 

	
1357 1382
 
#endif /* _VMK_NMP_SATP_H_ */
1358 1383
 
/** @} */
1359 1384
 
/** @} */
1
 
#define BUILD_NUMBER "build-00000"
2
 
#define BUILD_NUMBER_NUMERIC 00000
3
 
#define BUILD_NUMBER_NUMERIC_STRING "00000"
4
 
#define PRODUCT_BUILD_NUMBER "product-build-00000"
5
 
#define PRODUCT_BUILD_NUMBER_NUMERIC 00000
6
 
#define PRODUCT_BUILD_NUMBER_NUMERIC_STRING "00000"
1
 
#define BUILD_NUMBER "build-2899292"
2
 
#define BUILD_NUMBER_NUMERIC 2899292
3
 
#define BUILD_NUMBER_NUMERIC_STRING "2899292"
4
 
#define PRODUCT_BUILD_NUMBER "product-build-30998"
5
 
#define PRODUCT_BUILD_NUMBER_NUMERIC 30998
6
 
#define PRODUCT_BUILD_NUMBER_NUMERIC_STRING "30998"
...
 
@@ -3,16 +3,16 @@ This server should have SSH access enabled: Customize System/View Logs ->
3 3
 
Troubleshooting Options -> Enable SSH
4 4
 

	
5 5
 
To install the package create a working directory on a datastore on the
6
 
ESXi server, e.g., "/vmfs/volumes/Storage1/install" and copy the binary
6
 
ESXi server, e.g., "/vmfs/volumes/datastore1/" and copy the binary
7 7
 
disclosure created by the build:
8 8
 

	
9
 
scp centos-5.3-x64.tar root@esx.example.org:/vmfs/volumes/Storage1/install/centos-5.3-x64.tar
9
 
scp centos-5.3-x64.tar root@esx.example.org:/vmfs/volumes/datastore1/centos-5.3-x64.tar
10 10
 

	
11 11
 
On the ESXi host, verify the shipped version:
12 12
 

	
13 13
 
Replace the shipped version with the custom build:
14 14
 

	
15
 
cd /vmfs/volumes/Storage1/install
15
 
cd /vmfs/volumes/datastore1/
16 16
 
tar xf centos-5.3-x64.tar
17 17
 
./update-drivers.sh
18 18
 

	

Changeset was too big and was cut off... Show full diff anyway

0 comments (0 inline, 0 general)