Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Niraj
Community Record
19
Posts
1
Kudos
0
Solutions
Badges
Sep 27 2021
11:58 PM
Hi Team, MX84 reflects error of "Bad IP assignment configuration" through Broadband link configuration as WAN. Please suggest for fixation of issue. Thanks, Niraj
... View more
Sep 17 2019
5:04 AM
Helpdesk engineer putting best effort in hanging issue on supercilious approach for weeks and months with NIL accountability and answerability. Except a Helpdesk support number neither there is any support matrix nor escalation matrix whatever the business impact for Meraki Customers. Meraki Helpdesk support engineer itself all in all for whatever issue logged and what business impact a customer is facing
... View more
Sep 16 2019
4:23 AM
Definitely agree, that more worst with other OEM or vendor but Meraki is also among Top contender.
... View more
Sep 13 2019
11:00 PM
Undoubtedly a genuine reason why Meraki solution is loosing its spine in industry and in near feature its will be more challenging. Through such supercilious approach don't think so manage so long only through sales of solution.
... View more
Sep 13 2019
10:22 PM
Sounds Good Philip at least acknowledged and accepted things are wrong here in Meraki Support. Also, if we take feedback as an genuine concern its will be quite helpful in betterment of services. Somewhere, we form an opinion and came on conclusion for other concern itself became jury. Isn't its good, if things should be taken in right manner and put effort for improvement.
... View more
Sep 13 2019
4:49 AM
Exceptionally in Meraki customer support some engineer is simply degrading the entire support architecture. Even solution is cloud based and completely managed despite Meraki support engineers are hanging issue for weeks and months on negligence and supercilious approach where there is no any monitoring and supervision.
... View more
Sep 13 2019
4:13 AM
1 Kudo
Meraki Customer Support Poor in Industry
... View more
Sep 30 2018
10:08 PM
Meraki MX400 & MX80 register on cloud through same gateway as all traffic routing via MPLS.
... View more
Sep 29 2018
1:39 AM
Thankful, if get a appropriate solution as in 72 hrs no concrete from Meraki TAC and its impacting our entire business. Facing intermittent issue in multiple site where MX84 is installed.
... View more
Sep 29 2018
12:09 AM
List of observation: 1. MPLS Spoke-Hub and Hub- Spoke response is absolutely fine (Eliminating MX84 from Mumbai) 2. From Mumbai Hub (Spoke)- Mumbai DC application is accessible, Tunnel set-up absolutely fine through same MPLS. 3. From Mumbai Hub (Spoke) - Nxtra DC Loss Tunnel set-up through same MPLS. Incident raised since 27 September 2018 11:02 with Meraki TAC despite resolution yet awaited.
... View more
Sep 28 2018
11:49 PM
Sep 28 2018
12:40 AM
There is Spoke-Hub topology where MX84 installed in Spoke & MX400 in Hub. Traffic is routing through Tunnel towards one Hub but its not routing to other. MPLS Link LM and Spoke-Hub traffic routing is absolutely without MX84 through Router. Logs through direct Sify MPLS connection: C:\Users\Administrator>ping 192.170.1.1 Pinging 192.170.1.1 with 32 bytes of data: Reply from 192.170.1.1: bytes=32 time=36ms TTL=251 Reply from 192.170.1.1: bytes=32 time=36ms TTL=251 Reply from 192.170.1.1: bytes=32 time=35ms TTL=251 Ping statistics for 192.170.1.1: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Reply from 192.170.1.1: Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 36ms, Average = 35ms bytes=32 Control-C ^C C:\Users\Administrator>ping 172.16.10.1 Pinging 172.16.10.1 with 32 bytes of data: Reply from 172.16.10.1: bytes=32 time=3ms TTL=252 Reply from 172.16.10.1: bytes=32 time=8ms TTL=252 Reply from 172.16.10.1: bytes=32 time=11ms TTL=252 Reply from 172.16.10.1: bytes=32 time=5ms TTL=252 Ping statistics for 172.16.10.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 11ms, Average = 6ms C:\Users\Administrator>tracert -d 192.170.1.1 Tracing route to 192.170.1.1 over a maximum of 30 hops 1 1 ms 3 ms 2 ms 192.169.120.1 2 4 ms 4 ms 5 ms 172.11.5.21 3 35 ms 36 ms 37 ms 172.11.7.197 4 36 ms 35 ms 36 ms 172.11.7.198 5 35 ms 36 ms 36 ms 192.170.1.1 Trace complete. C:\Users\Administrator>tracert 172.16.10.1 Tracing route to 172.16.10.1 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.169.120.1 2 12 ms 4 ms 6 ms 172-11-5-21.lightspeed.jcvlfl.sbcglobal.net [172.11.5.21] 3 7 ms 6 ms 6 ms 172-11-5-254.lightspeed.jcvlfl.sbcglobal.net [172.11.5.254] 4 4 ms 3 ms 2 ms 172.16.10.1 Trace complete. Logs through MX connection: C:\Users\Administrator>tracert 192.170.1.1 Tracing route to 192.170.1.1 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.246.5.1 2 * * * Request timed out. 3 * * * Request timed out. 4 ^C C:\Users\Administrator>tracert 172.16.10.1 Tracing route to 172.16.10.1 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.246.5.1 2 4 ms 4 ms 3 ms 172.16.10.1 Trace complete. C:\Users\Administrator>ping 192.170.1.1 Pinging 192.170.1.1 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.170.1.1: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\Administrator>tracert 192.170.1.1 Tracing route to 192.170.1.1 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.246.5.1 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. C:\Users\Administrator>ping 172.16.10.1 Pinging 172.16.10.1 with 32 bytes of data: Reply from 172.16.10.1: bytes=32 time=4ms TTL=254 Reply from 172.16.10.1: bytes=32 time=4ms TTL=254 Reply from 172.16.10.1: bytes=32 time=4ms TTL=254 Reply from 172.16.10.1: bytes=32 time=6ms TTL=254 Ping statistics for 172.16.10.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 6ms, Average = 4ms C:\Users\Administrator>tracert 172.16.10.1 Tracing route to 172.16.10.1 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.246.5.1 2 6 ms 7 ms 4 ms 172.16.10.1 Trace complete.
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 1 | 8061 |
© 2024 Cisco Systems, Inc.
