The following configuration examples describe various methods of configuring Service Probe.
This example creates a probe on the corp VLAN using DHCP, then verifies that clients on that VLAN can reach DNS.
# Create the probe — it will attempt DHCP immediately create service-probe 1 vlan corp # Confirm the probe received an address and the VLAN is up show service-probe 1 detail # Test DNS resolution against all configured servers run service-probe 1 query dns www.extremenetworks.com # Narrow it down to the primary server if a failure is seen run service-probe 1 query dns primary www.extremenetworks.com
This example creates a probe with a fixed IP address and validates both gateway reachability and DNS resolution — useful when you want repeatable results independent of DHCP.
# create a static probe create service-probe 18 vlan corp100 ipaddress 192.168.200.93/24 192.168.200.10 # Add up to three DNS servers configure service-probe 18 add name-server 1.1.1.1 8.8.4.4 208.67.222.222 # Verify the gateway is responding to ARP run service-probe 18 query gateway # Verify DNS resolution run service-probe 18 query dns extreme.com # Review full probe detail, including cached query results show service-probe 18 detail
This example uses shell execution (version 33.6.1 and later) to run a traceroute from inside the probe's network namespace, revealing the actual path traffic takes from the client's perspective.
# Create a static probe on the uplink VLAN create service-probe 1 vlan uplink ipaddress 172.16.1.99/24 172.16.1.1 # Launch a shell command in the probe's context run service-probe 1 shell
At the prompt, enter the command:
traceroute 11.100.100.1
Expected output:
Exit Status: 0 ...output follows: traceroute to 11.100.100.1 (11.100.100.1), 30 hops max, 46 byte packets 1 172.16.1.1 (172.16.1.1) 0.547 ms 0.343 ms 0.321 ms 2 11.100.100.1 (11.100.100.1) 0.287 ms 0.271 ms 0.247 ms