Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About auhyden
Community Record
10
Posts
4
Kudos
0
Solutions
Badges
Aug 29 2023
4:51 PM
I have a Starlink <WAN_PORT> MX68W <Wireless> Users crash kit that we are working on standing up. This crash kit will be on the Starlink network. Is it possible to have a VPN tunnel established from this crash kit to another org/user network? Is there documentation anywhere on this?
... View more
Labels:
- Labels:
-
Client VPN
-
Other
Aug 23 2023
12:35 AM
A little. It's an emergency kit being deployed to support a Site-to-Site VPN solution. I was thinking the same. Our Primary objective is to get that Starlink working so the MX can register to the Cloud. Then I can worry about the LAN portion. I think you're right though. The issue would be with how the LAN port from the MX65 is configured going to the ASR. I'll check that out and update then!
... View more
Aug 22 2023
7:38 PM
From what I have seen in documentation for installing the MX65, it says to connect it up to a switch. Has anyone connected a MX65 to a router? We have a crash kit with a MX65 and Starlink. Connection flow is: Starlink <WAN_PORT> MX65 <LAN_PORT_3> ASR >> Internal LAN My customer is doing this. We assigned a /30 point-to-point connection, and we are unable to ping the router from the Meraki. We configured this on the router: interface GigabitEthernet0/0/0 ip address 20.176.255.18 255.255.255.252 no ip redirects no ip proxy-arp ip nbar protocol-discovery ip pim sparse-mode ip nat outside ip ospf network point-to-point no shutdown negotiation auto cdp enable ip virtual-reassembly router ospf 100 no passive-interface GigabitEthernet0/0/0 network 20.176.255.16 0.0.0.3 area 0.0.0.168 On the MX65 we created a dummy vlan 801 and assigned the /30 Router_P2P We also read something that said this: On your MX create a new VLAN. Assign it a random subnet your not using. Put three LAN ports on the MX84 into that VLAN in access mode. Plug your MX WAN interface into one of these MX84 LAN ports. Plug your router and Internet circuit into the other two ports. That seemed weird. Does anyone have insight to this?
... View more
Aug 22 2023
4:04 PM
2 Kudos
This is what I see when I am on the MX for that network's Appliance Status page. What I discovered was the new MX64 that I need to add is going to be at another site, so creating the new network is what I need to do, and set it up as a Spoke to the MX85's Hub site. I was running into that Warm spare conflict because by default, the MX will assume trying to create an HA pair hence the reason I got the models are different error. Happy learning under trial by fire! haha. Thank you for your help!! I will post results once I verify the network is up and running.
... View more
Aug 22 2023
3:29 PM
2 Kudos
Ok good to know. I believe that is what they are doing, and would need to confirm.
... View more
Aug 22 2023
3:28 PM
yes i do. On the Appliance Status page for the MX84. "Configure Warm Spare" shows disabled.
... View more
Aug 22 2023
3:21 PM
My Customer is trying to establish AutoVPN in lieu of a recent critical outage. They do not have another MX84 that can be added to the network unfortunately, so they are trying to get the M64 in there. Following your AutoVPN train of thought, how does that work having the MX64 in another network? Does it a assume a site-to-site VPN between Network 1 (MX84) and Network 2 (MX64)?
... View more
Aug 22 2023
3:15 PM
So there would be no way to add multiple MX's of differing models to a single network? Does it try to establish HA pairing by default? IPv6 is not enabled on the MX84 that we have in the network.
... View more
Aug 22 2023
2:04 PM
In the inventory, there are multiple MX (MX84 is the Active, and MR34) in the network. Warm spare is not configured, and shows disabled in the Appliance Status settings. I was curious as to why HA would attempt to establish if it's not enabled.
... View more
Aug 22 2023
1:59 PM
I am looking for some help in troubleshooting a device not being able to be added to a network in the Dashboard. I am trying to add a MX64 to the network with the end state goal of establishing it as a spoke for Auto VPN. Network's current MX84 shows Warm Spare as Disabled on the Appliance Status page. When I try to add the MX64 to the network, I receive the following error: "Primary and Spare MXes must be the same model when using Warm Spare" I understand that MX'es must be the same model when utilizing the HA feature. However, is this a default behavior of the MX to assume the HA role and try to pair with the active MX even if Warm Spare is disabled?
... View more
Labels:
- Labels:
-
Auto VPN
-
Client VPN
-
Other
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 2711 | |
| 2 | 2736 |
© 2024 Cisco Systems, Inc.
