Can we SSH into the SRE-v for troubleshooting?

Version 1
    This document was generated from CDN thread

    Created by: Christopher Daniel on 05-04-2011 12:11:24 PM
    The standard vmWare Hypervisor ESXi lets one SSH into the hypervisor to troubleshoot.
    However I am unable to SSH into the SRE-v. Could you please confirm if this is the case?
     
    Is there any other way i can get into the SRE-v? We are currently troubleshooting dropped packets at the virtual switch (suspected) and need to way to isolate/narrow down the issue.
     
    Thanks!

    Subject: RE: New Message from Christopher Daniel in Service Ready Engine Virtualizat
    Replied by: John Voss on 05-04-2011 03:54:27 PM
    The ESXi Tech Support Shell isn't available in the current release of
    SRE-V.  We are looking at enabling this in a future release.

    Please contact me directly at jovoss@cisco.com for assistance with
    troubleshooting this issue.

    Best Regards,

    John

    ________________________________

    From: Cisco Developer Community Forums
    [mailto:cdicuser@developer.cisco.com]
    Sent: Tuesday, April 05, 2011 9:11 AM
    To: cdicuser@developer.cisco.com
    Subject: New Message from Christopher Daniel in Service Ready Engine
    Virtualization - Technical Questions: Can we SSH into the SRE-v for
    troubleshooting?


    Christopher Daniel has created a new message in the forum "Technical
    Questions":

    --------------------------------------------------------------
    The standard vmWare Hypervisor ESXi lets one SSH into the hypervisor to
    troubleshoot.
    However I am unable to SSH into the SRE-v. Could you please confirm if
    this is the case?

    Is there any other way i can get into the SRE-v? We are currently
    troubleshooting dropped packets at the virtual switch (suspected) and
    need to way to isolate/narrow down the issue.

    Thanks!

    --
    To respond to this post, please click the following link:

    <http://developer.cisco.com/web/srev/forums/-/message_boards/view_messag
    e/3510096>

    or simply reply to this email.