Yes. I can help you build a production-ready configuration, but I need to know the exact platform because Cisco has several 64×100G switches, and the configuration differs between IOS-XE, IOS-XR, and NX-OS.
From your description, I suspect you actually have Cisco Nexus switches (for example, 9316D-GX, 9364C, or similar), because:
- Cisco MLAG is called vPC (Virtual Port Channel) on Nexus.
- Traditional IOS switches do not support MLAG in the same way.
- 2020 software would likely be NX-OS 9.x rather than classic IOS.
Could you provide the output of:
show version
show inventory
or at least tell me the model number?
Typical design
+-------------------------+
| DHCP / PXE Server |
| TFTP / HTTP / iPXE |
+-----------+-------------+
|
VLAN 20 (Servers)
|
=====================================
Nexus A ======== Nexus B
Peer-Link (200G or 400G)
Keepalive (mgmt0 or L3)
| |
| |
vPC vPC
Compute Hosts Storage Hosts
vPC (Cisco MLAG)
Normally you'll configure:
- Peer Keepalive
- Peer Link
- vPC Domain
- LACP Port-Channels
- Peer Gateway
- Delay Restore
- Bridge Assurance
- STP Root
Example:
feature lacp
feature vpc
vpc domain 1
peer-keepalive destination 10.1.1.2 source 10.1.1.1 vrf management
peer-switch
peer-gateway
auto-recovery
delay restore 150
Peer link:
interface port-channel1
switchport
switchport mode trunk
spanning-tree port type network
vpc peer-link
PXE Boot
PXE itself doesn't require anything special on the switches.
Usually you need:
- VLAN for clients
- DHCP relay (if DHCP server is elsewhere)
- Jumbo MTU if desired
- Trunk ports to servers
- Access ports to compute nodes
Example:
interface vlan100
ip address 192.168.100.1/24
ip dhcp relay address 192.168.20.5
Cisco supports DHCP relay for vPC environments, and recommends keeping DHCP relay configuration synchronized across both peers.
For UEFI PXE
Typical DHCP options are:
Option 66 = boot server
Option 67 = ipxe.efi
or
Option 67 = grubx64.efi
or
Option 67 = snponly.efi
depending on your PXE environment.
Recommended Features
I'd normally enable:
feature interface-vlan
feature lacp
feature vpc
feature lldp
feature nxapi (optional)
feature scp-server
Best Practices
For a two-switch fabric:
- Dedicated peer-link (2×100G or larger)
- Dedicated keepalive network (management or routed)
- LACP everywhere
peer-gatewaypeer-switch- STP root on the vPC pair
- Use DHCP relay instead of stretching DHCP if the server is on another subnet
- Keep vPC-related configuration identical on both switches.
If these are Cisco Nexus 9300 switches running NX-OS 9.x (circa 2020), I can provide a complete deployment guide with:
- Initial switch setup
- vPC (MLAG) configuration
- Management network
- Peer-link
- Keepalive
- VLANs
- LACP uplinks
- PXE/DHCP relay
- Server port-channels
- Validation commands
- Failure testing
- Zero-downtime upgrade procedure
That configuration typically runs to around 250–350 lines and is suitable as a starting point for production.
