![]() ![]() ![]() Large systems (51C/61C/81C) use a DB-9 (E1), or DB-15 (T1) connector, located at the rear of a network shelf. If the circuit doesn't go green, swap the TX/RX pairs: If neither are available, make the termination directly on the MDF block associated with the card slot using the following pinout. The NTBK65 is a replacement to the NTBK04 cable assembly. The following table shows the NTBK65 adaptor signal pin out: Be prepared to swap these, to switch the TX / RX pairs. An RJ-45 connector will fit an RJ-48 jack, but the key on an RJ-48 connector will prevent it from plugging into an RJ-45 jack.Ī standard RJ-45 ethernet cable (568B) works, but note the active pairs are orange and blue, not orange/green. If the circuit doesn't go green, just swap the TX/RX pairs. If you can't find an NTBK65 UDT RJ48C breakout adaptor (right), use pairs 23 (TX) and 24 (RX) on the MDF. Media Gateways (and Option 11's) can use an NTBK04 cable, NTBK65 adapter, or a direct MDF connection. A single direct CAT5/6 cable is always preferred. Ethernet accessories (eg, patch panels) may either not work or cause problems. Note: When using RJ-45's, remember it isn't ethernet! The active pairs in a T1/E1 network are pins 1 & 2 and pins 4 & 5, not 1 & 2 and 3 & 6. * CSU/DSU = Channel Service Unit/Data Service Unit, eg, the PTT modem. The following table shows the pinouts for each: A Yellow "Far End Alarm" (FEA) indicates the local TX pair is open (a yellow alarm is "received").Ī circuit can be presented on a DB-9 (E1), DB-15 (T1), or RJ48/RJ45.A Red "Near End Alarm" (NEA) indicates a local cabling problem, with the RX (or both) pairs open.It can use a number of different connection methods depending upon the service, provider, equipment, and location:Ī TX pair will generally connect to a RX pair, but be prepared to experiment a little (and/or swap/crossover the pairs). The test will repeat indefinitely.A 2 pair connection (TX/RX) between the service providers CSU/DSU (Channel Service Unit/Data Service Unit) and the customers PBX.For ports 40 through 48, type in loopback -e eth0 /dev/port4.For ports 30 through 39, type in loopback -e eth0 /dev/port3.For ports 20 through 29, type in loopback -e eth0 /dev/port2.For ports 10 through 19, type in loopback -e eth0 /dev/port1.The screen will then show 7 columns for ports 10 through 16 and one for Ethernet To test ports 10 through 16 on the CM4116 you need to type loopback -e eth0 /dev/port1.The screen will show 9 columns for serial loopback and one for Ethernet: To invoke the inbuilt loopback diagnostics type in loopback -e eth0 /dev/port0 then press 'return'.Install the ELB on the Ethernet RJ45 socket and an SLB plug onto each serial RJ-45 sockets.You should now see the command line prompt which is a hash (#) Enter username 'root' and password 'default'. The console server will request a username and password. Log on to the console server by pressing 'return' a few times.If you are using "HyperTerminal" or a similar program running on a Windows PC as the terminal device, then the cable is made up from a Cat5 UTP (440016) cable and two DB-9 to RJ-45 adapters (319001) Plug a serial cable between the console server local DB-9 port and terminal device. ![]() Power up the console server and configure the serial connection of the "terminal" device/program you are using to 9600bps, 8 data bits, no parity and one stop bit.custom made RJ-45 Ethernet loopback plug (refer the ELB section at end of this faq).custom made R-45 serial loopback plugs (the SLB section at end of this faq shows the SLB required for a console server with Opengear classic pinout).To undertake these tests you'll need to have at hand: This test enables you to test the console server serial ports and your serial cabling. The Loopback Test also undertakes an Ethernet loopback that senses the data transmitted is received properly. The loopback program senses that data sent is received properly and that signals set and received properly. When undertaking a Loopback Test, each of the serial ports loop data transmitted to data received, RTS to CTS, and DTR to DSR + DCD. For example the Serial Ports panel will then show you the status of each serial port.Īlternately you can get this serail port status information from the command line by typing pmshell –signals –l port1 Hardware loopback testing the portsĮach console server has Loopback Test facilities built in. You can verify that devices are attached correctly to ports by navigating to the web interface and selecting Status: Statistics. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |