Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About johnjutte
Community Record
12
Posts
3
Kudos
1
Solution
Badges
Apr 12 2022
12:35 PM
I feel like it's a stack issue, but I need to test or would like to verify that before rebuilding the stack. I just haven't had the time to do it yet. Thanks!
... View more
Apr 12 2022
12:34 PM
I tried to build it in the same fashion. 2 ports on building switches, 2 ports on the stack (1 on each switch in the stack). Aggregate groups were: 1. Building 1 Ports 49/50 2. Building 2 Ports 49/50 3. Building 3 Ports 49/50 4. Stack 1 Port 7/Stack 2 Port 7 5. Stack 1 Port 8/Stack 2 Port 8 6. Stack 1 Port 9/Stack 2 Port 9 Group 1 to Group 4 Group 2 to Group 5 Group 3 to Group 6
... View more
Apr 7 2022
6:59 AM
I have 2 MS425-16s stacked and setup as "core' switches. They handle layer 3 and handoff to a Sophos firewall. I tried to setup redundant uplinks from my MS125 switches to the core using LACP. However, it seems to break my network when Core 2 gets involved. I'm not great at breaking this down, so bare with me a little. Here's a simple version of what I want: Currently the blue uplinks are in place and everything works. The Cores are stacked, but I only have single server on Core 2 right now. There are 3 routed vLANs (interfaces on the MS with a static route) and a couple DHCP relays all working. We have a couple layer 2 vLANs that are working too. Then I setup LACP and aggregated ports on stack (1 on each Core) and 2 ports on each building switch. A few minutes after adding the red uplinks to Core2 things stop working. DHCP relays aren't working as wifi vLAN can't hand out IPs anymore. I can ping wifi vLAN interface, but not known devices on it. When I pull the red uplinks things normalize again. During this time, L2 vLANs seem unaffected. No switches complain about LACP or showed any issues. Trunk ports all match, no ACLs to hinder flow, etc., but it's like Core 2 is unable to route the layer 3 that is setup on the stack. Core1 has our VM hosts and couple other servers hanging off it, so Core 2 load is lower. I feel like the LACP is updating traffic to pass through Core 2 but it's not doing L3. The server on Core 2 does not have issues ping devices on different vLANs right now (I didn't check during my issues). When this was happening, my PC was plugged into Building 2 switch with a LACP to both cores. I was connected to vLAN20 and was able to see devices inside that vLAN, but I couldn't ping vLAN30. However, I code remote into a server connected to vLAN20 and it had no issue pinging vLAN30. I remove Core 2 LACP and then my laptop pings across vLAN30 normally again. I know this should work, but it keeps giving me fits and I feel a bit defeated/nervous to play around.
... View more
Well, so I might be stupid... The link in question is OM1 and about 395ft long. A bit outside the range of 10Gb, so the link connected but signal is weak. I suspected this, and I was trying to some LRM modules with conditioning cables to see if I could be better signal. In a rush, not paying attention, I connect the conditioning cable backwards on 1 side (conditioner into patch instead of module). I flipped the conditioner around and so far so good... yea so, my bad guys. Thanks for input.
... View more
I had more, inconsistent, CRC errors overnight tonight. I changed modules, patch cables, and ports a few times now. I guess my fiber between closets is likely the issue (dirty or damaged).
... View more
I have particular 10Gb link between an MS-125-48LP and MS-125-24P that is reporting brief CRC errors on loose but almost consistent basis. In the last month here's what I'm seeing: 11/2 - Switch installed no issues 11/8 - 2:46p to 2:56p - CRC errors side A - played wait and see. 11/9 - 11:18a to 11:22a - CRC errors side A - cleared before noticed 11/16 - 3:59p to 4:06p - CRC errors side A - I took action. 11/16 - 4:06p to 4:21p - replaced SFP+ modules and fiber cables on both sides 11/17 - 10:03a to 10:07a - CRC errors side A - cleared before I noticed 11/23 - 3:45p to 3:50p - CRC errors side A - vacation. 11/24 - 11:56a to 12:00p - CRC errors side A - vacation. 11/29 - 2:30p to 2:35p - CRC errors side A - saw it this morning 11/30 - 12:05p to 12:10p -CRC errors side A - moved to different fiber pair with new module/cables 11/30 - 3:05p to 3:15p - CRC errors side B While not precise.. there is some consistency with later in the day on Mon/Tues and then late morning the day after. The rest of week the link seems fine or at least not enough issues to alert. I understand CRC errors to mean a physical layer issue hence changing modules, cables, fiber strands, and ports. Are there other things I can check that might cause this? Is environment interference possible (outside RF or something)? Could support maybe dig deeper? Or should I try more hardware/get my fiber between closets checked? Devices on the switch uplinked through this connection never complain - includes VOIP devices and a MR36 with 10-15 devices connected all the time.
... View more
Switches started showing in the dashboard normally sometime after 11p EST (2-3 hours after switches were connected). One switch claims a firmware reboot and both show 'bad gateway warning' for about minute at 11:01p before being solid green again. Support replied to my case at 11:44p to tell me every thing looked normal on their end [>: |] It feels like something stuck on the server side as the switches were working just not updating the cloud or the cloud wasn't showing me the updates. I've never experienced anything like that without some kind of error or warning, and waiting hours for a device to propagate isn't normal. I know it can take 10-15 minutes sometimes, but never waited hours. I don't know and probably will never get anymore from Meraki.
... View more
MS125s connecting to MS425 as core switches. I have management vLAN and all IPs statically set. We have 14 switches in this location and I was trying finish deployment by installing the last 5 today. First 3 went normally, connect them to network, let them boot, reboot, and then plug in everything else. By the time that's done, I check the dashboard and can see the switch is online with the right IP and ports are showing up. No problem. Well, the 2nd to last switch does it's thing shows green on dashboard, but nothing else. No port information, never shows RSTP Root, never updates the IP... but it's working. vLANs are working, clients are getting IPs and connecting fine, etc. I messed with it for a while - rebooting and trying different uplink ports. No change. I move on to the last switch (thinking if I stop watching the pot boil.. ) I get it online, see it's connected - same problem. Local status page shows Healthy, shows the proper IP, shows me port information... but dashboard is still not. I closed Chrome and went back in, no change. I have a case open, but was posting to see if anything else ran into this?
... View more
Labels:
- Labels:
-
Other
I don't have a fix for faxing or an explanation for the sudden problem, but we ruled out networking as an issue. We ran multiple tests with ISP and Wireshark. Confirmed minimal jitter, 0 packet loss, sub 10ms return times, etc. Port settings all line up and no filtered/blocked traffic. Apparently we have ATA that won't communicate like it should. ISP says this happens with other businesses and offered to provide analog lines instead (more consistent). We're going to test online fax service first though. Thanks for the comments on the sanity check.
... View more
Oct 1 2021
4:28 AM
@PhilipDAth I know those things matter, but settings are same as they were on EdgeMax switches when it was working. Ports have auto-negotiated to same speeds for the ATAs and ONT as before. It's not a new setup, just new switches.
... View more
Oct 1 2021
4:26 AM
@DarrenOC I agree with you, but I'm trying to not assume anything at this point. I appreciate the confirmation and I was posted in some way as a sanity check. Thanks.
... View more
Sep 30 2021
1:20 PM
Recently upgraded to Meraki switches where we have a couple Grandstream ATAs serving as gateways to our hosted PBX for faxing. The ports connected to the ATAs are set as 'Access' the 'VLAN' is 1001 and 'Voice VLAN' is blank. vLAN 1001 is our VOIP vLAN that comes from our ISP (they host the PBX). We connect to this directly from their ONT equipment. No firewall or traffic shaping between the ATA and our provider. I do have QoS enabled for the phone vLAN set to 'Trust incoming...' I can send/receive fax from building to building. I can receive faxes from outside orgs and services. I can't send a fax to outside orgs or services. Kyocera error says: No relevant signal was received after transmission of a PPS (Q) signal during phase D of transmission, and the preset number of command transfers was exceeded I don't think the switches are the problem, but they're the only change since this started. ISP says they didn't change anything. I believe the port is setup properly or should it be a Trunk, Native VLAN 1001, Allow VLANs 1001? Or did I screw up the uplink port to the ONT.. should it be a Trunk port? It's currently an Access port vLAN 1001 only. Does it make a difference?
... View more
Labels:
- Labels:
-
Layer 2
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 1360 | Oct 7 2021 4:42 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 1681 | |
| 1 | 1784 |
© 2024 Cisco Systems, Inc.
