NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Sourii415e
Aug 07, 2023Aspirant
XS708T and XS708Ev2 Will not Communicate Directly to one another
I have updated both switch's firmware to the latest version : XS708Ev2 - V1.6.0.30 XS708T- V7.0.0.24 Whenever I connect a cable between them (because I would like to extend my 10Gbps Network with ...
Sourii415e
Aug 07, 2023Aspirant
Sounds good, I am not seeing anything in particular, however, I am factory defaulting the unit to make sure nothing is configured that I am missing, plus I have not set defaults since upgrading the firmware. Is there something in specific I should filter to see if I am having an error?
schumaku
Aug 07, 2023Guru - Experienced User
With both switches up on the default config, accessing the XS708T from a locally attached computer, connecting the RJ45 network cable.
Does the Ethernet copper link come up now (LEDs on both ends)?
What showing in the logs on the XS708T after connecting the link?
Or are we facing a config using the SFP+ ports on both ends, with what SFP+ modules (make and model), and what kind of fiber?
- Sourii415eAug 07, 2023Aspirant
I do not know what I was missing, but after the factory default on the XS708T, it now connects to the XS708Ev2.
The cabling was Cat8 on Port 6. I noticed that Port 7 wasn't responding to anything. I swapped the cable to Port 7 and it now also recognizes the other switch.
Thanks for the assistance in troubleshooting this issue.- Sourii415eAug 07, 2023Aspirant
It just failed after about 30 minutes of connectivity and will not connect anymore. I have no idea at this point. Just plugged the unit in on the router again and it connects.
- Sourii415eAug 07, 2023Aspirant
Memory Log Reads as following:
<13> Jan 1 03:35:49 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 148 %% Link Up: xg1 <13> Jan 1 03:35:43 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 146 %% Link Down: xg1 <14> Jan 1 03:35:25 192.168.1.9-1 General[emWeb]: main_login.c(784) 144 %% HTTP Session 7 initiated for connection from 192.168.1.26 <14> Jan 1 03:35:25 192.168.1.9-1 CLI_WEB[emWeb]: emweb_common_custom.c(162) 143 %% HTTP Session 7 started for user admin connected from 192.168.1.26 <14> Jan 1 03:33:31 192.168.1.9-1 CLI_WEB[emWeb]: emweb_common_custom.c(119) 142 %% HTTP Session 7 ended for user admin connected from 192.168.1.26 <13> Jan 1 03:33:30 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 141 %% Link Down: xg7 <13> Jan 1 03:28:34 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 139 %% Link Up: xg7 <13> Jan 1 03:28:26 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 137 %% Link Up: xg5 <13> Jan 1 03:28:25 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 135 %% Link Down: xg7 <13> Jan 1 03:28:15 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 133 %% Link Down: xg5 <13> Jan 1 03:27:49 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 131 %% Link Up: xg1 <13> Jan 1 03:27:41 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 129 %% Link Down: xg1 <13> Jan 1 03:26:01 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 127 %% Link Up: xg7 <13> Jan 1 03:25:56 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 125 %% Link Down: xg6 <13> Jan 1 03:24:10 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 123 %% Link Up: xg6 <13> Jan 1 03:24:01 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 121 %% Link Up: xg5 <13> Jan 1 03:23:58 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 119 %% Link Down: xg6 <13> Jan 1 03:23:58 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 117 %% Link Down: xg5 <13> Jan 1 03:23:33 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 115 %% Link Up: xg6 <13> Jan 1 03:23:33 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 113 %% Link Up: xg1 <13> Jan 1 03:23:16 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 111 %% Link Down: xg1 <13> Jan 1 03:23:01 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 109 %% Link Down: xg6 <14> Jan 1 03:21:54 192.168.1.9-1 General[emWeb]: main_login.c(784) 107 %% HTTP Session 7 initiated for connection from 192.168.1.26 <14> Jan 1 03:21:54 192.168.1.9-1 CLI_WEB[emWeb]: emweb_common_custom.c(162) 106 %% HTTP Session 7 started for user admin connected from 192.168.1.26 <14> Jan 1 03:13:25 192.168.1.9-1 CLI_WEB[emWeb]: emweb_common_custom.c(119) 105 %% HTTP Session 7 ended for user admin connected from 192.168.1.26 <14> Jan 1 03:08:13 192.168.1.9-1 General[emWeb]: main_login.c(784) 104 %% HTTP Session 7 initiated for connection from 192.168.1.26 <13> Jan 1 03:07:32 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 103 %% Link Up: xg6 <14> Jan 1 03:06:22 192.168.1.9-1 General[emWeb]: main_login.c(784) 101 %% HTTP Session 7 initiated for connection from 192.168.1.26 <14> Jan 1 03:06:22 192.168.1.9-1 CLI_WEB[emWeb]: emweb_common_custom.c(162) 100 %% HTTP Session 7 started for user admin connected from 192.168.1.26 <14> Jan 1 00:07:52 192.168.1.9-1 CLI_WEB[emWeb]: emweb_common_custom.c(119) 99 %% HTTP Session 7 ended for user admin connected from 192.168.1.26 <13> Jan 1 00:04:56 192.168.1.9-1 TRAPMGR[lldpTask]: traputil.c(795) 98 %% LLDP-MED Topology Change Detected: ChassisIDSubtype: 4, ChassisID: 28:F1:0E:29:8F:D4, DeviceClass: 1, Interface: xg1 <14> Jan 1 00:02:45 192.168.1.9-1 General[emWeb]: main_login.c(784) 97 %% HTTP Session 7 initiated for connection from 192.168.1.26 <14> Jan 1 00:02:45 192.168.1.9-1 CLI_WEB[emWeb]: emweb_common_custom.c(162) 96 %% HTTP Session 7 started for user admin connected from 192.168.1.26 <14> Jan 1 00:02:36 192.168.1.9-1 CLI_WEB[emWeb]: emweb_common_custom.c(119) 95 %% HTTP Session 7 ended for user admin connected from 192.168.1.26 <14> Jan 1 00:02:26 192.168.1.9-1 General[emWeb]: main_login.c(784) 91 %% HTTP Session 7 initiated for connection from 192.168.1.26 <14> Jan 1 00:02:26 192.168.1.9-1 CLI_WEB[emWeb]: emweb_common_custom.c(162) 90 %% HTTP Session 7 started for user admin connected from 192.168.1.26 <13> Jan 1 00:01:40 192.168.1.9-1 TRAPMGR[SNMPCfgTask]: traputil.c(795) 89 %% Cold Start: Unit: 0 <13> Jan 1 00:01:03 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 88 %% Link Up: xg8 <13> Jan 1 00:01:02 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 86 %% Link Down: xg8 <13> Jan 1 00:01:01 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 84 %% Link Up: xg8 <13> Jan 1 00:01:00 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 82 %% Link Down: xg8 <13> Jan 1 00:00:55 192.168.1.9-1 TRAPMGR[trapTask]: traputil.c(753) 80 %% Link Up: xg8 <13> Jan 1 00:00:53 192.168.1.9-1 SIM[DHCPv4 Client T]: sim_net_port.c(232) 78 %% Network port IPv4 address has been set to 192.168.1.9. <14> Jan 1 00:00:53 192.168.0.239-1 DHCP_CLI[DHCPv4 Client T]: dhcp_prot.c(2426) 77 %% The Network Interface management address is 192.168.1.9 (via DHCP) <13> Jan 1 00:00:51 192.168.0.239-1 TRAPMGR[boxs Req]: traputil.c(795) 76 %% Temperature state change alarm: Unit Number: 1 Current: Normal, Previous: None <13> Jan 1 00:00:51 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 74 %% SFP+ inserted in xg8 <13> Jan 1 00:00:47 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 73 %% Entity Database: Configuration Changed <13> Jan 1 00:00:46 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 72 %% Link Up: xg5 <13> Jan 1 00:00:44 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 70 %% Link Up: xg1 <13> Jan 1 00:00:41 192.168.0.239-1 SIM[emWeb]: sim_util.c(3869) 62 %% Switch firmware operational: XS708T 8-Port 10-Gigabit Copper Smart Managed Pro Switch with 2 Copper/SFP+ Combo Ports <12> Jan 1 00:00:41 192.168.0.239-1 CLI_WEB[emWeb]: cli_txtcfg.c(550) 61 %% Configuration validation failed, applying the default configuration. <11> Jan 1 00:00:41 192.168.0.239-1 General[emWeb]: nsdp_util.c(1134) 60 %% Failed to open the file. <14> Jan 1 00:00:41 192.168.0.239-1 CLI_WEB[emWeb]: sysapi.c(2740) 59 %% Configuration file could not be found on any drive! <12> Jan 1 00:00:40 192.168.0.239-1 CLI_WEB[emWeb]: cli_txtcfg.c(550) 37 %% Configuration validation failed, applying the default configuration. <11> Jan 1 00:00:40 192.168.0.239-1 General[emWeb]: nsdp_util.c(1134) 36 %% Failed to open the file. <14> Jan 1 00:00:40 192.168.0.239-1 CLI_WEB[emWeb]: sysapi.c(2740) 35 %% Configuration file could not be found on any drive! <13> Jan 1 00:00:39 192.168.0.239-1 SIM[Cnfgr_Thread ]: sim_net_port.c(232) 34 %% Network port IPv4 address has been set to 192.168.0.239. <14> Jan 1 00:00:39 0.0.0.0-1 General[procLOG]: procmgr.c(808) 21 %% Application Started (traceroute-0, ID = 10, PID = 1579 <13> Jan 1 00:00:39 0.0.0.0-1 General[procLOG]: procmgr.c(2444) 20 %% Administrative Command:app-start traceroute-0 <14> Jan 1 00:00:39 0.0.0.0-1 General[procLOG]: procmgr.c(808) 19 %% Application Started (ping-0, ID = 9, PID = 1572 <13> Jan 1 00:00:39 0.0.0.0-1 General[procLOG]: procmgr.c(2444) 18 %% Administrative Command:app-start ping-0 <14> Jan 1 00:00:39 0.0.0.0-1 General[procLOG]: procmgr.c(808) 16 %% Application Started (vr-agent-0, ID = 8, PID = 1538 <13> Jan 1 00:00:39 0.0.0.0-1 General[procLOG]: procmgr.c(2444) 15 %% Administrative Command:app-start vr-agent-0 <14> Jan 1 00:00:39 0.0.0.0-1 VR_AGENT[Cnfgr_Thread ]: vr_agent_api.c(72) 11 %% initialized the clnt addr:/tmp/fpcvragent.00,family:1 <9> Jan 1 00:00:38 0.0.0.0-1 SIM[Cnfgr_Thread ]: sim_util.c(3906) 9 %% Switch was reset due to operator intervention. <13> Jan 1 00:00:38 0.0.0.0-1 OSAPI[fp_main_task]: osapi_netlink.c(489) 8 %% Unable add the entry to /etc/iproute2/rt_protos. <10> Jan 1 00:00:38 0.0.0.0-1 General[fp_main_task]: bootos.c(188) 7 %% Event(0xaaaaaaaa) <13> Jan 1 00:00:38 0.0.0.0-1 BSP[fp_main_task]: bootos.c(172) 6 %% BSP initialization complete, starting switch firmware. <13> Jan 1 00:00:30 0.0.0.0-1 General[fp_main_task]: sdm_template_mgr.c(488) 4 %% Booting with default SDM template Dual IPv4 and IPv6. <14> Jan 1 00:00:30 0.0.0.0-1 BSP[fp_main_task]: sysbrds.c(124) 3 %% hpcBoardIdCheck: Detected boardType:0x2, unitType:0x84120002, devId:0x8412 <14> Jan 1 00:00:29 0.0.0.0-1 General[procLOG]: procmgr.c(3685) 2 %% Application Terminated (user.start, ID = 7, PID = 1390 <13> Jan 1 00:00:29 0.0.0.0-0 General[fp_main_task]: usmdb_sim.c(3877) 1 %% Reboot 1 (0x1) - JulienRAug 11, 2023Administrator
Hi Sourii415e,
I will get a member of our support team to contact you and log a case.
Best Regards,
Julien R.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!