Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Programming IP via maintenance port

    I'm a Shoretel customer. We're doing some network infrastructure changes this week, and moving all of our Shoretel gear to a different subnet. My vendor is 'too busy' on an install right now and is not responding to my e-mails. Thought I might get some help here.

    I've read the Shoretel documentation/instructions on connecting to the switches via serial cable and hyperterminal, but the instructions are not consistent with what I'm seeing.

    When I establish a hyperterminal session with the box and reboot the switch I see the switch booting VxWorks. The boot completes and the switch shows online in the Director. The hyperterminal session then just sits there, occassionally displaying some diagnostic-type data. If I push ENTER I then get a command line prompt that looks like similar to: ->

    The Shoretel documentation says that there should be a Shoretel login prompt, at which I should push ENTER, and then type 3 to display a menu of configuration options, then chose Menu Options and follow the onscreen prompts to configure the network settings.

    I don't ever see a Shoretel login prompt, and the prompt I do get doesn't allow any sort of network adapter configuration changes to be made.

    I've also attempted to telnet into the box. There I am prompted for a VxWorks login and password that I do not have.

    What am I doing wrong?



    Thanks in advance.

  • #2
    Originally posted by netwizzerd
    I'm a Shoretel customer. We're doing some network infrastructure changes this week, and moving all of our Shoretel gear to a different subnet. My vendor is 'too busy' on an install right now and is not responding to my e-mails. Thought I might get some help here.

    I've read the Shoretel documentation/instructions on connecting to the switches via serial cable and hyperterminal, but the instructions are not consistent with what I'm seeing.

    When I establish a hyperterminal session with the box and reboot the switch I see the switch booting VxWorks. The boot completes and the switch shows online in the Director. The hyperterminal session then just sits there, occassionally displaying some diagnostic-type data. If I push ENTER I then get a command line prompt that looks like similar to: ->

    The Shoretel documentation says that there should be a Shoretel login prompt, at which I should push ENTER, and then type 3 to display a menu of configuration options, then chose Menu Options and follow the onscreen prompts to configure the network settings.

    I don't ever see a Shoretel login prompt, and the prompt I do get doesn't allow any sort of network adapter configuration changes to be made.

    I've also attempted to telnet into the box. There I am prompted for a VxWorks login and password that I do not have.

    What am I doing wrong?



    Thanks in advance.

    Once the -> comes up through the console session, just type "?" and it will bring up the menu.

    You can make changes through telnet but they are driven by command line and not menus. It is more difficult and not recommended to make changes through the telnet option.

    Comment


    • #3
      Thanks for responding, Chris, but typing "?" brings back a 'Syntax Error'

      Typing "help" does result in a list of commands, but not menus. Of all the commands returned by "help" nothing leads to a point at which I can modify NIC settings.

      There are definitely not any menu-driven options....this is totally CLI.

      Here are the first 10 commands returned by "help":
      help
      dbgHelp
      nfsHelp
      netHelp
      spyHelp (print task histogrammer help info)
      timexHelp (print execution timer help info)
      h [n] (Print or set shell history)
      i [task] (Summary of tasks' TCB's)
      ti task (Complete info on TCB on task)
      sp adr,args.... (spawn a task, pri=100, opt=0, stk=20000)

      I don't mind CLI at all, and thus wouldn't mind making changes via telnet if I had the login info....but if it's not recommended then..........

      Can anyone point me in the right direction from here?
      Last edited by netwizzerd; 05-09-2007, 09:25 PM.

      Comment


      • #4
        Originally posted by netwizzerd
        Thanks for responding, Chris, but typing "?" brings back a 'Syntax Error'

        Typing "help" does result in a list of commands, but not menus. Of all the commands returned by "help" nothing leads to a point at which I can modify NIC settings.

        There are definitely not any menu-driven options....this is totally CLI.

        Here are the first 10 commands returned by "help":
        help
        dbgHelp
        nfsHelp
        netHelp
        spyHelp (print task histogrammer help info)
        timexHelp (print execution timer help info)
        h [n] (Print or set shell history)
        i [task] (Summary of tasks' TCB's)
        ti task (Complete info on TCB on task)
        sp adr,args.... (spawn a task, pri=100, opt=0, stk=20000)

        I don't mind CLI at all, and thus wouldn't mind making changes via telnet if I had the login info....but if it's not recommended then..........

        Can anyone point me in the right direction from here?
        You need to call TAC. You should not be getting the console from the serial port... just the menu system (unless you run the command from the menu to dump you to the console)...

        Comment


        • #5
          Ok. I figured this one out.

          Turns out there are boot parameters that can be passed to VxWorks. There is one that disables the Shoretel shell. For some reason that parameter (0x2000 to be exact) was being passed to VxWorks so I was being dumped straight into the VxWorks shell. As soon as I changed 0x2000 to 0x0000 it dumped me into the Shoretel shell and I was able to make all the config changes necessary.

          Funny thing is....I wouldn't know how to get back to the VxWorks shell now, even if I wanted to

          I'm sure with some tinkering it's possible, but that's another project for another day.

          Comment


          • #6
            Originally posted by netwizzerd
            Ok. I figured this one out.

            Turns out there are boot parameters that can be passed to VxWorks. There is one that disables the Shoretel shell. For some reason that parameter (0x2000 to be exact) was being passed to VxWorks so I was being dumped straight into the VxWorks shell. As soon as I changed 0x2000 to 0x0000 it dumped me into the Shoretel shell and I was able to make all the config changes necessary.

            Funny thing is....I wouldn't know how to get back to the VxWorks shell now, even if I wanted to

            I'm sure with some tinkering it's possible, but that's another project for another day.
            Bizzare... You can get back to the CLI (from the console) by typing cliStart (if I recall correctly).

            Comment


            • #7
              cliStart is the correct command to access the VxWorks shell.
              -LC

              Comment

              Working...
              X