Publication date: Oct., 2012
Revision A2
358
5. Maintenance
5-1. Resolving No Link Condition
The possible causes for a no link LED status are as follows:
The attached device is not powered on
The cable may not be the correct type or is faulty
The installed building premise cable is faulty
The port may be faulty
5-2. Q&A
1.
Computer A can connect to Computer B, but cannot connect to Computer C
through the Managed Switch.
The network device of Computer C may fail to work. Please check the
link/act status of Computer C on the LED indicator. Try another network
device on this connection.
The network configuration of Computer C may be something wrong. Please
verify the network configuration on Computer C.
2. The uplink connection function fails to work.
The connection ports on another must be connection ports. Please check if
connection ports are used on that Managed Switch.
Please check the uplink setup of the Managed Switch to verify the uplink
function is enabled.
3. The console interface cannot appear on the console port connection.
The COM port default parameters are [Baud Rate: 115200, Data Bits: 8,
Parity Bits: None, Stop Bit: A, Flow Control: None]. Please check the COM
port property in the terminal program. And if the parameters are changed,
please set the COM configuration to the new setting.
Check the RS-232 cable is connected well on the console port of the
Managed Switch and COM port of PC.
Check if the COM of the PC is enabled.
4. How to configure the Managed Switch?
The “Hyperterm” is the terminal program in Win95/98/NT. Users can also use
any other terminal programs in Linux/Unix to configure the Managed Switch.
Please refer to the user guide of that terminal program. But the COM port
parameters (baud rate/ data bits/ parity bits/ flow control) must be the same
as
the setting of the console port of the Managed Switch.
Summary of Contents for 065-7851
Page 1: ......
Page 2: ......
Page 62: ...Publication date Oct 2012 Revision A2 60 Fig 3 12 ...
Page 101: ...Publication date Oct 2012 Revision A2 99 Fig 3 34 ...
Page 104: ...Publication date Oct 2012 Revision A2 102 Fig 3 37 Fig 3 38 Fig 3 39 ...
Page 105: ...Publication date Oct 2012 Revision A2 103 Fig 3 40 Fig 3 41 ...
Page 106: ...Publication date Oct 2012 Revision A2 104 Fig 3 42 ...
Page 121: ...Publication date Oct 2012 Revision A2 119 Fig 3 61 Set up VLAN Tag Priority Mapping ...
Page 122: ...Publication date March 2011 Revision A1 120 Fig 3 62 Set up VLAN Tag Priority Mapping Finish ...
Page 136: ...Publication date Oct 2012 Revision A2 134 Fig 3 69 Frame Type Fig 3 70 ...
Page 137: ...Publication date Oct 2012 Revision A2 135 Fig 3 71 Fig 3 72 Fig 3 73 ARP ...
Page 138: ...Publication date Oct 2012 Revision A2 136 Fig 3 74 ARP Fig 3 75 ARP Fig 3 76 ARP Fig 3 77 ARP ...
Page 139: ...Publication date Oct 2012 Revision A2 137 Fig 3 79 ARP Fig 3 80 ARP Fig 3 81 ARP ...
Page 141: ...Publication date Oct 2012 Revision A2 139 Fig 3 87 ARP Fig 3 88 IPv4 ...
Page 145: ...Publication date Oct 2012 Revision A2 143 Fig 3 103 IPv4 Fig 3 104 IPv4 Fig 3 105 IPv4 ...
Page 146: ...Publication date Oct 2012 Revision A2 144 Fig 3 106 IPv4 Fig 3 107 IPv4 Fig 3 108 IPv4 ...
Page 147: ...Publication date Oct 2012 Revision A2 145 Fig 3 109 IPv4 Fig 3 110 IPv4 Fig 3 111 IPv4 ...
Page 148: ...Publication date Oct 2012 Revision A2 146 Fig 3 112 IPv4 Fig 3 113 IPv4 Fig 3 114 IPv4 ...
Page 149: ...Publication date Oct 2012 Revision A2 147 Fig 3 115 IPv4 Fig 3 116 IPv4 Fig 3 117 IPv4 ...
Page 150: ...Publication date Oct 2012 Revision A2 148 Fig 3 118 Action Fig 3 119 Rate Limiter ...
Page 151: ...Publication date Oct 2012 Revision A2 149 Fig 3 120 Port Copy Fig 3 121 DMAC Filter ...
Page 250: ...Publication date Oct 2012 Revision A2 248 Fig 4 1 Fig 4 2 ...