<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Console conection using CISCO terminal server in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/console-conection-using-cisco-terminal-server/m-p/142013#M48474</link>
    <description>&lt;P&gt;Generally these terminal servers use RJ45 flip cables as the connection from the terminal server port to the port on the device and not ethernet cables. &amp;nbsp;But many also have custom pin out arrangements as well. &amp;nbsp;You should look up the cable requirements of your model device and confirm what you have is correct.&lt;/P&gt;</description>
    <pubDate>Wed, 08 Feb 2017 23:09:32 GMT</pubDate>
    <dc:creator>pulukas</dc:creator>
    <dc:date>2017-02-08T23:09:32Z</dc:date>
    <item>
      <title>Console conection using CISCO terminal server</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/console-conection-using-cisco-terminal-server/m-p/141584#M48426</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First of all i would like to say that im able to conect with serial cable to the Console Port with my laptop.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The issue only occurs when i try to conect to the Console port via Cisco Terminal controller (TTY)&lt;/P&gt;&lt;P&gt;At the begining i thought was a problem with the values that Palo Alto recomend for this kind of conection (see below)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Bits per sec&amp;nbsp;&amp;nbsp;&amp;nbsp; :&amp;nbsp; 9600&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Data bits&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; :&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 8&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Parity&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; :&amp;nbsp; none&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Stop bits&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; :&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Flow control&amp;nbsp;&amp;nbsp;&amp;nbsp; :&amp;nbsp; none&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But after check and as you can see on below ouput the TTY that i use on the Cisco Device is with Values&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;show line tty 6&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Tty Line Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;0/0/4 6 TTY 9600/9600 - - - - - 0 0 0/0 -&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Line 0/0/4, Location: "", Type: ""&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Length: 24 lines, Width: 80 columns&lt;/EM&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;Baud rate (TX/RX) is 9600/9600, no parity, 1 stopbits, 8 databits&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;EM&gt;Status: Ready&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Capabilities: EXEC Suppressed&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Modem state: Ready&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Modem hardware state: noCTS noDSR DTR noRTS&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Special Chars: Escape Hold Stop Start Disconnect Activation&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;BREAK none - - none &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Timeouts: Idle EXEC Idle Session Modem Answer Session Dispatch&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;never 02:00:00 none not set&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Idle Session Disconnect Warning&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;never &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Login-sequence User Response&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;00:00:30&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Autoselect Initial Wait&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;not set &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Modem type is unknown.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Session limit is not set.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Time since activation: never&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Editing is enabled.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;History is enabled, history size is 20.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DNS resolution in show commands is enabled&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Full user help is disabled&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Allowed input transports are pad telnet rlogin lapb-ta mop udptn v120 ssh.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Allowed output transports are pad telnet rlogin lapb-ta mop v120 ssh.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Preferred transport is telnet.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Shell: enabled&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Shell trace: off&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;No output characters are padded&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;No special data dispatching characters&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2017 15:33:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/console-conection-using-cisco-terminal-server/m-p/141584#M48426</guid>
      <dc:creator>AlvaroArcazBarrero</dc:creator>
      <dc:date>2017-02-07T15:33:00Z</dc:date>
    </item>
    <item>
      <title>Re: Console conection using CISCO terminal server</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/console-conection-using-cisco-terminal-server/m-p/142013#M48474</link>
      <description>&lt;P&gt;Generally these terminal servers use RJ45 flip cables as the connection from the terminal server port to the port on the device and not ethernet cables. &amp;nbsp;But many also have custom pin out arrangements as well. &amp;nbsp;You should look up the cable requirements of your model device and confirm what you have is correct.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2017 23:09:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/console-conection-using-cisco-terminal-server/m-p/142013#M48474</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2017-02-08T23:09:32Z</dc:date>
    </item>
  </channel>
</rss>

