Difference between revisions of "Cabling and Configuring Opengear CM4148"
From NesevoWiki
Jump to navigationJump to search(5 intermediate revisions by the same user not shown) | |||
Line 42: | Line 42: | ||
*** Take a common straight ethernet patch cable to connect the console server's (CM4148) serial port to the Cisco specific Opengear adaptor cable. | *** Take a common straight ethernet patch cable to connect the console server's (CM4148) serial port to the Cisco specific Opengear adaptor cable. | ||
* For Opengear equipment with a RJ45 console port | * For Opengear equipment with a RJ45 console port | ||
− | ** | + | ** Use an RJ45 - RJ45 rollover cable, these are usually easily identified as light blue and flat – however are not included with your Opengear device |
+ | ** connect a Cisco to Opengear Adapter Cable between the light blue rollover cable and the console port of the Opengear device you want connect to. | ||
+ | ** you should see a console output. | ||
== Connecting ALIX Mini PC Local Consoles == | == Connecting ALIX Mini PC Local Consoles == |
Latest revision as of 09:39, 4 December 2018
Connecting Cisco Network Equipment
Configuration of Serial Ports
- Common Settings
Baud Rate: 9600
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None
- Console Server Settings
- Activate Console Server Mode
- Activate SSH (or other protocols you want to use)
Cabling
- Plug Opengear's Cisco specific adapter Cable (Opengear PartNo 449016) into the Cisco device's console port (do not plug it into the console server's (CM4148) serial port, that won't work!)
- Use a common, straight ethernet patch cable to connect the console server's serial port to the socket of the adapter cable.
Connecting Opengear Local Consoles
To connect another Opengear device via it's local console.
Configuration of Serial Ports
- Common Settings
Baud Rate: 115200
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None
- Console Server Settings
- Activate Console Server Mode
- Activate SSH (or other protocols you want to use)
Cabling
- For Opengear equipment with a DB9 console port
- Alternative 1
- Plug the DB9-to-RJ45 adaptor (Opengear PartNo 319000, the straight variant, not the cross-over one!) into the devices console port.
- Use one of the typical light blue Cisco (!) console cables to connect the console server's (CM4148) serial port to the DB9-connector.
- Alternative 2
- Plug the DB9-to-RJ45 adaptor (Opengear PartNo 319001, the crossover variant, not the straight one!) into the devices console port.
- Take a common straight ethernet patch cable to connect the console server's (CM4148) serial port to the DB9-connector.
- Alternative 3
- Plug the DB9-to-RJ45 adaptor (PartNo 74-0495-01) into the devices console port.
- Plug the Cisco specific Opengear adaptor cable (Opengear PartNo 449016) into the DB9-to-RJ45 adaptor.
- Take a common straight ethernet patch cable to connect the console server's (CM4148) serial port to the Cisco specific Opengear adaptor cable.
- Alternative 1
- For Opengear equipment with a RJ45 console port
- Use an RJ45 - RJ45 rollover cable, these are usually easily identified as light blue and flat – however are not included with your Opengear device
- connect a Cisco to Opengear Adapter Cable between the light blue rollover cable and the console port of the Opengear device you want connect to.
- you should see a console output.
Connecting ALIX Mini PC Local Consoles
Configuration of Serial Ports
- Common Settings
Baud Rate: 38400
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None
- Console Server Settings
- Activate Console Server Mode
- Activate SSH (or other protocols you want to use)
Cabling
- Plug the DB9-connector (Opengear PartNo 319001, the x-over variant, not the straight one!) into the devices console port.
- Use a common straight ethernet patch cable to connect the console server's (CM4148) serial port to the DB9-connector.
Connecting via SSH
- Connect via SSH to
<IP of console server>
on port3000 + <PortNo>
. If your console server has the IP address of 192.168.3.3 and your device is connected to port 25, then connect via SSH to192.168.3.3:3025
using the user name and password you configured.