3Com 3812 - SuperStack 3 Switch Getting Started Manual

Also see for 3C17400: Getting started guide Implementation guide Implementation guide Datasheet

Contents

3Com 3812 - SuperStack 3 Switch Getting Started Manual Manual pdf 49 page image

Solving Communication Problems 49Error message indicating that the SFP transceiver is invalidThe Switch has identified that the SFP does not meet the minimumrequirements for the Switch and has disabled the port. To correct thisproblem, completely remove the SFP and replace it with a 3Comapproved SFP. See ““Approved SFP Transceivers” on page 26.Error message indicating that the SFP transceiver is faultyTo correct this problem, completely remove the SFP and then reinsert it.Alternatively, insert another identical SFP. If the problem persists, contact3Com Technical Support.SolvingCommunicationProblemsIf you experience communication problems with the Switch, ensure that:■ The Switch IP address has been configured.■ If the Switch is separated from your management application by arouter, ensure that the default gateway IP address within the Switch isthe same as the IP address of the router.■ The Switch’s IP address has been entered correctly in your networkmanagement application (for example 3Com Network Supervisor).The following is an brief overview of IP addressing, and how to obtain aregistered IP address.IP AddressingTo be managed correctly, each device on your network (for example aSwitch or Hub) must have a unique IP address. IP addresses have theformat n.n.n.n where n is a decimal number between 0 and 255. Anexample IP address is 192.168.100.8.The IP address is split into two parts:■ The first part (‘192.168.100’ in the example) identifies the network onwhich the device resides■ The second part (‘.8’ in the example) identifies the device within thenetworkThe natural subnet mask for this example is 255.255.255.0.If your network has a connection to the external IP network, that is, youaccess the Internet, you must apply for a registered IP address.dua1740-0aaa03.book Page 49 Thursday, December 23, 2004 9:23 PM