Problems with connectivity on VLAN mgmt

[tunfas]

Hello,i have an extreme switch x440-g2.
i try to put an ip in the mgmt vlan, but after doing that, switch does not ping.
After i enabled dhcp, and i have communications by the default vlan.
I need to set an specific ip for Mgmt, and i cant do that. Can someone help me please.

[Henrique]

Hi, since Mgmt vlan belongs to another Virtual Router (VR-Mgmt), you have to specify the vr name when pinging an outside ipaddress throught Mgmt vlan. Otherwise the ICMP request will use VR-Default.

ping vr vr-mgmt

Please see the article below:

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-an-IP-address-on-the-mana...

[Tim_Black]

My problem turned out to be caused by a bad physical ethernet connection. Please disregard.

[Tim_Black]

Henrique, thanks for this - I didn't know this. Is there anything similarly special we need to know about incoming ethernet traffic on the Mgmt port/vlan/vr?

I'm also trying to troubleshoot ICMP and IP(telnet) connectivity from a PC (configured 192.168.1.2/24) to the Mgmt port (configured 192.168.1.100/24) on an EXOS switch. The connection is a direct ethernet connection right now. When I ping using your format above, I get:
* X440G2-12p-10G4.2 # ping vr "VR-Mgmt" 192.168.1.2
Ping(ICMP) 192.168.1.2: 4 packets, 8 data bytes, interval 1 second(s).
--- 192.168.1.2 ping statistics ---
4 packets transmitted, 0 packets received, 100% loss
round-trip min/avg/max = 0/0/0 mstand when I ping from the PC, I get:
C:\>ping 192.168.1.100
Pinging 192.168.1.100 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
I've confirmed the (windows) PC has a route to the EXOS Mgmt ip address:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.16.8.1 172.16.8.60 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
172.16.8.0 255.255.255.0 On-link 172.16.8.60 281
172.16.8.60 255.255.255.255 On-link 172.16.8.60 281
172.16.8.255 255.255.255.255 On-link 172.16.8.60 281 192.168.1.0 255.255.255.0 On-link 192.168.1.2 281 192.168.1.2 255.255.255.255 On-link 192.168.1.2 281 ...I have also checked the route on the Mgmt vlan/vr:
* X440G2-12p-10G4.2 # sho iproute vr "VR-Mgmt"
Ori Destination Gateway Mtr Flags VLAN Duration
#s Default Route 192.168.1.1 1 UG---S-um--f- Mgmt 0d:22h:2m:35s
#d 192.168.1.0/24 192.168.1.100 1 U------um--f- Mgmt 0d:22h:2m:36s

I think this is ok, though for what I'm trying to do (simple access to Mgmt port - no routing required)

Anything else you can think of that I should check? Thanks.

[tunfas]

Hello, sure, no problem at all.
So let see if i got it right. If nothing is connected to mgmt port, i can use the default vlan , there will be no issue?
Thank you very much for the reply

[Drew_C]

I think you've got it right 🙂

The mgmt port is for a truly out-of-band management network. If you don't have a separate network for that, then the default VLAN (or another that you create and tag/route across the network) will work fine.