Avoid populating StaticNameServers property

Redfish ethernet schema has two properties for nameservers
1.NameServers - Represents nameservers currently in use on Interface
2.StaticNameServers -Repre

Avoid populating StaticNameServers property

Redfish ethernet schema has two properties for nameservers
1.NameServers - Represents nameservers currently in use on Interface
2.StaticNameServers -Represents only statically defined set of DNS

As we have only one DBUS property `Nameservers` which is used for both
the static and dynamic nameservers, So the idea behind this commit is
to not populate the StaticnameServers property when DHCP mode is
enabled.

Tested By:

GET https://${BMC_IP}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0

Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I64f66bde55ec41dc78befbb659a0cbc425bbc24b

show more ...

Redfish(Network): IPV4 DHCP ipaddreses dont show gateway when in DHCP mode

Tested by:
configuring DHCP,
GET https://${BMC_IP}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0

Signed-off-by: Ravi Tej

Redfish(Network): IPV4 DHCP ipaddreses dont show gateway when in DHCP mode

Tested by:
configuring DHCP,
GET https://${BMC_IP}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0

Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
Change-Id: Ic7067db41fbb8327ef55cc7552f9153d1ecfb63a

show more ...

Redfish(Network): Add support for IPv4StaticAddresses

Added GET and PATCH support for IPv4StaticAddresses
and modified IPv4Addresses as read-only property

Tested by:
GET
PATCH -D patch.txt -d '{"IP

Redfish(Network): Add support for IPv4StaticAddresses

Added GET and PATCH support for IPv4StaticAddresses
and modified IPv4Addresses as read-only property

Tested by:
GET
PATCH -D patch.txt -d '{"IPv4StaticAddresses": [{},{},{"Address": "10.7.8.7","SubnetMask": "255.255.0.0","Gateway":"10.7.8.1"}]}'
PATCH -D patch.txt -d '{"IPv4StaticAddresses": [{},{"Address": "10.7.7.8","SubnetMask": "255.255.0.0","Gateway":"10.7.7.1"}]}'
PATCH -D patch.txt -d '{"IPv4StaticAddresses": [null,{},{"Address": "10.7.7.9","SubnetMask": "255.255.0.0","Gateway":"10.7.7.1"}]}']}'
PATCH -D patch.txt -d '{"IPv4StaticAddresses": [{},{"Address": "10.8.8.9"}]}'

Tested with validator and no errors.

Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
Change-Id: I580787933f1d93d0734e32f71ac9fc80dc108247

show more ...

[Redfish] Add FQDN and IPv6Address in NetworkProtocol and EthernetInterface

FQDN and IPv6Address are mandatory properties in OCP profile.

Tested:
GET /redfish/v1/Managers/bmc/NetworkProtocol HTTP/1

[Redfish] Add FQDN and IPv6Address in NetworkProtocol and EthernetInterface

FQDN and IPv6Address are mandatory properties in OCP profile.

Tested:
GET /redfish/v1/Managers/bmc/NetworkProtocol HTTP/1.1
Response:
{
"@odata.context": "/redfish/v1/$metadata#ManagerNetworkProtocol.ManagerNetworkProtocol",
"@odata.id": "/redfish/v1/Managers/bmc/NetworkProtocol",
"@odata.type": "#ManagerNetworkProtocol.v1_4_0.ManagerNetworkProtocol",
"Description": "Manager Network Service",
"FQDN": <host name>.<domain name>,
"HTTPS": {
"Port": 443,
"ProtocolEnabled": true
},
"HostName": <host name>,
...
}

GET /redfish/v1/Managers/bmc/EthernetInterfaces/eth0 HTTP/1.1
Response:
{
"@odata.context": "/redfish/v1/$metadata#EthernetInterface.EthernetInterface",
"@odata.id": "/redfish/v1/Managers/bmc/EthernetInterfaces/eth0",
"@odata.type": "#EthernetInterface.v1_4_1.EthernetInterface",
...
"FQDN": <host name>.<domain name>,
"HostName": <host name>,
...
"IPv6Addresses": [],
...
}

Signed-off-by: Jennifer Lee <jennifer1.lee@intel.com>
Change-Id: I0ca8f98523cbcfc935e0ac3bbf93f87762ff183b

show more ...

Redfish: Remove "state" response content from PATCH commands

A PATCH command should not return any JSON content for the NICs. PATCH
commands should only return success or failure responses.

Reporti

Redfish: Remove "state" response content from PATCH commands

A PATCH command should not return any JSON content for the NICs. PATCH
commands should only return success or failure responses.

Reporting state based upon the input to the command is, in most
instances, going to be incorrect in comparison to the actual state of
the HW. For example: moving from static addresses to a DHCP assigned
address cannot be predicted based upon the input. It also takes
several seconds for a DHCP transaction to complete, which creates a
significant temporal lag between what was sent and what will be.

Tested: Performed the following tests:

For IPv4:
"IPv4Addresses": [
{},
{
"Address": "192.168.20.12",
"SubnetMask": "255.255.255.0",
"Gateway": "192.168.20.1"
}
]
For IPv6:
"IPv6StaticAddresses": [
{
"Address": "2001::5:4:3:4",
"PrefixLength": 64
}
]

Both tests complete without emitting any JSON content.

Change-Id: Ic7eb824eb6d996d85d52a3b7c855e9825f4a0d87
Signed-off-by: Johnathan Mantey <johnathanx.mantey@intel.com>

show more ...

Redfish: Remove the IPv4 AddressOrigin read-only element

The AddressOrigin entry in the IPv4Addresses schema is read-only. It
is not permitted to PATCH the AddressOrigin.

Tested: Added the "Address

Redfish: Remove the IPv4 AddressOrigin read-only element

The AddressOrigin entry in the IPv4Addresses schema is read-only. It
is not permitted to PATCH the AddressOrigin.

Tested: Added the "AddressOrigin": "DHCP" to an IPv4Addresses PATCH
command. The JSON response is "property is not in the list of valid
properties".

Change-Id: Id7d41e9f1b393738e20725495b3821dd2f9f69d0
Signed-off-by: Johnathan Mantey <johnathanx.mantey@intel.com>

show more ...

Redfish: Correctly identify IPv4 LinkLocal vs. LinkGlobal

Self assigned IPv4 addresses must be flagged as LinkLocal, not
LinkGlobal. Likewise global IPv4 addresses must be flagged as
LinkGlobal.

Ch

Redfish: Correctly identify IPv4 LinkLocal vs. LinkGlobal

Self assigned IPv4 addresses must be flagged as LinkLocal, not
LinkGlobal. Likewise global IPv4 addresses must be flagged as
LinkGlobal.

Change-Id: I9f6f0ceb3d312dd0198cb54c59c579ed96fbc38a
Signed-off-by: Johnathan Mantey <johnathanx.mantey@intel.com>

show more ...

Redfish: Correct PATCH for IPv6 static addresses

Manipulating IPv6 static addresses works the same way as IPv4 static
addresses. Keep the IPv6StaticAddresses collection, and remove write
access from

Redfish: Correct PATCH for IPv6 static addresses

Manipulating IPv6 static addresses works the same way as IPv4 static
addresses. Keep the IPv6StaticAddresses collection, and remove write
access from the read-only IPv6Addresses collection.

Change-Id: If58c858c676f7ae843e0642800a4083c5df79d1d
Signed-off-by: Johnathan Mantey <johnathanx.mantey@intel.com>

show more ...

Redfish(Network): Add support for IPv6Addresses and IPv6StaticAddresses

Added GET support for IPv6Addresses
Added GET and PATCH support for IPv6StaticAddresses

Tested by:
GET
PATCH -D patch.txt -d

Redfish(Network): Add support for IPv6Addresses and IPv6StaticAddresses

Added GET support for IPv6Addresses
Added GET and PATCH support for IPv6StaticAddresses

Tested by:
GET
PATCH -D patch.txt -d '{"IPv6StaticAddresses": [{"Address": "2002:905:150e:301:72e2:84ff:fe14:222","PrefixLength": 64}]}'
PATCH -D patch.txt -d '{"IPv6StaticAddresses": [{},{"Address": "2002:905:150e:301:72e2:84ff:fe14:333","PrefixLength": 64}]}'
PATCH -D patch.txt -d '{"IPv6StaticAddresses": [null,{},{"Address": "2002:905:150e:301:72e2:84ff:fe14:444","PrefixLength": 64}]}'
PATCH -D patch.txt -d '{"IPv6StaticAddresses": [{"Address": "2002:905:150e:301:72e2:84ff:fe14:555","PrefixLength": 64},{}]}'
PATCH -D patch.txt -d '{"IPv6StaticAddresses": [{},{"Address": "2002:905:150e:301:72e2:84ff:fe14:666"}]}'
PATCH -D patch.txt -d '{"IPv6StaticAddresses": [{},{"PrefixLength": 64}]}'

Tested with validator and no errors.

Change-Id: I7d1314a0c7843aae8425d66119f0d205a5cfac55
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>

show more ...

[Redfish] Enable PATCH for DHCPv4 properties in EthernetInterface schema

DHCPv4 were read-only properties, this code change make following
properties to be PATCHable:

- DHCPEnabled
- UseDNSServers

[Redfish] Enable PATCH for DHCPv4 properties in EthernetInterface schema

DHCPv4 were read-only properties, this code change make following
properties to be PATCHable:

- DHCPEnabled
- UseDNSServers
- UseDomainName
- UseNTPServers

Tested:
1. Check DHCPv4 properties value

GET /redfish/v1/Managers/bmc/EthernetInterfaces/<ethID> HTTP/1.1
Response:
{
......
"DHCPv4": {
"DHCPEnabled": true,
"UseDNSServers": true,
"UseDomainName": true,
"UseNTPServers": true
},
......
}

2. PATCH DHCPv4

PATCH /redfish/v1/Managers/bmc/EthernetInterfaces/eth1 HTTP/1.1
{
"DHCPv4": {
"DHCPEnabled":false,
"UseDNSServers": false,
"UseDomainName": false,
"UseNTPServers": false
}
}

3. Check whether DHCPv4 properties are set

GET /redfish/v1/Managers/bmc/EthernetInterfaces/<ethID> HTTP/1.1
Response:
{
......
"DHCPv4": {
"DHCPEnabled": false,
"UseDNSServers": false,
"UseDomainName": false,
"UseNTPServers": false
},
......
}

Signed-off-by: Jennifer Lee <jennifer1.lee@intel.com>
Change-Id: I125029ae4cdef329edabd18f6aa6a16db6e27d3d

show more ...

Fix 404 handling in Redfish EthernetInterfaces

Previously, when a user requested a network interface that was
non-sensical, like:
/redfish/v1/Managers/bmc/EthernetInterfaces/foobar/VLANs
OR
/redfish

Fix 404 handling in Redfish EthernetInterfaces

Previously, when a user requested a network interface that was
non-sensical, like:
/redfish/v1/Managers/bmc/EthernetInterfaces/foobar/VLANs
OR
/redfish/v1/Managers/bmc/EthernetInterfaces/foobar

They would be presented with a 200-OK, and a partially filled in object.
While this doesn't matter much for the casual redfish user, who uses the
collection to properly enumerate devices, this causes an issue with
security scanners, which think they've found some vulnerability when
they can throw whatever injection text they want to in the message, and
it shows up in the response.

This patchset corrects this, and causes the urls referenced above to
properly return 404, and the appropriate "ResourceNotFound" error
message.

Tested:
Attempted both URLs shown above. Both return 404.

Ran redfish service validator, observed no errors related to
EthernetInterface, or sub nodes. Attempted good URLs, and observed no
change to the payload.

Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Change-Id: Idb2758858d4dbaf421c0cef28b1d5d02402e0ad8

show more ...

Redfish(Network): Implemented PATCH of Nameservers array

Testing:

"NameServers": [],
"NameServers@Message.ExtendedInfo": [
{
"@odata.type": "/redfish/v1/$metadata#Message.v1_0_0.Message

Redfish(Network): Implemented PATCH of Nameservers array

Testing:

"NameServers": [],
"NameServers@Message.ExtendedInfo": [
{
"@odata.type": "/redfish/v1/$metadata#Message.v1_0_0.Message",
"Message": "The property NameServers is a read only property and cannot be assigned a value.",
"MessageArgs": [
"NameServers"
],
"MessageId": "Base.1.4.0.PropertyNotWritable",
"Resolution": "Remove the property from the request body and resubmit the request if the operation failed.",
"Severity": "Warning"
}
]

Change-Id: I12b8cb0ad9b8ad83371ee1d834f38e7537cc7b61
Signed-off-by: RAJESWARAN THILLAIGOVINDAN <rajeswgo@in.ibm.com>

show more ...

Redfish(Network): Implement IPv6DefaultGateway support

Added GET support for IPv6DefaultGateway.its read only property
On Patch operation display "PropertyNotWritable" message.

Tested by:
GET
PATCH

Redfish(Network): Implement IPv6DefaultGateway support

Added GET support for IPv6DefaultGateway.its read only property
On Patch operation display "PropertyNotWritable" message.

Tested by:
GET
PATCH -D patch.txt -d '{"IPv6DefaultGateway": "fe80::226:88ff:feac:8401"}'

Tested with validator and no errors.

Change-Id: Ib67234496b70ec53508a9be36cd86c1859b5d895
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>

show more ...

Fix empty IPV4 gateway error

If an IPV4 gateway is empty use "0.0.0.0".

The RedfishServiceValidator throws the following error on
a Witherspoon system:
"IPv4Addresses[0].Gateway: String '' does not

Fix empty IPV4 gateway error

If an IPV4 gateway is empty use "0.0.0.0".

The RedfishServiceValidator throws the following error on
a Witherspoon system:
"IPv4Addresses[0].Gateway: String '' does not match pattern
''^(?:[0-9]{1,3}\\.){3}[0-9]{1,3}$''"

Tested: Ran RedfishServiceValidator and no longer observe the
error. IPV4 addresses with gateways are untouched.

Change-Id: I423aeeb0bec46fa5cc0c8cf5a017c16d20314984
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>

show more ...

Redfish(Network): Implemented PATCH of StaticNameServers array

Testing:

PATCH -D patch.txt -d '{"StaticNameServers": ["3.3.3.3"]}'
PATCH -D patch.txt -d '{"StaticNameServers": ["3.3.3.3","6.6.6.6"]

Redfish(Network): Implemented PATCH of StaticNameServers array

Testing:

PATCH -D patch.txt -d '{"StaticNameServers": ["3.3.3.3"]}'
PATCH -D patch.txt -d '{"StaticNameServers": ["3.3.3.3","6.6.6.6"]}'
PATCH -D patch.txt -d '{"StaticNameServers": []}'

Signed-off-by: RAJESWARAN THILLAIGOVINDAN <rajeswgo@in.ibm.com>
Change-Id: I3ffb7f5b704437b31ddfeb6a74eae3e6a582164a

show more ...

Redfish(Network): VLAN PATCH fix

This patch set fixes the issue at the Patch operation on VLAN resource.
Before this for any new value of VLANId , the patch command used to apply
value 1 as the new

Redfish(Network): VLAN PATCH fix

This patch set fixes the issue at the Patch operation on VLAN resource.
Before this for any new value of VLANId , the patch command used to apply
value 1 as the new VLANId

Tested by :

GET https://${bmc}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0/VLANs/eth0_10
PATCH https://${bmc}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0/VLANs/eth0_10 -d '{ "VLANId" : 12, "VLANEnable": true}'
PATCH https://${bmc}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0/VLANs/eth0_10 -d '{ "VLANId" : 20, "VLANEnable": false}'

Signed-off-by: Sunitha Harish <sunithaharish04@gmail.com>
Change-Id: Ia18e58816e6c78c8609e0daa558bc66d6914568e

show more ...

Redfish(Network): Fixes VLAN specific issues

This commit fixes the following issues. Before this fix the VLAN functionality was inconsiststant.
1)Add VLANs property to the EthernetInterface resource

Redfish(Network): Fixes VLAN specific issues

This commit fixes the following issues. Before this fix the VLAN functionality was inconsiststant.
1)Add VLANs property to the EthernetInterface resource
2)Removed VLAN property under EthernetInterface resource
3)Made the property - VLANEnable mandatory for creating vlans (POST command)
4)Fetch the VLANId when GET on the VLAN Interface resource
5)Updated Ethernet schema to EthernetInterface.v1_4_1
6)Changed the propert name "DHCPv4Configuration" to "DHCPv4" as per the schema

Tested by:

GET https://${bmc}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0
GET https://${bmc}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0/VLANs
POST -D headers.txt https://${bmc}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0/VLANs -d '{ "VLANId" : 30, "VLANEnable": true}'
GET https://${bmc}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0/VLANs/eth0_30

Signed-off-by: Sunitha Harish <sunithaharish04@gmail.com>
Change-Id: I2339f6711cdd56fe42fee030701125492911dc26

show more ...

Revert "bmcweb: Fix a bunch of warnings"

This reverts commit 6ea007a2faec52ad62680015d2a3f00371a1e351.

Reason for revert: Reports of bmcweb seg faults.

Change-Id: I408f1bb29c2f8e427a6621cdaac8c31b

Revert "bmcweb: Fix a bunch of warnings"

This reverts commit 6ea007a2faec52ad62680015d2a3f00371a1e351.

Reason for revert: Reports of bmcweb seg faults.

Change-Id: I408f1bb29c2f8e427a6621cdaac8c31b847ebf06

show more ...

bmcweb: Fix a bunch of warnings

bmcweb classically has not taken a strong opinion on warnings. With
this commit, that policy is changing, and bmcweb will invoke the best
warnings we are able to ena

bmcweb: Fix a bunch of warnings

bmcweb classically has not taken a strong opinion on warnings. With
this commit, that policy is changing, and bmcweb will invoke the best
warnings we are able to enable, and turn on -Werror for all builds.

This is intended to reduce the likelihood of hard-to-debug situations
that the compiler coulve caught early on.

Change-Id: I57474410821e82666b3a108cfd0db7d070e8900a
Signed-off-by: Ed Tanous <ed@tanous.net>

show more ...

Redfish(Ethernet): Send the correct JSON response after creating the IPV4 object.

Before this commit after creating the IPv4 address object,JSON response
was having empty string for the newly added

Redfish(Ethernet): Send the correct JSON response after creating the IPV4 object.

Before this commit after creating the IPv4 address object,JSON response
was having empty string for the newly added object.

This commit fixes the problem.

Tested By:
Assuming there are already two IP addresses configured then the following
PATCH request would throw the following output

PATCH -D patch.txt -d '{"IPv4Addresses": [{},{},{"Address": "a.a.a.a","Address
Origin": "Static","SubnetMask": "255.255.0.0","Gateway":"g.g.g.g"}]}

{
"@odata.id": "/redfish/v1/Managers/bmc/EthernetInterfaces/eth0",
"HostName": "witherspoon",
"IPv4Addresses": [
{
"Address": "169.254.201.17",
"AddressOrigin": "IPv4LinkLocal",
"Gateway": "9.3.185.1",
"SubnetMask": "255.255.0.0"
},
{
"Address": "9.3.185.83",
"AddressOrigin": "Static",
"Gateway": "9.3.185.1",
"SubnetMask": "255.255.255.0"
},
{
"Address": "a.a.a.a",
"Gateway": "g.g.g.g",
"SubnetMask": "255.255.0.0"
}
],

Change-Id: I6be340051020839ff7f669296c2077ecfdce78ff
Signed-off-by: Ratan Gupta <ratagupt@linux.vnet.ibm.com>

show more ...

Redfish(Network): Support the PATCH opertration of MACAddress property

TestedBy:
PATCH '{"MACAddress": "x2:xx:xx:xx:xx:xx"}'

Change-Id: I6dc421ea509506a2f3062fc0531778ffa2b00310
Signed-off-by: Rata

Redfish(Network): Support the PATCH opertration of MACAddress property

TestedBy:
PATCH '{"MACAddress": "x2:xx:xx:xx:xx:xx"}'

Change-Id: I6dc421ea509506a2f3062fc0531778ffa2b00310
Signed-off-by: Ratan Gupta <ratagupt@linux.vnet.ibm.com>

show more ...

Redfish(Network): Support for deletion of IP address through PATCH operation

Before this commit we were reading the IPV4address through readJSON
function in vector of json, readJSON doesn't like the

Redfish(Network): Support for deletion of IP address through PATCH operation

Before this commit we were reading the IPV4address through readJSON
function in vector of json, readJSON doesn't like the null list
parameter and throws the error as below

"The value null for the property IPv4Addresses is of a different type
than the property can accept"

This commit fixes that problem and some restructuring the code to make
delete work.

TestedBy:
PATCH {"IPv4Addresses": [{},null,{},{}]}
deletes second object
PATCH {"IPv4Addresses": [null,{}]}
deletes first object

Suppose if the IPv4Address has two addresses then the
Following PATCH request would give the folowing error.

PATCH {"IPv4Addresses": [{},{},null]
{
"IPv4Addresses/0@Message.ExtendedInfo": [
{
"@odata.type": "/redfish/v1/$metadata#Message.v1_0_0.Message",
"Message": "The value [{},{},null] for the property IPv4Addresses/2 is of a
different format than the property can accept.",
"MessageArgs": [
"[{},{},null]",
"IPv4Addresses/2"
],
}

Change-Id: Iaefd59de469cb345e86b19349b27567a4fcec3fa
Signed-off-by: Ratan Gupta <ratagupt@linux.vnet.ibm.com>

show more ...

Redfish: Populate DHCPv4Configuration Information

With this commit the get-request on ethernet interface service
gets the DHCPv4Configuration.The following are the properties
that are add as a part

Redfish: Populate DHCPv4Configuration Information

With this commit the get-request on ethernet interface service
gets the DHCPv4Configuration.The following are the properties
that are add as a part of this commit.

- UseDNSServers
- UseNTPServers
- UseDomainName
- DHCPEnabled

Tested By:(On Qemu)

GET https://<ip>/redfish/v1/Managers/bmc/EthernetInterfaces/eth0

Change-Id: Ia1f6dbe2c4f1f2ed33adc54f7fd99b61a36c1058
Signed-off-by: manojkiraneda <manojkiran.eda@gmail.com>

show more ...

Redfish(Network): Allow empty list item for ipv4 address.

Tested by:

Assuming there are two IP addresses in the IPv4Addresses for the
following PATCH request.

1) PATCH {"IPv4Addresses": [{},{}]} =

Redfish(Network): Allow empty list item for ipv4 address.

Tested by:

Assuming there are two IP addresses in the IPv4Addresses for the
following PATCH request.

1) PATCH {"IPv4Addresses": [{},{}]} =>No change in the existing list.

2) PATCH {"IPv4Addresses": [{},{},{}]}
Following error for the third list item.
"IPv4Addresses/0/Address@Message.ExtendedInfo": [
{
"@odata.type": "/redfish/v1/$metadata#Message.v1_0_0.Message",
"Message": "The property IPv4Addresses/2/Address is a required property
and must be included in the request.",
"MessageArgs": [
"IPv4Addresses/2/Address"
],
"MessageId": "Base.1.4.0.PropertyMissing",
"Resolution": "Ensure that the property is in the request body and has a
valid value and resubmit the request if the operation failed.",
"Severity": "Warning"
}

Change-Id: I24d11ca82cf6843611f72912499878bcbe1aecac
Signed-off-by: Ratan Gupta <ratagupt@linux.vnet.ibm.com>

show more ...

Redfish(Ethernet): Fix to not convert the json index into string

During Property Update for the Ipv4address, Index was getting
converted into string which was causing the bmcweb to crash.

This comm

Redfish(Ethernet): Fix to not convert the json index into string

During Property Update for the Ipv4address, Index was getting
converted into string which was causing the bmcweb to crash.

This commit fixes this problem.

TestedBy:

Assumption: There is already three IP address and updating the
third one.
PATCH -D patch.txt -d '{"IPv4Addresses":
[{},{},{"Address": "x.x.x.x","AddressOrigin": "Static","SubnetMask": "255.255.0.0","Gateway":"x.x.x.x"}]}

Change-Id: Ic055649b75aaa36e16bda5d8dc4e4e9c87dcb315
Signed-off-by: Ratan Gupta <ratagupt@linux.vnet.ibm.com>

show more ...