10-27-2022 12:22 PM
Based on the PA-5400 MPC Component Descriptions, the MGT-A and MGT-B management ports are bundled by default as a LAG:
"Two SFP/SFP+ management ports providing 1/10GE connectivity that are used to access the management interface. MGT-A and MGT-B are bundled by default as a LAG (link aggregation group). To leverage both ports, they must be connected to a LAG aware switch." (source)
In comparison, this is all we see on the CLI output, it seems to us that the dedicated logging interfaces are bonded (bond1), but it doesn't show this for management interfaces; we can't find any reference in the documentation to the above operation, does anyone know how the two MGT ports of the PA-5450 actually work, how to configure the two MGT ports on the PA-5450?
Hostname> show interface management
-------------------------------------------------------------------------------
Name: Management Interface
Link status:
Runtime link speed/duplex/state: unknown/unknown/down
Configured link speed/duplex/state: auto/auto/auto
MAC address:
Port MAC address 94:56:xx:xx:xx:ea
Ip address: x.x.x.x
Netmask: 255.255.255.128
Default gateway: x.x.x.x
Ipv6 address: unknown
Ipv6 link local address: unknown
Ipv6 default gateway:
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Logical interface counters:
-------------------------------------------------------------------------------
bytes received 0
bytes transmitted 578
packets received 0
packets transmitted 7
receive errors 0
transmit errors 0
receive packets dropped 0
transmit packets dropped 0
multicast packets received 0
-------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Logging Interface bond1 and slave interfaces eth6 and eth7 stats:
--------------------------------------------------------------------------------
bond1: flags=5123<UP,BROADCAST,MASTER,MULTICAST> mtu 1500
ether 94:56:xx:xx:xx:ec txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth6: flags=6147<UP,BROADCAST,SLAVE,MULTICAST> mtu 1500
ether 94:56:xx:xx:xx:ec txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth7: flags=6147<UP,BROADCAST,SLAVE,MULTICAST> mtu 1500
ether 94:56:xx:xx:xx:ec txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
04-25-2024 07:39 AM
@szabo_sandor - how did this effort end up?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
