Abstract: Systems and methods described herein allow a configurable policy for managing Power over Ethernet (PoE) to be implemented by Power Sourcing Equipments (PSEs) across a network. The policy specifies a set of rules for prioritizing power distribution over Ethernet for the computer network. When Powered Devices (PDs) are connected via Ethernet cables to the PSEs, the PDs send identification information about themselves (e.g., device type and location) to the PSEs. The PSEs assign priority levels to the PDs by electronically comparing the identification information to the set of rules. When a present level of available power is insufficient to power all the PDs via PoE, the PSEs use the priority levels to determine which PDs to power down.

Abstract: Examples described herein relate to a system including a BC network associated with a plurality of entities in a defined geographic scope. A first entity of the plurality of entities includes a connected vehicle that generates vehicular data. The BC network is governed by a smart contract. The smart contract includes a data sharing policy defined by a user of the connected vehicle, wherein the data sharing policy allows the user of the connected vehicle to selectively share the vehicular data with one or more other entities of the plurality of entities.

Abstract: Systems and methods are provided for providing supplemental information or data to location-based data provided by conventional asset tags. In particular, sensors such as environmentally-aware sensors, Internet of Things (IoT) sensors, and the like may be incorporated into asset tag devices. In turn, these enhanced asset tags may be integrated into network devices, such as access points, network switches, etc. Accordingly, network devices can be leveraged to provide location-based information, in addition to other information, such as environmental operating conditions relative to the location of such network devices. Moreover, secure communication links can be created between the enhanced asset tags, network devices, and controlling entities in the network, such as network management servers through a mutual authentication mechanism.

Abstract: A network device may send, to a Dynamic Host Configuration Protocol (DHCP) server, a request for an Internet Protocol version 6 (IPv6) address to be assigned to a management port of the network device, wherein IPv6 is disabled at the network device, and may receive a message that includes information associated with a network management system (NMS) and IPv6 configuration information for enabling IPv6 processing on the management port. In response to receiving the IPv6 configuration information, the network device may enable IPv6 processing on the management port of the network device and may register with the NMS based at least in part on the information associated with the NMS. The network device may, in response to receiving one or more configuration commands sent from the NMS to the management port of the network device, configure the network device according to the one or more configuration commands.

Abstract: Example implementations relate to transposed passwords. A computing device may comprise a processing resource; and a memory resource storing machine-readable instructions to cause the processing resource to: receive an entered password; generate, based on the entered password, a transposed version of the entered password; compare the transposed version of the password to a stored password; and grant access based on the comparison.

Abstract: A system may comprise a dock. The dock may comprise a front. The front may include a front side, wherein a plurality of connectors are disposed on the front side and wherein the plurality of connectors accept external cables, and a rear side, wherein the rear side includes a plurality of extenders and wherein each one of the plurality of extenders connects to one of the plurality of connectors. The dock may comprise a rear including an aperture to allow for insertion of a computing device, wherein the plurality of extenders correspond with and connect to one of a connector on the computing device.

Abstract: Aspects of feature-based reporting of software versions are described. A set of features of a software configured on a computing device is ascertained. A first database is queried, based on a current version of the software installed on the computing device and the set of features, to obtain a list of relevant defects addressed for each feature in later versions of the software. A second database is queried, based on the current version of the software and the set of features, to obtain a list of relevant enhancements provided for each feature of the set of features in the later versions. A report is generated based on responses received from the first and second database. The report comprises, for each feature, a summary of the list of relevant defects addressed and the list of relevant enhancements provided in each later version.

Abstract: Examples described relate to disabling of MAC address aging time for an IoT device on a network switch. In an example, in response to a device joining a network, a network switch in the network may determine a media access control (MAC) address of the device. The network switch may then send the MAC address to an authentication server. In response, the network switch may receive a Vendor Specific Attribute (VSA) associated with the MAC address from the authentication server. The VSA indicates that the MAC address relates to an IoT device. Based on the VSA, the network switch may recognize the MAC address of the device as a MAC address of the IoT device. In response to recognizing, the network switch may disable MAC address aging time for the MAC address of the IoT device on the network switch.

Abstract: Examples described herein relate to a system including a BC network associated with a plurality of entities in a defined geographic scope. A first entity of the plurality of entities includes a connected vehicle that generates vehicular data. The BC network is governed by a smart contract. The smart contract includes a data sharing policy defined by a user of the connected vehicle, wherein the data sharing policy allows the user of the connected vehicle to selectively share the vehicular data with one or more other entities of the plurality of entities.

Abstract: A technique includes receiving a request from a first electronic device to connect to a network and receiving a first part from the first electronic device. The technique includes regulating onboarding of the first electronic device. Regulating the onboarding includes authenticating the first electronic device. Authenticating the first electronic device includes communicating with a plurality of electronic devices that are connected to the network to receive a set of second secret parts; constructing a first secret from the first secret part and the set of second secret parts; and comparing the first secret to a second secret. Regulating the onboarding of the first electronic device includes allowing the first electronic device to connect to the network based on a result of the comparison.

Abstract: Systems and methods described herein allow a configurable policy for managing Power over Ethernet (PoE) to be implemented by Power Sourcing Equipments (PSEs) across a network. The policy specifies a set of rules for prioritizing power distribution over Ethernet for the computer network. When Powered Devices (PDs) are connected via Ethernet cables to the PSEs, the PDs send identification information about themselves (e.g., device type and location) to the PSEs. The PSEs assign priority levels to the PDs by electronically comparing the identification information to the set of rules. When a present level of available power is insufficient to power all the PDs via PoE, the PSEs use the priority levels to determine which PDs to power down.

Abstract: Examples include systems and methods for managing a network for example, an enterprise network using a distributed ledger. Some examples include maintaining a distributed ledger by a plurality of NMS units in the network. Use of such distributed ledger may allow communication among NMS units of the plurality of NMS units deployed in the network through the distributed ledger.

Abstract: Systems and methods are disclosed in which Simple Network Management Protocol (SNMP) servers form a blockchain network. Each SNMP server stores and maintains a local copy of a consensus ledger for which a consensus agreement has been obtained among the SNMP servers. The consensus agreement may be based on a validation of one or more fingerprints for one or more blocks of information in the ledger. The fingerprint for each block may be based on information in a preceding block. The consensus ledger includes transaction information for SNMP operations performed between the SNMP servers and managed devices. The common consensus ledger helps ensure that bandwidth, CPU time, and energy for the managed devices and the SNMP servers is not wasted on duplicate SNMP operations.

Abstract: Examples include systems and methods for managing a network for example, an enterprise network using a distributed ledger. Some examples include maintaining a distributed ledger by a plurality of NMS units in the network. Use of such distributed ledger may allow communication among NMS units of the plurality of NMS units deployed in the network through the distributed ledger.

Abstract: A system may comprise a dock. The dock may comprise a front. The front may include a front side, wherein a plurality of connectors are disposed on the front side and wherein the plurality of connectors accept external cables, and a rear side, wherein the rear side includes a plurality of extenders and wherein each one of the plurality of extenders connects to one of the plurality of connectors. The dock may comprise a rear including an aperture to allow for insertion of a computing device, wherein the plurality of extenders correspond with and connect to one of a connector on the computing device.

Abstract: A method for network testing simulation includes generating a simulated network configuration comprising a plurality of simulation nodes based on a topology of an existing network. The method also includes determining a peak traffic for the existing network based on a volume of traffic processed by the existing network, and a plurality of protocols of the traffic. The method further includes generating a simulated traffic based on the peak traffic, the protocols, and the simulated network configuration. Additionally, the method includes processing the simulated traffic using the simulated network configuration to generate a plurality of simulation states of the nodes. Also, the method includes determining whether the software upgrade is tested successfully based on the generated states of the nodes.

Abstract: Systems and methods are provided for providing supplemental information or data to location-based data provided by conventional asset tags. In particular, sensors such as environmentally-aware sensors, Internet of Things (IoT) sensors, and the like may be incorporated into asset tag devices. In turn, these enhanced asset tags may be integrated into network devices, such as access points, network switches, etc. Accordingly, network devices can be leveraged to provide location-based information, in addition to other information, such as environmental operating conditions relative to the location of such network devices. Moreover, secure communication links can be created between the enhanced asset tags, network devices, and controlling entities in the network, such as network management servers through a mutual authentication mechanism.

Abstract: Examples disclosed herein relate to provisioning a network device in a stack. In an example, a master network device in a stack may detect a new network device in the stack. In response to detecting, master network device may determine whether a member network device of the stack is missing. In response to determining that the member network device of the stack is missing, master network device may identify each active adjacent member of the member network device. The master network device may determine whether each active adjacent member of the member network device has detected the new network device in the stack. In response to determining that each active adjacent member of the member network device has detected the new network device in the stack, master network device may provision the new network device with a member ID of the member network device to the stack.

Abstract: Aspects of feature-based reporting of software versions are described. A set of features of a software configured on a computing device is ascertained. A first database is queried, based on a current version of the software installed on the computing device and the set of features, to obtain a list of relevant defects addressed for each feature in later versions of the software. A second database is queried, based on the current version of the software and the set of features, to obtain a list of relevant enhancements provided for each feature of the set of features in the later versions. A report is generated based on responses received from the first and second database. The report comprises, for each feature, a summary of the list of relevant defects addressed and the list of relevant enhancements provided in each later version.

Abstract: A network device may send, to a Dynamic Host Configuration Protocol (DHCP) server, a request for an Internet Protocol version 6 (IPv6) address to be assigned to a management port of the network device, wherein IPv6 is disabled at the network device, and may receive a message that includes information associated with a network management system (NMS) and IPv6 configuration information for enabling IPv6 processing on the management port. In response to receiving the IPv6 configuration information, the network device may enable IPv6 processing on the management port of the network device and may register with the NMS based at least in part on the information associated with the NMS. The network device may, in response to receiving one or more configuration commands sent from the NMS to the management port of the network device, configure the network device according to the one or more configuration commands.