The release notes cover the following topics

• What's New in this Release
• Supported Operating Systems and Version Details
• Installation
• Log Files
• Reconcile User-modifiable Files
• Uninstallation

About VMware Smart Assurance GA Patch

A patch provides one or more fixes to a VMware Smart Assurance product. A patch can only be applied to the specific major or minor release and Service Pack of the particular product for which it is intended, this is called the product’s baseline.

What's New in this Release

The VMware Smart Assurance 10.1.2.14 introduces the following enhancement:

• Following System OIDs are certified in this release: 

Certified Devices

This section describes the devices certified and the certification impact in this patch.

Simple Certification

Simple certification involves only in configure file changes and the qualification of new OID in the currently existing driver. This section describes the devices certified in this patch.

Simple devices certified in the patch:

SR/TASC Number	Vendor Name	Description
SASS-15819/306440	CISCO	Certified the following components for the FirePOWER 1010 Firewall (System OID:.1.3.6.1.4.1.9.1.2483): Interface, Memory, and Processor.
SASS-15815/306335	FORTINET	Certified the following components for the FortiGate 601E Firewall (System OID:.1.3.6.1.4.1.12356.101.1.6006): Disk, Fan, Interface, Memory, PowerSupply, Processor, TemperatureSensor, and VoltageSensor.
SASS-15817/306336	FORTINET	Certified the following components for the FortiGate 4201F Firewall (System OID:.1.3.6.1.4.1.12356.101.1.42002): Disk, Fan, Interface, Memory, PowerSupply, Processor, TemperatureSensor, and VoltageSensor.
SASS-15813/306319	SILVERPEAK	Certified the following components for the spsECV Host (System OID:.1.3.6.1.4.1.23867.1.2.46): Interface, Memory, MemoryGroup, Processor, and ProcessorGroup.
SASS-15827/306414	CISCO	Certified the following components for the ENCS5408/K9 CIMC Switch (System OID:.1.3.6.1.4.1.9.1.2376): Fan, Memory, Port, Processor, TemperatureSensor, and VoltageSensor.
SASS-15847/306405	CISCO	Certified the following components for the 93180YC-FX3S Switch (System OID:.1.3.6.1.4.1.9.12.3.1.3.2378): AggregatePort, Card, Fan, Memory, Port, PowerSupply, Processor, TemperatureSensor, VoltageSensor, and Vlan.
SASS-15839/306387	JUNIPER	Certified the following components for the jnxProductQFX512048T Switch (System OID:.1.3.6.1.4.1.2636.1.1.1.4.82.27): AggregatePort, Card, CardRedundancyGroup, Disk, Fan, Interface, Memory, Port, PowerSupply, Processor, TemperatureSensor, VoltageSensor, and Vlan.
SASS-15836/306330	JUNIPER	Certified the following components for the NFX250ATTLS1 Router (System OID:.1.3.6.1.4.1.2636.1.1.1.4.138.3): Card, Disk, Interface, Memory, PowerSupply, Processor, and TemperatureSensor.
SASS-15833/306406	CISCO	Certified the following components for the 8202-SYS Router (System OID:.1.3.6.1.4.1.9.1.2650): Card, Fan, Interface, Memory, PowerSupply, Processor, TemperatureSensor, and VoltageSensor.
SASS-15823/306436	CISCO	Certified the following components for the Cisco Firepower Threat Defense Firewall (System OID:.1.3.6.1.4.1.9.1.2991): Interface, Memory, and Processor.
SASS-15860/306404	CISCO	Certified the following components for the ASR-9903 Router (System OID:.1.3.6.1.4.1.9.1.3075): AggregateInterface, Card, Fan, Interface, Memory, PowerSupply, and Processor.
SASS-15862/306399	CISCO	Certified the following components for the SF300-08 Switch (System OID:.1.3.6.1.4.1.9.6.1.82.8.4): Interface, Port, Processor, and Vlan.
SASS-15879/306395	CISCO	Certified the following components for the SF300-28MP Switch (System OID:.1.3.6.1.4.1.9.6.1.83.28.3): Fan, Interface, Port, Processor, TemperatureSensor, VoltageSensor, and Vlan.
SASS-15869/306434	FORTINET	Certified the following components for the fgtVM64AWS Firewall (System OID:.1.3.6.1.4.1.12356.101.1.45): Disk, Interface, Memory, and Processor.
SASS-15867/306431	CISCO	Certified the following components for the cevChassisN9KC93180YCFX3 Switch (System OID:.1.3.6.1.4.1.9.12.3.1.3.2193): AggregatePort, Card, Fan, Memory, Port, PowerSupply, Processor, TemperatureSensor, VoltageSensor, and Vlan.
SASS-15888/306339	CISCO	Certified the following components for the Meraki MX67 Router (System OID:.1.3.6.1.4.1.29671.2.118): Interface.
SASS-15969/306445	CISCO	Certified the following components for the Cisco8201-SYS Router (System OID:.1.3.6.1.4.1.9.1.2649): Card, Fan, Interface, Memory, PowerSupply, Processor, TemperatureSensor, and VoltageSensor.
SASS-15895/306433	CISCO	Certified the following components for the Nexus-7018 Swicth (System OID:.1.3.6.1.4.1.9.12.3.1.3.777): Card, CardRedundancyGroup, Fan, Interface, Memory, Port, PowerSupply, Processor, TemperatureSensor, VoltageSensor, and Vlan.
SASS-15898/306384	TIPPINGPOINT	Certified the following components for the 8200TX-IPS Firewall (System OID:.1.3.6.1.4.1.10734.1.3.51): Fan, FileSystem, Interface, Memory, PowerSupply, Processor, TemperatureSensor, and VoltageSensor.
SASS-15971/306448	FORTINET	Certified the following components for the FortiGate-1801F Firewall (System OID:.1.3.6.1.4.1.12356.101.1.15002): Disk, Fan, Interface, Memory, PowerSupply, Processor, TemperatureSensor, and VoltageSensor.
SASS-15918/306318	CISCO	Certified the following components for the ciscoFpr1120td Firewall (System OID:.1.3.6.1.4.1.9.1.2663): Interface, Memory, and Processor.
SASS-15911/306407	CHECKPOINT	Certified the following components for the CPAP-SG4200-NGFW Firewall  (System OID:.1.3.6.1.4.1.2620.1.6.123.1.99): Disk, Fan, FileSystem, Interface, Memory, PowerSupply, Processor, TemperatureSensor, and VoltageSensor.
SASS-15914/306415	JUNIPER	Certified the following components for the SRX380 Firewall (System OID:.1.3.6.1.4.1.2636.1.1.1.2.164): Card, Disk, Fan, Interface, Memory, PowerSupply, Processor, and TemperatureSensor.
SASS-15977/306456	JUNIPER	Certified the following components for the jnxProductEX2300port48MP Switch (System OID:.1.3.6.1.4.1.2636.1.1.1.4.132.8): Master:AggregatePort, Card, CardRedundancyGroup, Disk, Fan, Interface, Memory, Port, PowerSupply, Processor, TemperatureSensor, VCCRECardRedundancyGroup, and Vlan. Backup:Port.
SASS-15975/306455	JUNIPER	Certified the following components for the jnxProductEX2300port24MP Switch (System OID:.1.3.6.1.4.1.2636.1.1.1.4.132.7): Master:AggregatePort, Card, CardRedundancyGroup, Disk, Fan, Interface, Memory, Port, PowerSupply, Processor, TemperatureSensor, VCCRECardRedundancyGroup, and Vlan. Backup:Port.
SASS-15973/306454	JUNIPER	Certified the following components for the EX4300-48mp Switch (System OID:.1.3.6.1.4.1.2636.1.1.1.4.63.9): Master:Card, CardRedundancyGroup, Disk, Fan, Interface, Memory, Port, PowerSupply, Processor, TemperatureSensor, VCCRECardRedundancyGroup, and Vlan. Backup:Port.
SASS-15928/306438	VMWARE	Certified the following components for the VeloCloud edge Host (System OID:.1.3.6.1.4.1.45346.1.1): FileSystem, Interface, Memory, MemoryGroup, Processor, ProcessorGroup, and Vlan.
SASS-15937/306417	HUAWEI	Certified the following components for the S2720-28TP-EI Switch (System OID:.1.3.6.1.4.1.2011.2.23.529): Card, Interface, Memory, Port, Processor, TemperatureSensor, and Vlan.
SASS-15940/306411	JUNIPER	Certified the following components for the SRX4100 Firewall (System OID:.1.3.6.1.4.1.2636.1.1.1.2.142): AggregatePort, Card, Disk, Fan, Interface, Memory, PowerSupply, Processor, TemperatureSensor,VoltageSensor, and Vlan.
SASS-15954/306392	A10 NETWORKS	Certified the following components for the TH5440 Host with ICMP ONLY(System OID:.1.3.6.1.4.1.22610.1.3.44): Interface.
SASS-15909/306372	HP	Certified the following components for the arubaWiredSwitchJL636A Switch (System OID:.1.3.6.1.4.1.47196.4.1.1.1.70): AggregatePort, FileSystem, Interface, Memory, Port, and Processor.

Complex Certifications

Complex certifications involve re-certification, new device certifications, and involve new driver creations or multiple file changes. This section describes the devices certified in this patch.

Complex devices certified in the patch:

SR /TASC Number	Vendor Name	Description
SASS-15901/306369	CISCO	Certified the following components for the ciscoCat9200LFixedSwitchStack StackSwitchSystem (System OID:.1.3.6.1.4.1.9.1.2694): Card, Fan, Interface, Memory, Port, PowerSupply, Processor, TemperatureSensor, and Vlan.
SASS-15960/306377	REDWIN	Certified the following components for the WINLINK1000 oduHSUIntegratedAntenna WirelessAccessPoint (System OID:.1.3.6.1.4.1.4458.20.6.1.1): Port, and TemperatureSensor.
SASS-15964/306439	BROCADE	Certified the following components for the MLXe-8 Router (System OID:.1.3.6.1.4.1.1991.1.3.55.2.2): Card, Fan, Interface, Memory, Port, PowerSupply, and Processor.
SASS-15958/306488	CISCO	Certified the following components for the ASR1002F Router (System OID:.1.3.6.1.4.1.9.1.1116): Card, Interface, Memory, PowerSupply, Processor, TemperatureSensor, and VoltageSensor.
SASS-15930/306458	EXTREME	Certified the following components for the SummitX250e-24t Switch (System OID:.1.3.6.1.4.1.1916.2.93): AggregatePort, Card, Fan, Interface, Memory, Port, PowerSupply, Processor, and TemperatureSensor.
SASS-15981/306450	REDWARE	Certified the following components for the 5412XL Switch (System OID:.1.3.6.1.4.1.1872.1.13.3.2.2): Disk, Fan, Interface, Memory, Port, Processor, TemperatureSensor, and Vlan.
SASS-15966/306221	EFFICIENTIP	Certified the following components for the eip Host (System OID:.1.3.6.1.4.1.2440): Disk, FileSystem, Interface, Memory, MemoryGroup, PowerSupply, Processor, ProcessorGroup, and TemperatureSensor.
SASS-15916/306368	CISCO	Certified the following components for the ciscoFpr2110td Firewall (System OID:.1.3.6.1.4.1.9.1.2404): Card, Disk, Fan, Interface, Memory, PowerSupply, Processor, TemperatureSensor, and VoltageSensor.
SASS-15932/306122	CERAGON	Certified the following components for the Ceragon IP20C Host (System OID:.1.3.6.1.4.1.2281.1.20.2.2): Interface, TemperatureSensor, and VoltageSensor.
SASS-15944/306121	CERAGON	Certified the following components for the Ceragon IP20N Host (System OID:.1.3.6.1.4.1.2281.1.20.1.2): Card, Fan, Interface, TemperatureSensor, and VoltageSensor.

 

Certification impact

This section lists the impacted drivers and SysOIDs as a result of certification changes.

TASC Number	Impacted Drivers	Impacted SysOIDs
306450	CONT                      = RadwareAlteon HEALTH                  = RadwareAlteon VLAN                      = RadwareAlteon	.1.3.6.1.4.1.1872.1.13.3.6 .1.3.6.1.4.1.1872.1.13.3.12 .1.3.6.1.4.1.1872.1.13.3.12.1
306221	HOSTRESRCS         = EfficientIP-MIB2 HEALTH                    = EfficientIP	.1.3.6.1.4.1.2440
306368	CONT              = Cisco-FirePower-2110 HEALTH          = Cisco-FirePower-Health	.1.3.6.1.4.1.9.12.3.1.3.1410 .1.3.6.1.4.1.9.1.2406 .1.3.6.1.4.1.9.1.2405 .1.3.6.1.4.1.9.12.3.1.3.1417
306122	HEALTH          = Ceragon	.1.3.6.1.4.1.2281.1.20.2.1
306121	CONT             = Ceragon-MIB2 HEALTH          = Ceragon	.1.3.6.1.4.1.2281.1.20.2.2
306369	HEALTH             = Cisco-Router	.1.3.6.1.4.1.9.1.301 .1.3.6.1.4.1.9.1.320 .1.3.6.1.4.1.9.1.291 .1.3.6.1.4.1.9.1.271 .1.3.6.1.4.1.9.1.276 .1.3.6.1.4.1.9.1.288 .1.3.6.1.4.1.9.1.289 .1.3.6.1.4.1.9.1.338 .1.3.6.1.4.1.9.1.340 .1.3.6.1.4.1.9.1.319 .1.3.6.1.4.1.9.1.290 .1.3.6.1.4.1.9.1.384 .1.3.6.1.4.1.9.1.390 .1.3.6.1.4.1.9.1.286 .1.3.6.1.4.1.9.1.389 .1.3.6.1.4.1.9.1.308 .1.3.6.1.4.1.9.1.323 .1.3.6.1.4.1.9.1.324 .1.3.6.1.4.1.9.1.200 .1.3.6.1.4.1.9.1.123 .1.3.6.1.4.1.9.1.339 .1.3.6.1.4.1.9.1.374 .1.3.6.1.4.1.9.1.273 .1.3.6.1.4.1.9.1.274 .1.3.6.1.4.1.9.1.279 .1.3.6.1.4.1.9.1.313 .1.3.6.1.4.1.9.1.318 .1.3.6.1.4.1.9.1.399 .1.3.6.1.4.1.9.1.284 .1.3.6.1.4.1.9.1.451 .1.3.6.1.4.1.9.1.326 .1.3.6.1.4.1.9.1.466 .1.3.6.1.4.1.9.1.310 .1.3.6.1.4.1.9.1.468 .1.3.6.1.4.1.9.1.414 .1.3.6.1.4.1.9.1.444 .1.3.6.1.4.1.9.1.467 .1.3.6.1.4.1.9.1.469 .1.3.6.1.4.1.9.1.272 .1.3.6.1.4.1.9.1.437 .1.3.6.1.4.1.9.1.448 .1.3.6.1.4.1.9.1.392 .1.3.6.1.4.1.9.1.436 .1.3.6.1.4.1.9.1.417 .1.3.6.1.4.1.9.1.450 .1.3.6.1.4.1.9.1.391 .1.3.6.1.4.1.9.1.423 .1.3.6.1.4.1.9.1.470 .1.3.6.1.4.1.9.1.416 .1.3.6.1.4.1.9.1.438 .1.3.6.1.4.1.9.1.471 .1.3.6.1.4.1.9.1.439 .1.3.6.1.4.1.9.1.413 .1.3.6.1.4.1.9.1.401 .1.3.6.1.4.1.9.1.404 .1.3.6.1.4.1.9.1.476 .1.3.6.1.4.1.9.1.375 .1.3.6.1.4.1.9.1.381 .1.3.6.1.4.1.9.1.485 .1.3.6.1.4.1.9.5.56 .1.3.6.1.4.1.9.1.403 .1.3.6.1.4.1.9.1.425 .1.E13.6.1.4.1.9.1.365 .1.3.6.1.4.1.9.1.522 .1.3.6.1.4.1.9.5.1.3.1.1.2.914 .1.3.6.1.4.1.9.1.393 .1.3.6.1.4.1.9.1.489 .1.3.6.1.4.1.9.1.482 .1.3.6.1.4.1.9.1.488 .1.3.6.1.4.1.9.1.501 .1.3.6.1.4.1.9.1.502 .1.3.6.1.4.1.9.1.508 .1.3.6.1.4.1.9.1.449 .1.3.6.1.4.1.9.1.341 .1.3.6.1.4.1.9.1.342 .1.3.6.1.4.1.9.1.343 .1.3.6.1.4.1.9.1.503 .1.3.6.1.4.1.9.1.497 .1.3.6.1.4.1.9.1.495 .1.3.6.1.4.1.9.1.480 .1.3.6.1.4.1.9.1.516 .1.3.6.1.4.1.9.5.53 .1.3.6.1.4.1.9.5.54 .1.3.6.1.4.1.9.1.402 .1.3.6.1.4.1.9.5.55 .1.3.6.1.4.1.9.1.509 .1.3.6.1.4.1.9.1.499 .1.3.6.1.4.1.9.1.550 .1.3.6.1.4.1.9.1.538 .1.3.6.1.4.1.9.1.539 .1.3.6.1.4.1.9.1.542 .1.3.6.1.4.1.9.1.540 .1.3.6.1.4.1.9.1.560 .1.3.6.1.4.1.9.1.559 .1.3.6.1.4.1.9.1.528 .1.3.6.1.4.1.9.5.60 .1.3.6.1.4.1.9.1.533 .1.3.6.1.4.1.9.1.397 .1.3.6.1.4.1.9.1.317 .1.3.6.1.4.1.9.1.446 .1.3.6.1.4.1.9.1.382 .1.3.6.1.4.1.9.1.498 .1.3.6.1.4.1.9.1.500 .1.3.6.1.4.1.9.1.496 .1.3.6.1.4.1.9.1.299 .1.3.6.1.4.1.9.1.297 .1.3.6.1.4.1.9.1.253 .1.3.6.1.4.1.9.1.553 .1.3.6.1.4.1.9.1.479 .1.3.6.1.4.1.9.1.545 .1.3.6.1.4.1.9.1.546 .1.3.6.1.4.1.9.1.547 .1.3.6.1.4.1.9.1.544 .1.3.6.1.4.1.9.1.457 .1.3.6.1.4.1.9.1.537 .1.3.6.1.4.1.9.12.3.1.9.17.39 .1.3.6.1.4.1.9.1.552 .1.3.6.1.4.1.9.1.565 .1.3.6.1.4.1.9.1.558 .1.3.6.1.4.1.9.1.520 .1.3.6.1.4.1.9.1.395 .1.3.6.1.4.1.9.1.396 .1.3.6.1.4.1.9.1.322 .1.3.6.1.4.1.9.1.554 .1.3.6.1.4.1.9.1.557 .1.3.6.1.4.1.9.1.383 .1.3.6.1.4.1.9.1.347 .1.3.6.1.4.1.9.1.345 .1.3.6.1.4.1.9.1.344 .1.3.6.1.4.1.9.1.346 .1.3.6.1.4.1.9.1.270 .1.3.6.1.4.1.9.1.398 .1.3.6.1.4.1.9.1.362 .1.3.6.1.4.1.9.1.277 .1.3.6.1.4.1.9.1.900 .1.3.6.1.4.1.9.1.581 .1.3.6.1.4.1.9.1.351 .1.3.6.1.4.1.9.1.353 .1.3.6.1.4.1.9.1.354 .1.3.6.1.4.1.9.1.358 .1.3.6.1.4.1.9.1.548 .1.3.6.1.4.1.9.1.577 .1.3.6.1.4.1.9.1.578 .1.3.6.1.4.1.9.1.901 .1.3.6.1.4.1.9.1.576 .1.3.6.1.4.1.9.1.534 .1.3.6.1.4.1.9.1.626 .1.3.6.1.4.1.9.1.573 .1.3.6.1.4.1.9.1.459 .1.3.6.1.4.1.9.1.543 .1.3.6.1.4.1.9.1.620 .1.3.6.1.4.1.9.1.619 .1.3.6.1.4.1.9.1.592 .1.3.6.1.4.1.9.1.618 .1.3.6.1.4.1.9.1.627 .1.3.6.1.4.1.9.1.628 .1.3.6.1.4.1.9.1.629 .1.3.6.1.4.1.9.1.440 .1.3.6.1.4.1.9.1.562 .1.3.6.1.4.1.9.1.694 .1.3.6.1.4.1.9.1.679 .1.3.6.1.4.1.9.10.56 .1.3.6.1.4.1.9.1.657 .1.3.6.1.4.1.9.1.512 .1.3.6.1.4.1.9.1.642 .1.3.6.1.4.1.9.1.685 .1.3.6.1.4.1.9.1.660 .1.3.6.1.4.1.9.1.640 .1.3.6.1.4.1.9.1.690 .1.3.6.1.4.1.9.1.745 .1.3.6.1.4.1.9.1.758 .1.3.6.1.4.1.9.1.122 .1.3.6.1.4.1.9.1.571 .1.3.6.1.4.1.9.1.195 .1.3.6.1.4.1.9.1.659 .1.3.6.1.4.1.9.1.549 .1.3.6.1.4.1.9.1.641 .1.3.6.1.4.1.9.1.570 .1.3.6.1.4.1.9.1.733 .1.3.6.1.4.1.9.1.838 .1.3.6.1.4.1.9.1.674 .1.3.6.1.4.1.9.1.791 .1.3.6.1.4.1.9.1.789 .1.3.6.1.4.1.9.1.790 .1.3.6.1.4.1.9.1.792 .1.3.6.1.4.1.9.1.793 .1.3.6.1.4.1.9.1.795 .1.3.6.1.4.1.9.1.569 .1.3.6.1.4.1.9.1.568 .1.3.6.1.4.1.9.1.46 .1.3.6.1.4.1.9.1.182 .1.3.6.1.4.1.9.1.222 .1.3.6.1.4.1.9.1.638 .1.3.6.1.4.1.9.1.639 .1.3.6.1.4.1.9.1.566 .1.3.6.1.4.1.9.1.477 .1.3.6.1.4.1.9.1.658 .1.3.6.1.4.1.9.1.567 .1.3.6.1.4.1.9.1.664 .1.3.6.1.4.1.9.1.666 .1.3.6.1.4.1.9.1.826 .1.3.6.1.4.1.9.1.732 .1.3.6.1.4.1.9.1.744 .1.3.6.1.4.1.9.1.864 .1.3.6.1.4.1.9.1.863 .1.3.6.1.4.1.9.1.981 .1.3.6.1.4.1.9.1.821 .1.3.6.1.4.1.9.1.875 .1.3.6.1.4.1.9.1.877 .1.3.6.1.4.1.9.1.819 .1.3.6.1.4.1.9.1.675 .1.3.6.1.4.1.9.1.676 .1.3.6.1.4.1.9.1.663 .1.3.6.1.4.1.9.1.668 .1.3.6.1.4.1.9.1.903 .1.3.6.1.4.1.9.1.834 .1.3.6.1.4.1.9.1.1000 .1.3.6.1.4.1.9.1.876 .1.3.6.1.4.1.9.1.917 .1.3.6.1.4.1.9.1.788 .1.3.6.1.4.1.9.1.904 .1.3.6.1.4.1.9.1.852 .1.3.6.1.4.1.9.1.1033 .1.3.6.1.4.1.9.1.1072 .1.3.6.1.4.1.9.1.1014 .1.3.6.1.4.1.9.1.835 .1.3.6.1.4.1.9.1.905 .1.3.6.1.4.1.9.1.930 .1.3.6.1.4.1.9.1.824 .1.3.6.1.4.1.9.1.1044 .1.3.6.1.4.1.9.1.1043 .1.3.6.1.4.1.9.1.1041 .1.3.6.1.4.1.9.1.1042 .1.3.6.1.4.1.9.1.1046 .1.3.6.1.4.1.9.1.1045 .1.3.6.1.4.1.9.1.1095 .1.3.6.1.4.1.9.1.1047 .1.3.6.1.4.1.9.5.61 .1.3.6.1.4.1.9.1.728 .1.3.6.1.4.1.9.1.874 .1.3.6.1.4.1.9.1.173 .1.3.6.1.4.1.9.1.1149 .1.3.6.1.4.1.9.1.1027 .1.3.6.1.4.1.9.1.1023 .1.3.6.1.4.1.9.1.1026 .1.3.6.1.4.1.9.1.1022 .1.3.6.1.4.1.9.1.1021 .1.3.6.1.4.1.9.1.1226 .1.3.6.1.4.1.9.1.1024 .1.3.6.1.4.1.9.1.1019 .1.3.6.1.4.1.9.1.1191 .1.3.6.1.4.1.9.1.1144 .1.3.6.1.4.1.9.1.963 .1.3.6.1.4.1.9.1.1291 .1.3.6.1.4.1.9.1.857 .1.3.6.1.4.1.9.1.689 .1.3.6.1.4.1.9.1.837 .1.3.6.1.4.1.9.1.964 .1.3.6.1.4.1.9.1.1178 .1.3.6.1.4.1.9.1.862 .1.3.6.1.4.1.9.1.1145 .1.3.6.1.4.1.9.1.836 .1.3.6.1.4.1.9.1.1009 .1.3.6.1.4.1.9.1.1007 .1.3.6.1.4.1.9.1.1008 .1.3.6.1.4.1.9.1.1229 .1.3.6.1.4.1.9.1.1249 .1.3.6.1.4.1.9.1.1274 .1.3.6.1.4.1.9.1.1225 .1.3.6.1.4.1.9.1.1227 .1.3.6.1.4.1.9.1.1198 .1.3.6.1.4.1.9.1.1138 .1.3.6.1.4.1.9.1.1256 .1.3.6.1.4.1.9.1.1174 .1.3.6.1.4.1.9.1.1192 .1.3.6.1.4.1.9.1.1096 .1.3.6.1.4.1.9.1.1231 .1.3.6.1.4.1.9.1.1355 .1.3.6.1.4.1.9.1.1383 .1.3.6.1.4.1.9.1.1197 .1.3.6.1.4.1.9.1.1397 .1.3.6.1.4.1.9.1.1194 .1.3.6.1.4.1.9.1.1200 .1.3.6.1.4.1.9.1.1389 .1.3.6.1.4.1.9.1.1247 .1.3.6.1.4.1.9.1.1421 .1.3.6.1.4.1.9.1.782 .1.3.6.1.4.1.9.1.1413 .1.3.6.1.4.1.9.1.1103 .1.3.6.1.4.1.9.1.1384 .1.3.6.1.4.1.9.1.653 .1.3.6.1.4.1.9.1.1660 .1.3.6.1.4.1.9.1.1643 .1.3.6.1.4.1.9.1.1859 .1.3.6.1.4.1.9.1.1371 .1.3.6.1.4.1.9.1.1752 .1.3.6.1.4.1.9.1.1495 .1.3.6.1.4.1.9.1.1934 .1.3.6.1.4.1.9.1.1858 .1.3.6.1.4.1.9.1.1826 .1.3.6.1.4.1.9.1.1542 .1.3.6.1.4.1.9.1.1626 .1.3.6.1.4.1.9.1.1852 .1.3.6.1.4.1.9.1.1414 .1.3.6.1.4.1.9.1.2120 .1.3.6.1.4.1.9.1.1830 .1.3.6.1.4.1.9.1.2053 .1.3.6.1.4.1.9.1.1902 .1.3.6.1.4.1.9.1.1827 .1.3.6.1.4.1.9.1.1494 .1.3.6.1.4.1.9.1.1622 .1.3.6.1.4.1.9.1.2819
306377	HEALTH = Radwin Environment = Radwin:DeviceID	.1.3.6.1.4.1.4458.20.6.1.1
306458	CONT = Extreme-Summit	.1.3.6.1.4.1.1916.2.6 .1.3.6.1.4.1.1916.2.12 .1.3.6.1.4.1.1916.2.15 .1.3.6.1.4.1.1916.2.66 .1.3.6.1.4.1.1916.2.56 .1.3.6.1.4.1.1916.2.54 .1.3.6.1.4.1.1916.2.71 .1.3.6.1.4.1.1916.2.22 .1.3.6.1.4.1.1916.2.76 .1.3.6.1.4.1.1916.2.58 .1.3.6.1.4.1.1916.2.93 .1.3.6.1.4.1.1916.2.77 .1.3.6.1.4.1.1916.2.82 .1.3.6.1.4.1.1916.2.129 .1.3.6.1.4.1.1916.2.72 .1.3.6.1.4.1.1916.2.155 .1.3.6.1.4.1.1916.2.154 .1.3.6.1.4.1.1916.2.223 .1.3.6.1.4.1.1916.2.227
306439	MIB2-Data-Access-Driver	All SysOIDs
306488	MIB2-Data-Access-Driver	All SysOIDs

Product and Version Details

Product	Version Number Details
IP	From <BASEDIR>/smarts/bin/, type the following command: ./sm_server --version (Linux) The following output is displayed: sm_server: linux_rhAS50-x86-64/301032700 IP_NETWORK_SUITE: V10.1.2.14(198377), 19-Oct-2021 06:21:04 Copyright 2021, VMware Inc - Build 86 Foundation V10.1.2.1(198125), 08-Oct-2021 17:45:02 Copyright 2021, VMware Inc - Build 4

Installation

A patch installs files to the <BASEDIR>/smarts/local directory of the product. The Installation software performs the following actions:

• Backs up all files that are being replaced or merged.
• Merges changes from your current, user-modifiable configuration files into the new versions of the files from the patch.
• Displays complete summary at the end of patch installation.
• Displays the location of a log file that lists the results of merging the files.

Note: If the original product was installed on one computer and then was copied to another computer, the patch cannot be applied to the copied installation. You must apply the patch to the computer with the original installation, and then the results can be copied to another computer.

Patch Installation File

You can install the patch on the host where the IP product is running. 

Binary detail for IP-10.1.2.14 release is:

IP:setup-IP-linux-10_1_2_14-20211019-64BIT.bin

Note: You can download the binary from https://support.vmware.com.

Installation directory

In this document, the term <BASEDIR> represents the location where Smarts software is installed.

For UNIX, the default location is:/opt/InCharge/<productsuite>.

The <productsuite>; represents the Smarts product suite to which the product belongs.

Optionally, you can specify the root of <BASEDIR> to be something other than /opt/InCharge (on UNIX) but you cannot change the name of the <productsuite> that is part of the <BASEDIR>.

Install a new patch over an older patch

Patches are cumulative each successive patch includes all of the fixes from any previous patches. As a result, a newer patch can be installed on top of an older patch. The patch number, which increments itself for each successive patch, indicates the version. A patch with higher version number can be installed over a patch with a lower version number.

The Installation software checks the version of the installed product and the version to be installed at the beginning of its process. It will not allow an older version to be installed on top of a newer version.

Apply patch using CLI mode

CLI mode provides a text-based method for invoking the Installation software. This mode is intended for UNIX platforms with non-graphic (text-only) consoles. The CLI mode installation follows the same process as the wizard mode but displays text on the terminal screen and requires user responses on the keyboard.

Run CLI mode

1. Change directory to the directory where you typically store patches, for example, ./opt.
2. Run following setup command and then press Enter. Replace xx with the relevant product name, for example: ESM. For exact name, see the Patch Installation File section:

           Setup command syntax for CLI mode (Linux): ./setup-IP-linux-10_1_2_14-20211019-64BIT.bin.

           A welcome message with information about the installation appears.

Note: Stop all VMware Smart Assurance services and processes that use programs or libraries from the product being upgraded or installed before performing the installation.

User selections and navigation in CLI mode

• During the patch installation process, at the end of each screen of text, you are prompted with a set of options. For example:

           type 'back' - to go to the previous step

           type 'quit' - to cancel anytime

• Select a choice by typing the text and press Enter.
• Accept the default choice, and press Enter.
• Other screens have different choices. For example when the license agreement is displayed, the following prompt appears:

           Press any key to continue to read license agreement or press '0' to advance to end.

• At the end of the license agreement, the installation process displays the first of several menus.

           Choose from the following (Y/N) options:

           Y - to accept the terms of the license agreement.

           N - not to accept the terms of the license agreement.

• Type the desired selection and press Enter. In the case of the license agreement, you must accept the agreement by typing Y and pressing Enter.

           The screen is displayed with an Get User Input. Choose the base location by entering the correct number.

            For example, type 1 to choose the default location for installation and press Enter.

      Get User Input

      1) /opt/InCharge 10.1.2.*

           For example, if the product name is ESM and default install folder is /opt/InCharge, the installer displays:

           VMware Smart Assurance Server Manager Suite will be installed in the following location:

           Product Name: ESM

           Install Folder: /opt/InCharge

• Press Enter to continue the installation.
• Press Enter to exit the installer.

           When the patch installation is complete, reconcile the configuration files as described in Reconcile user-modifiable files.

Apply patch using Unattended (Silent) mode

Unattended mode installs the patch without user input or a response file. When invoking the install program, specify the location of the product suite to be patched.

In order to invoke an unattended installation of the patch, type the appropriate setup command from below table and then press Enter. Replace “xx” with the relevant product name, for example, ESM. For exact name, see the Patch Installation File section:

Setup command syntax for unattended mode (Linux):setup-IP-linux-10_1_2_14-20211019-64BIT.bin -i silent -DrpProduct.installLocation=/opt/InCharge.

Where xx represents the product name.

Note: You must provide the correct base installation location. For example: base10.1 build is installed inside /opt/InCharge.

Once the installation is completed inside /tmp ** log file will be created with the summary. When the patch installation is complete, reconcile the configuration files as described in Reconcile user-modifiable files.

Log Files

Patch report and log file locations, lists the files that the Installation software creates during the install process.

Patch report and log file locations:

Name	Path	File Name
Install log	<BASEDIR>/smarts/setup/logs	Install.<product>_SUITE. <patchversion>.log
Merged files log	<BASEDIR>/smarts/setup/logs	merge-summary-<patch version>.log

Install log

The installer creates an Install log file listing all actions performed by the installation. You need not read this file unless you suspect an installation failure.

If the installation process fails, the log files are located in a temporary directory, for example /tmp or C:\temp. A non-zero status indicates a failure.

Merged files Log

This log lists the files in the BASEDIR/smarts/local directory structure that were merged. For each merged file, the log lists the location and name of the file. If any file cannot be merged due to conflicts, this is also noted. In addition, the log lists the name and location for unmerged versions of all user-modifiable files that are included in the patch.

For example, in case of ESM: 

• Summary of merge operation can be found at location: /opt/InCharge/ESM/smarts/setup/logs/merge-summary-10.x.x.x.log
• For more detail logs: /opt/InCharge/ESM/smarts/setup/logs/detail-merge-10.1.2.14.log

If there were any conflict during the merge operation, the old local backup file will be saved as "File_Name.bkp" in its same location. These conflict files needs to be merged manually before starting the server.

Review the results of the reconciliation process

The results of the reconciliation analysis performed during the installation and all actions taken are included in the merged files log located in <BASEDIR>/smarts/setup/logs. The name of the log file is: install.merge.<patch version>.log

Reconcile User-modifiable Files

The Installation software is designed to preserve your changes to user-modifiable files when installing new versions of these files. Existing changes to user-modifiable files are always automatically merged. All files are merged by default.

The Installation software also creates a backup of all the versions of the user-modifiable files to ensure that you will not lose any configuration data.

Review the results of the reconciliation process

The results of the reconciliation analysis performed during the installation and all actions taken are included in the merged files log located in <BASEDIR>/smarts/setup/logs. The name of the log file is: install.merge.<patch version>.log.

Determine which files require action by reviewing the merged files log generated by the install process:

1. Using any editor, open and review the log:

   <BASEDIR>/smarts/setup/log/Install.Merge.10.x.x.x.log.

2. Review the log:

   1. Resolve conflicts in files manually. See Resolve the issue in conflict files.
   2. During the installation, the entries that indicate file merges without conflicts that resulted in automerge files.

Resolve issues in conflict files

If a conflict occurs for any file in the same local directory of the file location, you can find the below files:

• One is the conflict file. For example, <filename>
• Another file is .bak.001. For example, <filename>.bak.001

Review the conflict files and resolve issues using the following procedure:

1. Open the user-modifiable file where the conflict occurs using sm_edit.

   For example, the conflict file for esm.param.conf is named esm-param.conf.

2. Review and resolve the conflict manually.
3. Save and close the file.

To use patch introduced file (for example, esm-param.conf):

1. Rename the original conflict file. (For example, if the conflict file name is esm-param.conf, rename the file esm-param.conf to esm-param.conf_old).
2. Rename the <filename>.bak.001 file to the original file name <filename> by removing .bak.001 extension.

   For example, if the patch file name is esm-param.conf.bak.001, rename it to the esm-param.conf to use the original file.

3. Save and close the file.

Note: All the user-modifiable unmerged files before patch installation, are backed up in "<BASEDIR>/<Product Name>/smarts" location. By default, the backup directory is hidden.

Uninstallation

Uninstalling a patch removes all previously applied patches and returns the software to the baseline product version.

Note:Root privileges are required to uninstall a patch. Use either the uninstaller program to uninstall a patch. Failure to use one of these methods can result in an unstable system and/or inconsistent product directories.

Before uninstallation

You must complete the following task before uninstalling the patch:

• Stop all VMware Smart Assurance services and processes that use programs or libraries from the product.

Roll back to a previous patch

If you want to revert to a previous patch, you must:

• Uninstall the currently installed patch to return to the baseline version.

• Reinstall the previous patch.

For example, to revert from Patch 2 to Patch 1, uninstall Patch 2, and then reinstall Patch 1.

Uninstall Patch Using the Uninstaller Program

Use the uninstaller program to uninstall a patch:

Note: Do not to use the uninstaller program in the _uninst directory because it will remove the entire product.

1. Change the directory or use the file navigator to find the _rpuninst directory.

   For Example: /opt/InCharge/<Product>/_rpuninst on UNIX systems.

2. Invoke the uninstaller program.

   For example: ./uninstaller on UNIX systems.

3. Press Enter to continue the uninstallation.

Uninstall Patch Using Unattended (Silent) Mode

Use the uninstaller program to uninstall a patch.

Note: Do not to use the uninstaller program in the _uninst directory because it will remove the entire product.

1. Change the directory or use the file navigator to find the _rpuninst directory.

   For Example: /opt/InCharge/<Product>/_rpuninst on UNIX systems.

2. Execute the uninstaller program.

   ./uninstaller -i silent on UNIX systems.

3. Press Enter to continue the uninstallation.