Reset Search
 

 

Article

Getting IP connectivity on a EXOS switch

« Go Back

Information

 
TitleGetting IP connectivity on a EXOS switch
Objective
In order to use things like a syslog, RADIUS client, NTP, or telnet access you must first have IP connectivity to your switch.  There are many ways to get IP connectivity to your switch.  This article will cover 5 easy ways to get IP connectivity to your switch.
Environment
  • EXOS
Procedure
Before we get started lets first talk a little about EXOS.  In EXOS you don't add IP addresses to ports, you only add IP addresses to VLANs.  Ports added to the vlan will have access to the IP of the VLAN.  On EXOS switches you will find a management port, console port, and all your front facing ports.  Your management port is statically linked to the "Mgmt" VLAN, and the  Mgmt virtual router.  All your front facing ports are linked to the "Default" VLAN, and the  Default virtual router.  If you need help understanding VLANS and ports look at this article.  Understanding EXOS VLANs and tagged and untagged ports.  If you need help understanding virtual routers please look at this article. What is a Virtual Router?

In order to get IP connectivity to your switch you simply need an IP address on a VLAN interface, and a route/path to reach the vlan interface.  This article is going to cover 5 different ways of getting IP connectivity on a new switch.

IP connectivity to a Switch on the Default VLAN from the same VLAN
  1. Power up your switch and connect to it via console:
  2. Configure an IP address on the Default VLAN
  3. Connect your PC to the Switch/VLAN, and add a static IP to it.
  4. Ping the switch IP from your PC to make sure it works.  If it doesn't make sure VLAN tagging it correct. 
IP connectivity to a Switch on the Default VLAN from a different VLAN
  1. Power up your switch and connect to it via console:
  2. Configure an IP address on the Default VLAN
  3. Configure a static or default route on the Default VR for the next hop router for this switch.
  4. Ensure that your PC and Switch take the correct routed path to each other. ( Use "traceroute <host_IP>")
IP connectivity to a Switch on the Default VLAN from a different VLAN using OSPF
  1. Power up your switch and connect to it via console:
  2. Configure an IP address on the Default VLAN
  3. Configure OSPF to advertise interface via OSPF
  4. Ensure that your PC and Switch take the correct routed path to each other. ( Use "traceroute <host_IP>")
IP connectivity to a Switch on the Mgmt VLAN from the same VLAN
  1. Power up your switch and connect to it via console:
  2. Configure an IP address on the Mgmt VLAN
  3. Connect your PC to the Mgmt port or Mgmt VLAN, and add a static IP to it.
  4. Ping the switch IP from your PC to make sure it works.  If it doesn't make sure VLAN tagging it correct. 
IP connectivity to a Switch on the Mgmt VLAN from a different VLAN
  1. Power up your switch and connect to it via console:
  2. Configure an IP address on the Mgmt VLAN, and create a static or default route on the Mgmt virtual router.
  3. Ensure that your PC and Switch take the correct routed path to each other. ( Use "traceroute <host_IP>")
Additional notes
Another way is to get IP connectivity to a EXOS switch is to connect the switch to a edge port in our current network with DHCP, and enable DHCP on the vlan your connected it to with the below commands. 
  • enable dhcp vlan <vlan_name>
  • disable dhcp vlan <vlan_name>
Note: Be careful using DHCP on VLANS your going to use for Radius, Syslog, etc.  After a reboot the configuration can be removed because the IP is not static.  See this article for reference.

Related Articles:
Troubleshooting IP Default Gateway issues

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255