nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

F248XT-25E) today. The F2e module is described in more detail in Chapter 1,
“Introduction to NX-OS.” By default IEEE EEE is disabled and can be enabled by
following Example 7-58.
Example 7-58. Enabling IEEE Energy Efficient Ethernet
Click here to view code image
N7K-1-EEE# show int e5/45
Ethernet5/45 is down (Link not connected)
admin state is up, Dedicated Interface
EEE (efficient-ethernet) : Disabled
N7K-1-EEE# config
Enter configuration commands, one per line. End with
CNTL/Z.
N7K-1-EEE(config)# int e5/45
N7K-1-EEE(config-if)# power efficient-ethernet auto
N7K-1-EEE(config-if)# end
N7K-1-EEE# show int e5/45
Ethernet5/45 is up
admin state is up, Dedicated Interface
EEE (efficient-ethernet) : Enabled
N7K-1-EEE#
Note
Enabling IEEE EEE is disruptive as the link is flapped to allow the end points to
negotiate EEE parameters.
Power On Auto-Provisioning
As of NX-OS 6.1(2) on the Nexus 7000 and NX-OS 5.1(3)N2, a feature named Power on
Auto Provisioning has been added to the capabilities of NX-OS. POAP provides the
foundation to automate the provisioning of Nexus switches in a data center through the use of
automation tools and Python scripting. To use POAP, a few infrastructure services are
needed as Dynamic Host Configuration Protocol (DHCP) and Trivial File Transfer Protocol
(TFTP) are used during the process. When a new switch boots up for the first time with no
configuration, a DHCP server supplies the IP address of a TFTP server with a Python
script, which can be configured to tell the switch how to configure itself on the network with
parameters such as IP address, NX-OS version, switchname, and more. Following are the
steps performed during a switch booting up in a POAP environment.
1. Switch powers on and starts the POAP process.