Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About getnyce32
getnyce32
Conversationalist
Member since Nov 27, 2017
Mar 21 2019
Community Record
20
Posts
0
Kudos
0
Solutions
Badges
Feb 25 2019
8:11 AM
Thanks for the input. This group policy is to be used in conjuction with 802.1x, specifically the role being passed by the aruba clearpass server will dictate which group policy the user gets. So if a user has been given a role as employee and user will be giving the group policy of employee and will have access to everything. If the user is being given the policy of guest it will only have access to the internet. My policy is working I was just trying to figure out a way of making it shorter. Just an FYI. In your example you give below i'm finding that if a client joins and gets 172.16.0.10 it WILL NOT be able to access anything else in that same subnet. For instance that client will be able to get out to the internet but it will not be able to ping it's default gateway of 172.16.0.1 or any other client on that network. Thanks again for your help. EDIT: My device is just an AP using Bridge mode for the SSIDs
... View more
Feb 25 2019
7:58 AM
Here is the most efficient way I can think of writing the policy.
... View more
Feb 25 2019
7:43 AM
I have a need to have L3 firewall settings at the group policy level. I'm curious if i'm able to use the "Local Lan" as a destination in Group Policy the same way it is using in the "Firewall" section of an SSID. And if so will it implicitly allow DNS and DHCP through?
... View more
Aug 29 2018
5:56 AM
Doesn't seem to exist. I'm just going to modify the existing MS220 stencil. Though the SFP ports are not the same
... View more
Aug 29 2018
5:52 AM
Anyone know where I can get a visio stencil of the MS120. The link to the most up to date stencil doesn't include that model.
... View more
Jul 18 2018
5:55 AM
thanks guys. I tried cutting this over last night and I just wasn't thinking clearly. I will give this a shot in my next change window.
... View more
Jul 18 2018
5:48 AM
I think I may have figured it out. My uplink port to my upstream device should be set to Native VLAN of 1. My management VLAN which is configured on switch>switch settings, should be set to VLAN 30 Now in the dashboard where you set the LAN IP address of the switch. I can either put vlan30 or leave it blank. If I leave it blank it will use VLAN 30 because I configured the management vlan of 30 is switch settings. Is that correct?
... View more
Jul 18 2018
5:10 AM
At one of my remote offices I have a 3900 Cisco router connecting to a 2960 Cisco switch. I bought a Meraki MS-120 to replace the 2960. To get the Meraki online I just plug in an access port on the Meraki to an access port on the Cisco switch. That gave the Meraki an IP address in the Data VLAN and it was able to get out. The other time it came time for me to remove the uplink between the 2960 and the 3900 and move it to the Meraki. So on the Meraki I disconnected it from the Cisco switch so it wasn't plugged into anything. I had port 51 configured at my trunk port which is trunk ALL vlans and set to a native VLAN of 1. I now move the cable so that the Meraki is not connected to the upstream device (Cisco 3900). The result was that the Meraki wasn't getting a good IP address from my Data VLAN (VLAN30). However if I plugged a computer into the access port of the Meraki I was able to route out the network and back to our headend (MPLS). What exactly am I doing wrong here. The native VLAN set on the router is VLAN1. But we have three vlans. Data VLAN30, Voice VLAN4 and Wireless VLAN 16. I want the Meraki to get an IP address on VLAN 30 but it just wasn't working. Sometimes it wouldn't get an IP address at all. Sometimes it would get an IP address on VLAN 16. How do I set the native VLAN of 1 but get the Meraki to pull an IP address from VLAN 30
... View more
May 16 2018
5:10 AM
Sounds like we have the same setup. My MPLS network is small, only about 6 sites. The MPLS is provided by Verizon however I do have access to the router Verizon puts on site. That router is also the default gateway for my voice and data vlan. So if you can imagine, my topology is MPLS Router -> Meraki Switch -> User device. Would my MX sit in between the MPLS Router and the Meraki Switch. If so I would need to change the default gateway of the user it points to the MX device.
... View more
May 15 2018
6:57 AM
I'm trying to wrap my head around routing with SD-WAN implemented. I'm going to request a free trial but before I do so I want to make sure that I have a design so I can hit the road running. I currently have a branch office that has it's own internet connection and it has a corporate MPLS connection. The site has less than 10 users so I would be putting an MX64 there. The internet will plug into one port and the MPLS handoff from the router will plug into the other. No issues there. Lets move to HQ/Data Center where the bigger concentrator will live. I'm thinking the MX100 which will terminate all the VPN connections from the branch offices. So I get this my MX100 will need to have a public IP address to be able to terminate the VPN tunnels over the internet but my questions revolve around routing on the MPLS. Right now my HQ is learning the routes for all my branch offices via OSPF. Envision this. A users at the branch office is destined for a file server at HQ and the path that is taken is over the MPLS through the MX64. It makes it to HQ via the MPLS and comes out of the MX100. The packet makes it to the file server. The File server responds but routing sends the response to the MPLS router in HQ instead of the MX100. I think of a solution that will fix this asymmetrical routing. Does the MX device in HQ participate in OSPF?
... View more
Dec 7 2017
7:11 AM
So your MPLS router's LAN interface is on the same segment as your users. You have a route in the meraki that says if you are voice traffic go to this ip address which is the LAN of the MPLS router. You must be leveraging Policy Based routing in this design, correct?. In your design is the Meraki at your remote using VPN over the MPLS?
... View more
Dec 7 2017
6:52 AM
I'm uncertain as to how I would deploy the MX65 at my spoke location to support my dual MPLS. The site accesses the internet over the MPLS back at the DataCenter/Hub which has a MX84. One of the MPLS is a Layer2 WAN. So I will be able to plug it's handoff into port internet2 and it will be able to ping the MX84 at the hub. The second is a Verizon MPLS that has a router with with two interfaces. One on the WAN and the other on the LAN, Data VLAN. I'm no sure where I should poisition the device in relationship to the MX65. Do I plug the LAN internet of the Verizon MPLS router into internet2 and keep it on the same network as my data vlan. Here is a diagram of the current design.
... View more
Dec 1 2017
10:58 AM
Just went into my data center and unpluggd the cable from port/internet 1 on the meraki and plugged it into my laptop. I gave my machine the same IP address as the Meraki and I was able to ping my DG and my DG was able to ping me.
... View more
Dec 1 2017
10:45 AM
Exactly what I did.. It's an access port going to my switch so naturally I didn't put trunk on that screen. I'm going to go back there now, unplug the cable from the Meraki and plug it into my PC to see if I can ping the DG.
... View more
Dec 1 2017
9:35 AM
There is not config.. this is out of the box setup. I took the device out of the box. Connected a cable to the managment port and went to setup.meraki.com which is local to the box. Gave port 1 an IP address and plugged it into my switch. I can't ping that interface from my switch (Default Gateway)
... View more
Dec 1 2017
6:27 AM
I have an MX84 I just took out of the box. I accessed the device through the management interface and assigned a static IP address to Internet 1. I'm green on the lights and up in the switch. From it's Default Gateway (my distribution switch) I can't ping the IP address of the MX84. I can however see it in the cam table and arp table. This is really making me feel dumb.
... View more
Dec 1 2017
6:25 AM
I'm having the same problem. I have an MX84 I just took out of the box. Accessed the device through the management interface and assigned a static IP address to Internet 1. I'm green on the lights and up in the switch. From it's Default Gateway I can't ping the IP address of the MX84. I can however see it in the arp table.
... View more
Nov 28 2017
5:34 AM
Disclaimer, i'm new to the organization. The WAN is an Verizon managed MPLS with the routers running BGP managed by Verizon. Prior to me joining the organization another WAN solution was purchased (never designed) to sit along side the Verizon MPLS and be used for redundancy. This secondary network isn't yet built because hardware requirements were never defined and as a result there are no routers to terminate the connect. Enter the new network guy (me) and my recommendation of maybe the MX can help me out. I'm looking to take this in a layered approach. First I want to bring one remote site on MX over the Verizon MPLS with the possibility of connecting the second ENS Layer two connection into the MX. In the DC I will put the MX on the same segment as the LAN of the Verizon router and my Core. My core knows how to get to the remote site via the BGP redistribution into OSPF on my core. It sounds like when I put in the MX i will need to enter a router that will instructor the core to send traffic destined to the remote site over to the MX instead of the Verizon router.
... View more
Nov 27 2017
12:33 PM
One other question. Assuming I go with the VPN solution for load balancing over two Private WANs (assuming in this case I have two WAN). If a client in a remote location initiates a connection to a resource in the DC that initial traffic is encrypted and sent over the VPN. however the return traffic would become asymmetric as the packet will be sent directly to the WAN router and never hit the MX for tunneling. Do I make sense?
... View more
Nov 27 2017
11:35 AM
So here is an easy. New to Meraki and I'm have an MX84 and a MX65 to trial out. The MX84 will go in my DC and the MX65 will go to a remote office. The WAN connecting sites is Layer2 ENS provided by Comcast. In the DataCenter the router has two interfaces. One is the WAN and the other is a LAN which is a /29 with an IP address of my core. Do I put the MX84 in that /29 that has the Router LAN and Core on it? It would be in One Armed mode. At the remote site would I just remove the router there and replace it with the MX64. I would need to have two interfaces as well the WAN and the LAN (which would be the DG of the users) Is this topology correct. In case this is not clear I will be leveraging this for SDWAN
... View more
© 2024 Cisco Systems, Inc.
