Community Record
10
Posts
0
Kudos
1
Solution
Badges
Sep 27 2021
10:22 AM
Unfortunely, I didn't get a clear answer to the problem. I got an RMA and the new MX is working fine. Thanks to everyone for your answers.
... View more
Sep 20 2021
1:02 PM
@BlakeRichardsonNo, it is connected to the ISP modem but there's not any configuration blocking the traffic
... View more
Sep 20 2021
9:12 AM
Hello @DarrenOC Yes, I tried with a different cable and doesn't work
... View more
Sep 20 2021
9:06 AM
The LAN stops working. I cannot access the local status page, even with static ip and dns in my pc. Also, I don't get an IP from the DHCP server (MX)
... View more
Sep 20 2021
8:58 AM
No, the MX stop functioning at all and I cannot access the local status page. Thanks for the comment, I have just added that info to the post.
... View more
Sep 20 2021
7:54 AM
Hello everyone. I'm facing this issue: My client has just included an MX67 in his network, but after a couple hours functioning correctly, the LED changes its color to ambar and it stays like that. I have tried the next: 1. Disconnect and reconnect the WAN cable. 2. Change the WAN connection to the LAN1 port (it is configured as WAN2). 3. Restart the MX. 4. Reset the MX with a paper clip. The only thing that works is the number 4, but after two or three hours, happens again. There are two things that I think may be indicators of what is happening: 1. While the MX is functioning, I get this logs very frecuently: "Ethernet port carrier change --- device: port1, carrier: true" "Ethernet port carrier change --- device: port3, carrier: true" 2. Our public IP appears in Brightcloud as phishing, but this is a recent problem and we are working on it. Also, while the LED is ambar, I cannot get an IP from the LAN and the MX is configured as DHCP server. I tried to set a static IP in my pc to get access to the local management but it doesn't work. The page does not load. Is there any solution you know? Thanks in advance.
... View more
Mar 2 2021
8:23 AM
So is not possible to have a single static route in the ISR and make it work for both VLANs?
... View more
Mar 2 2021
8:22 AM
But I have some computers attached to phones, so I guess the link between the MS and ISR should be trunk, isn't it?
... View more
Mar 1 2021
9:09 AM
Hi, We have an MX connected to a MS and then, to an ISR. MX <--> MS <--> ISR The ISR is our Voice Gateway, which is VLAN 30 (IP = 10.10.30.1), and it has a Management interface which stands in VLAN 10 (IP = 10.10.10.1). In order to access our voice vlan from the ClientVPN, I added a static route in the ISR with: ip route 192.168.102.0 255.255.255.0 10.10.30.254 where 192.168.102.0 is our ClientVPN subnet and 10.10.30.254 is the MX IP for VLAN 30. Everything good so far, but if I try to access the ISR's management interface I get this error in the MX log: The only way that I achieved to make it work, is adding a second static route like this: ip route 192.168.102.0 255.255.255.0 10.10.10.254 where 10.10.10.254 is the MX IP. My question is, how can I reach both subnets without adding two static routes?
... View more
Kudos given to
My Accepted Solutions
Subject | Views | Posted |
---|---|---|
7080 | Sep 27 2021 10:22 AM |