Wireless Access

last person joined: 13 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

SOE and me (a tearjerker)

This thread has been viewed 0 times

  • 1.  SOE and me (a tearjerker)

    Posted Dec 09, 2011 02:44 AM

    Hiya,

     

    Based on this: http://community.arubanetworks.com/t5/ArubaOS-and-Controllers/SPOE-in-MC-800-2400/m-p/7036/highlight/true

    I'm trying to get SOE working on a couple of 620s.  But I keep getting kicked out immediately.

     

    pimp:~$ telnet 172.16.0.254 2300
    Trying 172.16.0.254...
    Connected to 172.16.0.254.
    Escape character is '^]'.
    Connection closed by foreign host.
    pimp:~$

     

    Any ideas?



  • 2.  RE: SOE and me (a tearjerker)
    Best Answer

    Posted Dec 09, 2011 07:07 AM

    SoE is a feature that only works on our legacy controllers: 800, 2400 for example.  In the "old days" when we were doing only FE, we were able to use the remaining 4 pins in the cable to carry serial data as FE used only 4 wires.  But With GigE, all 8 pins are used by Ethernet not leaving any for SoE.

     

    Hence, the appearance of Console ports on the newer APs which have GigE ports on them.  This has become the defacto for us now.

     

    Hope that helps to understand the feature availability.



  • 3.  RE: SOE and me (a tearjerker)

    Posted Jan 14, 2014 08:03 AM

    Sir, 

     

    will SOE by doing telnet to the port 2300, will not work on 5.0 code?