China Telcos Are Removing US Network Equipments, Cisco Remotely Disabled RU Equipments
|
|
 Jan 27 2025, 03:42 PM
Return to original view | IPv6 | Post
#1
|
 
Junior Member
706 posts Joined: Jul 2012 
|
QUOTE(a_dot_el @ Jan 24 2025, 03:09 PM) Where is the proof that Cisco has kill switch in it's equipment? It happened to KLIA backed in Aug 2019 https://soyacincau.com/2019/08/23/klia-disr...ed/?form=MG0AV3  |
|
|
|
|
|
Jan 27 2025, 04:21 PM
Return to original view | IPv6 | Post
#2
|
|
Junior Member
706 posts Joined: Jul 2012
|
QUOTE(lurkingaround @ Jan 27 2025, 04:04 PM) . it happened right after KLIA decided to change all Cisco to Huawei. And then suddenly kaboom Your soyacincau news link does not say Cisco used a kill switch to disrupt the KLIA operations. . The management had no choice but to get Cisco to replace all those switches in a short timeframe. |
|
|
Jan 28 2025, 07:10 AM
Return to original view | IPv6 | Post
#3
|
|
Junior Member
706 posts Joined: Jul 2012
|
QUOTE(lurkingaround @ Jan 27 2025, 10:47 PM) . Your report doesn't prove Cisco innocent. What a coincidence, when they decided to switch the vendor, suddenly everything failed Fyi, ....... https://www.linkedin.com/pulse/klia-network...ttle-text-block KLIA Network Glitch - Final Case Study Ts. Dr. Suresh Ramasamy CISSP,CISM,GCTI,GNFA,GCDA,CIPMTs. Dr. Suresh Ramasamy CISSP,CISM,GCTI,GNFA,GCDA,CIPM Ts. Dr. Suresh Ramasamy CISSP,CISM,GCTI,GNFA,GCDA,CIPM CISO | Chief Research Officer | Keynote Speaker | Board Member Published Feb 15, 2023 In 2019, I wrote about the KLIA network glitch that affected the operations of the airport. The failure caused catastrophic failure which halted the airport operations. At that time, no details were available to confirm what actually happened. I used my own experiences to related to the case and hypothesize what happened. Now, official details have emerged and this case study is now final, complete and factual. Read on to find out what actually happened. The incident The incident happened at 2019, but the issue was due to a request that happened in 2017. There is a hotel in the vicinity of the airport called Sama-Sama hotel. In October 2017, personnels of Sama-Sama hotel requested to connect the IPTV network (SSEKLIA2) to their ICT office. Note that the airport network infrastructure falls under the care of MAHB, naturally this request will go to MAHB. The request also carried a potential “Layer 2 multicast/routing issue”. Come 11 July 2019, Sama-sama hotel personnel made another request to extend the VLAN 235 to SSHKILA, SSEKLIA1, SSEKLIA2. On 21 August 2019 8:15pm IT Division reported intermittent connection with TAMS (Total Airport Management System), at the Core Switch. An IT crisis was declared on 22 August 2019 at 3:00am, since the TAMS network was recovered (7 hours after the issue has been identified). TAMS network failure caused a cascading failure, affecting the Flight Information Management System, Flight Information Display System, Baggage Handling System, Gate Allocation System, Flight Data Processing System and the Immigration System. A specialist team from Cisco came in to resolve the issue, enabling IGMP (Internet Group Multicast Protocol) to reduce the multicast. The migration to a new switch was also done. As part of the recovery process, MAHB ordered a N5K and N7k core switches. Incident Assessment .... . . https://www.linkedin.com/pulse/case-study-k...ttle-text-block - Case study - KLIA airport glitch Ts. Dr. Suresh Ramasamy - Published Sep 3, 2019 .... Timeline 20 August 2019 - MAHB signed a MOU with Huawei on technology modernization. 21 August 2019 - KLIA/KLIA 2 reported system/technical issues affecting multiple systems in the airport. Initial news indicates a failure at the network equipment. 22 August 2019 - The Star reported that MAHB had informed that the situation will be resolved by 23 August 2019, as it has received new equipment to replace the existing ones and testing to be conducted on the same night. 23 August 2019 - MAHB updated their website (as at 6am) explaining that they are in the midst of stabilizing their system and had deployed additional buses to ferry the passengers to their respective terminals. ... . Malaysia Airports lodges police report over KLIA systems disruption https://www.malaysiakini.com/news/489747 |
|
|
Jan 28 2025, 02:33 PM
Return to original view | IPv6 | Post
#4
|
|
Junior Member
706 posts Joined: Jul 2012
|
QUOTE(lurkingaround @ Jan 28 2025, 02:24 PM) . Because Cisco has the backup. which can restore in a short period of time.To recover from the KLIA disruption in Aug 2019, MAHB ordered a N5K and N7K core switches from Cisco. Why would MAHB do that if Cisco was guilty.? . Huawei has to replace everything, which will take months. That is why Cisco used the kill switch. |
|
|
Jan 28 2025, 03:15 PM
Return to original view | IPv6 | Post
#5
|
|
Junior Member
706 posts Joined: Jul 2012
|
QUOTE(lurkingaround @ Jan 28 2025, 03:05 PM) . After 3 years, who knows what had happened.So, why was MAHB still buying Cisco network switches in 2022 with a maintenance contract of 12 months.? ...... . |
| Change to: |  0.0219sec
 0.45
 7 queries
 GZIP Disabled
Time is now: 3rd December 2025 - 11:31 PM |
Quote