<div>
Generally, most of the switches can't be used as WAN routers since NAT is not supported on switches. Juniper EX4300 does not support NAT. If you have &nbsp;virtual private LAN L2/L3 service provided by ISP link between locations and NAT is performed on some other device than you can use EX as CE device (or if you are using public IP addresses on all your end devices).<br />
Problem can also be any other protocol that is needed and not supported on EX device.<br />
<a href="https://www.juniper.net/documentation/en_US/junos/topics/reference/general/ex-series-l3-protocols-not-supported.html" rel="ugc">Layer 3 Protocols Not Supported on EX Series Switches</a>
</div>


<div>
There is absolutely no problem configuring the ports as layer-3. Delete family ethernet switching and configure them for family inet, on the other hand, if you wanted to only have ethernet switching, configure port as access and configure an vlan.x as an l3 interface, follow the below link and revert for any help. <br />
<br />
<a href="https://www.juniper.net/documentation/en_US/junos/topics/reference/general/ex-series-l3-protocols-supported.html" rel="ugc">https://www.juniper.net/documentation/en_US/junos/topics/reference/general/ex-series-l3-protocols-supported.html</a><br />
<br />
-R
</div>


<div>
I'd buy a Cisco 1841 off ebay for about £40. &nbsp;Use that until the equipment comes. &nbsp;A simple NAT config is dead easy.
</div>


<div>
1841 model?<br />
Does it have Gb fibre ports for SFP LC mmode?
</div>


<div>
Sorry, no, I didn't take note of the gbic requirement
</div>


<div>
There is no need for SFP on temporary router. You can use SFP on switch just to bring connection with ISP up.<br />
<br />
[ISP router] --- fiber optic --- [Juniper SFP ge-0/1/3] -- vlanX-- [router WAN interface gi0/0 - Juniper ge-0/0/23] --- [router inside interface gi0/1- Juniper ge-0/0/22]<br />
<br />
<u>Explanation (Juniper 24 ports switch; Cisco 2 port router):<br />
</u><br />
configure Juniper switch ports ge-0/1/3 and ge-0/0/23 to belong to the same VLAN<br />
on SFP port ge-0/1/3 connect link with ISP<br />
on RJ45 port ge-0/0/23 connect WAN router's interface (e.g fa0/0)<br />
This will create point-to-point link between PE and CE routers (it will work except in the case that subnet mask is /31)<br />
<br />
Router's inside interface (fa0/1) connect to port ge-0/0/22<br />
Configuration of ports depends on your switch configuration and future plans. But, generally, can be configured as point to point link/VLAN (default route point to router as next hop) or as trunk (subinterfaces for each VLAN on router's side - trunk on Juniper). Point-to point is preferred.
</div>


<div>
I thought the switch cannot do NAT &nbsp;and no IPSEC. &nbsp;Need firewall for that. &nbsp;I don't have it either yet.
</div>


How to use router without SFP and switch to connect to ISP via SFP :)

Topology.jpg

<div>
Thank you! &nbsp;I see you indicated a PE router. &nbsp;In my case the ISP doesn't provide any routers. &nbsp;I indicated I will provide my own router.
</div>


<div>
<div class="content wysiwyg-content">
I have a situation. &nbsp;Moving users to the new office. &nbsp;Cisco gear however 4 to 6 weeks delayed. &nbsp;Looking for a temp solution. &nbsp; <br />
I have a Juniper EX4300 switch. &nbsp; Can I configure it as layer 3 as a router to serve the purpose. &nbsp;Would that be any difference than having a router? &nbsp;It should have GBIC ports for ISP. &nbsp; And enough mbit ports for the users. &nbsp; There should be only 10-15 users initially. <br />
<br />
Any other temp ideas guys? &nbsp;Thanks.
</div>
</div>


I have a situation.  Moving users to the new office.  Cisco gear however 4 to 6 weeks delayed.  Looking for a temp solution.   
I have a Juniper EX4300 switch.   Can I configure it as layer 3 as a router to serve the purpose.  Would that be any difference than having a router?  It should have GBIC ports for ISP.   And enough mbit ports for the users.   There should be only 10-15 users initially. 

Any other temp ideas guys?  Thanks.

Layer 3 switch over the router

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Network Operations includes asset management, help-desk supervision, security and user policies, infrastructure administration and anything else that affects the operation of your network. Discussions will include those of best practices in platforms, configurations, performance, security and accounting.

Network Operations

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.