{"id":196,"date":"2019-06-25T17:36:04","date_gmt":"2019-06-25T17:36:04","guid":{"rendered":"https:\/\/cue.ciscoar.com\/?page_id=196"},"modified":"2019-08-06T23:11:37","modified_gmt":"2019-08-06T23:11:37","slug":"aim-cue-additional-cli-details","status":"publish","type":"page","link":"https:\/\/cue.ciscoar.com\/?page_id=196","title":{"rendered":"AIM-CUE additional CLI details"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Getting to know more<\/h2>\n\n\n\n<p>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:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>show ip interface brief<\/strong><\/li><\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code lang=\"bash\" class=\"language-bash\">vgw#show ip interface brief \nInterface                  IP-Address      OK? Method Status                Protocol\nGigabitEthernet0\/0         192.168.1.102   YES NVRAM  up                    up      \nService-Engine0\/1          unassigned      YES unset  administratively down down    \nGigabitEthernet0\/1         172.16.1.102    YES NVRAM  up                    up      \nGigabitEthernet3\/0         unassigned      YES unset  administratively down down    \nvgw#<\/code><\/pre>\n\n\n\n<p>This one is just a double checking to be absolutely sure we&#8217;re using the right interface.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong> service-module service-Engine 0\/1 ?  <\/strong><\/li><\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code lang=\"bash\" class=\"language-bash\">vgw#service-module service-Engine 0\/1 ?       \n  heartbeat-reset  Enable\/disable Heartbeat failure to reset Service Module\n  password-reset   Password reset of Service Module\n  reload           Reload service module\n  reset            Hardware reset of Service Module\n  session          Service module session\n  shutdown         Shutdown service module\n  statistics       Service Module Statistics\n  status           Service Module Information\n\nvgw#<\/code><\/pre>\n\n\n\n<p>This one is the juicy one, the start point to get as much information about CUE as we can.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Status<\/h2>\n\n\n\n<p>Now that we know a bunch of arguments we have available, let\u2019s start with \u201cstatus\u201d:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code lang=\"bash\" class=\"language-bash\">vgw#service-module service-Engine 0\/1 status\nService Module is Cisco Service-Engine0\/1\nService Module supports session via TTY line 386\nService Module is in Steady state\nService Module heartbeat-reset is enabled\nGetting status from the Service Module, please wait..\n \nCisco Unity Express 3.1.1\nCUE Running on AIM\n\nvgw#<\/code><\/pre>\n\n\n\n<p>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.<\/p>\n\n\n\n<p>Another not less important detail is that we&#8217;ll be able to establish a telnet connection using TTY line 386, that&#8217;s another confirmation about the need of an IP Address.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Session<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code lang=\"bash\" class=\"language-bash\">vgw#service-module service-Engine 0\/1 session \nIP address needs to be configured on interface Service-Engine0\/1\nvgw#<\/code><\/pre>\n\n\n\n<p>As you can see, we won&#8217;t be able to go further without proceeding with the IP addressing task.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Statistics<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code lang=\"bash\" class=\"language-bash\">vgw#service-module service-Engine 0\/1 statistics\n\nModule Reset Statistics:\n  CLI reset count = 0\n  CLI reload count = 0\n  Registration request timeout reset count = 0\n  Error recovery timeout reset count = 0\n  Module registration count = 311\n\nvgw#\n<\/code><\/pre>\n\n\n\n<p>Ok, I think that was enough, feel free to try a few more if you want.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Where to go from here?<\/h2>\n\n\n\n<p>We are making good progress, we can now move on to the following page:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"\/aim-cue-assigning-ip-address\">AIM-CUE Assigning IP Address<\/a><\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"<p>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 This one is just a double checking to be absolutely sure we&#8217;re using the right interface. service-module service-Engine 0\/1 ? This &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/cue.ciscoar.com\/?page_id=196\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;AIM-CUE additional CLI details&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-196","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/cue.ciscoar.com\/index.php?rest_route=\/wp\/v2\/pages\/196","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cue.ciscoar.com\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/cue.ciscoar.com\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/cue.ciscoar.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cue.ciscoar.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=196"}],"version-history":[{"count":29,"href":"https:\/\/cue.ciscoar.com\/index.php?rest_route=\/wp\/v2\/pages\/196\/revisions"}],"predecessor-version":[{"id":561,"href":"https:\/\/cue.ciscoar.com\/index.php?rest_route=\/wp\/v2\/pages\/196\/revisions\/561"}],"wp:attachment":[{"href":"https:\/\/cue.ciscoar.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=196"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}