| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The ncsi-netlink tool has changed, requiring the OEM command to be
prepended to the payload.
Signed-off-by: Eddie James <eajames@linux.ibm.com>
Change-Id: I349a992360d35bc0703979adfcc62d96789bff85
|
|
Move to a common file for all platforms that use the common mapping of
ethernet0 and ethernet1.
This was done as an optimization while adding system1 support in.
Tested:
- Confirmed sbp1 and system1 had correct common file
- Confirmed witherspoon had it's specific ibm-ac-server file
Change-Id: Id96ac9f669fa5cf1241958c5d2d958a95065b25e
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
-mac address wasn't persisting after reboot
Tested by:
1. Assign a valid MAC address aa:e2:84:14:28:79 to the system using
curl -k -H "X-Auth-Token:${bmc_token}" -X PATCH -D patch.txt -d '{"MACAddress":"AA:E2:84:14:28:79"}' https://$bmc/redfish/v1/Managers/bmc/EthernetInterfaces/eth0
2. Now GET and verify if the MAC address has changed using
curl -k -H "X-Auth-Token:${bmc_token}" -X GET https://${bmc}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0
3. Now reboot the BMC and verify if the MAC address remains the same
Change-Id: I334f1936f433e3e7e30ca5e669a89112f9879276
Signed-off-by: Isha Sahni <isha.sahni1@ibm.com>
|
|
IBM is building a system under the "p10bmc" bitbake machine that only
has a single ethernet port, eth0, wired up on it. The system is still
utilizing an AST2600, but only wired eth0 out of the system for cost
purposes.
Since the "p10bmc" machine is a shared target there is no way to remove
services that assume eth1 is present during the build process. Instead,
rely on the fact that the device will be present in /sys/class/net/
if in fact the system supports the network device.
Tested:
- Verified that a p10bmc Rainier machine with 2 eth ports still ran this
script for both ports
- Verified that a p10bmc Bonnell machine with only eth0 ran this script
for eth0 but not eth1
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ic5dfe4bc772fb4de5eb28f3035cf9952d4bbcb7a
|
|
IBM has run into some issues recently with certain network
configurations where eth1 is not getting set to 1 gigabit. This can
cause issues in scenarios where a network environment is running on 1
gigabit minimum-speed network switches.
Removing link-local support from eth1 seemed to aggravated this.
link-local is only on eth0 to avoid subnet issues. But without
link-local, the systemd call, systemd-networkd-wait-online, does not
always find an active eth1 so it never runs the command to force eth1 up
to 1 gigabit.
As far as we can tell, there's no appropriate mapping within
systemd-networkd-wait-online for it to know when the NCSI stack is
appropriately up on a network interface (allowing the 1 gigabit speed to
be set). Therefore the solution taken in this commit is to just keep
retrying for a period of time.
Tested:
- Verified new script ran and set eth ports as expected
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6737e208b59830262f51a8e30c78a97fc698e4fd
|
|
A fork of it is maintained but its upstream layer has largely been
unmaintained.
No future products are planned to be based on this layer.
Mihawk is similar to Witherspoon.
Signed-off-by: Myung Bae <myungbae@us.ibm.com>
Change-Id: I82f7d777b78cd126237d51e42f1e11abdf80ae68
|
|
This commit enables the hypervisor n/w configuration service
for the IBM systems and when it is enabled, the service file
gets created that starts after the bios manager service.
Tested By:
Service file is created for IBM machines and the service
is up and running when the image is flashed onto the system
Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com>
Change-Id: Iac6d4a52df2a85fa3c8b60cc42fa6905337769de
|
|
Since P9 systems need only to stop the link failover, and P10 systems
need only to set the gigabit link speed, split the nsci-netlink
service into two and make it per-interface. Use the systemd network
check to make sure the link is up first. Use a helper script to fetch
the ifindex for the network interface
Signed-off-by: Eddie James <eajames@us.ibm.com>
Change-Id: I6558787a2234575b528864bb71705964a63c0498
|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
We want to use packageconfig options instead of build system specific
ones.
Change-Id: I587d33e3dae82c4c9d85f59f4ee34618443f1dcb
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Change-Id: Ic76f6202f9ae43440e5e6a793ca835a45d6ab088
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
- As per the commit merged in phosphor-networkd, the ibm-config
flag is now changed to sync-mac.
(From meta-ibm rev: 7bd9b4a226207205adf0093b7c64bc69f20ad1dc)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ia02e350ffa3ca42e56f3cac4b0dbc14980fab3b7
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit enables the ibm-config flag for phosphor-networkd
service while compiling for IBM machines.
- ibm-config compilation flag would enable the configurable
Inventory-Interface Mapping JSON for setting the corresponding
MAC Address that are obtanined from the Inventory on to the
respective ethernet interface(s) during the first boot.
(From meta-ibm rev: 4b0db6e07d3207e256f01f2f34d144aa93950224)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Fixed minor typo in commit message
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I31d284839969ea55f13165f5957c164b9b1f6ce8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit removes the first-boot-set-mac service as the
similar and a better functionaly is now implemented in
phosphor-networkd service.
- Here are the few disadvantages of the first-boot-set-mac service
1. The first-boot-set-mac is a script is not scalable with the
increase in the number of ethernet interfaces.
2. Why do we need a new service just for setting the MAC Address
when the network service alone can do it , and it makes sense
to tie up this feature with Network as setting MAC address
functionality is implemented and owned by networkd.
3. With first-boot-set MAC, we need to make sure the VPD is populated
before , if for any reason the VPD is not generated the first-boot
service cannot help set the MAC.
(From meta-ibm rev: 8638c6eb8d54507b632088b329c104e859cd8d19)
Signed-off-by: manojkiran.eda@gmail.com <manojeda@in.ibm.com>
Change-Id: I955834b56c28f9a311563dd40607c8f2ba305d40
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit would enable a configuration JSON file, through which
one can map the inventory object paths to the actual ethernet
interfaces which are managed Network Service.
For Example:
- Lets say the Inventory path for a single ethernet Interface machine
would look something like below:
`/xyz/openbmc_project/inventory/system/chassis/motherboard/boxelder/bmc/ethernet`
Then the corresponding configuration JSON would looks something like below:
{
"eth0":"ethernet"
}
Note that the key (eth0) in the JSON is the actual ethernet Interface
managed by the Network Service, and the value (ethernet) is the search
pattern to be found in the Inventory Path String.
- The above JSON would help the phosphor-network service to look for a
match on the Interface Added signal under Inventory Path with an object
path that contains the pattern String ("ethernet"), and there it gets the
MAC address populated under the respective inventory path and set it as
the MAC address of the eth0 Interface.
(From meta-ibm rev: 0e69c800da414c88d24e4fa5fe8d9bf560b87637)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I9e0ab9d8368efae226334086f7b1c5b6fa821770
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
