AIM-CUE additional CLI details

Getting to know more

Before starting the actual configuration of the AIM-CUE we can get additional details beforehand, and for that we are going to use the following CLI commands:

  • show ip interface brief
vgw#show ip interface brief 
Interface                  IP-Address      OK? Method Status                Protocol
GigabitEthernet0/0   YES NVRAM  up                    up      
Service-Engine0/1          unassigned      YES unset  administratively down down    
GigabitEthernet0/1    YES NVRAM  up                    up      
GigabitEthernet3/0         unassigned      YES unset  administratively down down    

This one is just a double checking to be absolutely sure we’re using the right interface.

  • service-module service-Engine 0/1 ?
vgw#service-module service-Engine 0/1 ?       
  heartbeat-reset  Enable/disable Heartbeat failure to reset Service Module
  password-reset   Password reset of Service Module
  reload           Reload service module
  reset            Hardware reset of Service Module
  session          Service module session
  shutdown         Shutdown service module
  statistics       Service Module Statistics
  status           Service Module Information


This one is the juicy one, the start point to get as much information about CUE as we can.


Now that we know a bunch of arguments we have available, let’s start with “status”:

vgw#service-module service-Engine 0/1 status
Service Module is Cisco Service-Engine0/1
Service Module supports session via TTY line 386
Service Module is in Steady state
Service Module heartbeat-reset is enabled
Getting status from the Service Module, please wait..
Cisco Unity Express 3.1.1
CUE Running on AIM


A few important things to take note here, first a confirmation that our Service Module has CUE running on AIM, and second the CUE version is 3.1.1.

Another not less important detail is that we’ll be able to establish a telnet connection using TTY line 386, that’s another confirmation about the need of an IP Address.


vgw#service-module service-Engine 0/1 session 
IP address needs to be configured on interface Service-Engine0/1

As you can see, we won’t be able to go further without proceeding with the IP addressing task.


vgw#service-module service-Engine 0/1 statistics

Module Reset Statistics:
  CLI reset count = 0
  CLI reload count = 0
  Registration request timeout reset count = 0
  Error recovery timeout reset count = 0
  Module registration count = 311


Ok, I think that was enough, feel free to try a few more if you want.

Where to go from here?

We are making good progress, we can now move on to the following page: