Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

This section makes frequent use of data contained in the Technical Requirements.

All relevant sections of the Technical Requirements Data collection should be completed or known before commencing with the steps in this section.

Table of Contents

Create CUBE User

...

If the client is using TACACS or Radius to control IOS users, ask the client to create an account to that can access the CUBE with level 5 privileges.

...

Test the account by logging to into the CUBE (SSH to CUBE with the created account) and run those ALL the commands shown below.

Note

Make sure

...

each command displays some output after being run.


Code Block
linenumbers
languagetexttrue
Router# show running-config
Router# show startup-config
Router# show platform software mount
Router# show platform software
Router# show platformversion
Router# show dial-peer voice summary
Router# show dial-peer voice
Router# show dial-peer
Router# show call active voice compact
Router# show users
Router# show
Router# show environment

Local User Option

Login to IOS and enter the following commands:

Code Block
languagetext
linenumberstrue
Router        # Conf t
Router(config)# username {Enter User Here} privilege 15 Password  {Type Password}
Router(config)# privilege exec level 15 show platform software mount
Router(config)# privilege exec level 15 show dial-peer platformvoice softwaresummary
Router(config)# privilege exec level 15 show platform
Router(config)# privilege exec level 1version


Test the account by logging to the CUBE (SSH to CUBE with the account created) and run ALL the commands shown below.

Note

Make sure each command displays some output after being run.


Code Block
languagetext
Router# show running-config
Router# show startup-config
Router# show platform software mount
Router# show version
Router# show dial-peer voice summary

CUBE SNMP Configuration

There are two options for SNMP monitoring of the CUBE, SNMP Version 2c and SNMP version 3. SNMP Version 3 is more secure and is the preferred method.

SNMP Version 2 option

To configure SNMP V2c monitoring of the CUBE you will need the following:

ParameterDescription
VSM Collector IP AddressIP address of the VSM Collector at the customers site

Configure the SNMP Community using the following commands:

Code Block
languagetext
Router        # Conf t
Router(config)# privilege exec level 1 show dial-peer voice
Router(config)# privilege exec level 1 show dial-peer
Router(config)# privilege exec level 1 show users 
Router(config)# privilege exec level 1 show
Router(config)# privilege exec level 1 show environment

Test the account by logging to the CUBE (SSH to CUBE with the account created) and run those commands. Make sure there is output when you run these commands.

Code Block
languagetext
linenumberstrue
Router# show running-config
Router# show startup-config
Router# show platform software mount
Router# show platform software
Router# show platform
Router# show dial-peer voice summary
Router# show dial-peer voice
Router# show dial-peer
Router# show call active voice compact
Router# show users
Router# show
Router# show environment

CUBE SNMP Configuration

snmp-server community virsae RO
Router(Config)# snmp-server host {VSM Collector IP Address} version 2c virsae
Router(Config)# snmp-server enable traps
Router(Config)#exit

Use the following commands to verify SNMP V2 Configuration 

Code Block
languagetext
Router # Show snmp community  << This will display configured community string
Router # show snmp host       << This should display the configured SNMP host which should match the configured one

The following example demonstrates a sample configuration of SNMP Version 2 with option to enable all traps

Code Block
languagetext
Router        # Conf t
Router(Config)# snmp-server community virsae RO
Router(Config)# snmp-server host 10.10.10.20 version 2c virsae
Router(Config)# snmp-server enable traps
Router (Config) # Exit

Verification output :

Code Block
languagetext
Router    # Show snmp Community
Community name: virsae
Community Index: virsae
Community SecurityName: virsae
storage-type: nonvolatile        active

Router # Show snmp host
Notification host: 10.10.10.20        udp-port: 162   type: trap  user: virsae       security model: v2c

SNMP Version 3 option

To configure SNMP v3 monitoring of the CUBE you will need the following:

ParameterValueDescription
View NameVirsaeviewUse Virsaeview by default
Group NameVirsaegroupUse Virsagroup by default
User Name
The SNMP Trap username administered in your VSM equipment location
Authentication ProtocolSHA or MD5The SNMP Trap Authentication protocol administered in your VSM equipment location
Authentication Password
The SNMP Trap Authentication password administered in your VSM equipment location
Privacy ProtocolAES 128, AES 196, AES 256, DESThe SNMP Trap privacy protocol administered in your VSM equipment location

Privacy Password


The SNMP Trap privacy password administered in your VSM equipment location
VSM Collector IP Address
The IP address of the VSM Collector

The SNMP Trap configuration in VSM is documented here SNMP Configuration


Configure the SNMP V3 Configure the SNMP Community using the following commands:

Code Block
languagetext
linenumberstrue
Router        #  Conf t
Router(config)# snmp-server community {Enter SNMP Value here} ROview <View Name> iso included
Router(Config)# snmp-server group <Group Name> v3 priv read <View Name>
Router(Config)# snmp-server locationuser <location><User #ThisName> command<Group isName> optionalv3 andauth may<Authentication neededProtocol> only<Authentication ifPassword> youpriv want<Privacy toProtocol> specify the location.<Privacy Password>
Router(Config)# snmp-server contact <contact info> #This command is optional

...

 host <VSM Collector IP Address> version 3 priv <User Name>
Router(Config)# exit

Example (View name=Virsaeview, Groupname = Virsaegroup, Username = Virsaesnmp):

Code Block
languagetext
Router(Config)# snmp-server view Virsaeview iso included
Router(Config)# snmp-server group Virsaegroup v3 priv read Virsaeview
Router(Config)# snmp-server user Virsaesnmp Virsaegroup v3 auth sha P@ssword123 priv aes 256 P@ssword123
Router(Config)# snmp-server host 192.168.5.180 version 3 priv Virsaesnmp
Router(Config)# snmp-server enable traps
Router(Config)# Exit

Use the following commands to verify the SNMP V3 Configuration is correct administered:

Code Block
languagetext
Router # Show snmp user  << This will display configured snmp V3 user
Router # show snmp host {Enter VSM Probe IP Address here} 
[traps | informs] [version {1| 2c | 3 [auth | noauth | priv]}] community-string [udp-port port-number] [notification-type]  << This should display the configured SNMP host which should match the configured one

Example Verification output :

Code Block
languagetext
Router    # Show snmp user
User name: Virsaesnmp
Engine ID: 800000090300005056BA6363
storage-type: nonvolatile        active
Authentication Protocol: SHA
Privacy Protocol: None
Group-name: Virsaegroup


Router # Show snmp host
Notification host: 192.168.5.180  udp-port: 162   type: trap user: Virsaesnmp     security model: v3 auth

CDR Configuration

Voice Quality Metrics (VQM) Configuration


Code Block
languagetext
Router    #Conf t
Router (config)# voice service voip
Router (conf-voi-serv)# callmonitor
Router (conf-voi-serv)# media statistics
Router (conf-voi-serv)# exit

Enter media monitoring command for each required dial-peer in order to enable monitoring of the calls on each dial peerThe following example shows a sample configuration of SNMP.

Code Block
languagetext
Router(Config    #Conf t
Router (config)# snmp-server community VirsaeVSM RO
Router(Config)# snmp-server location BHIVE Auckland
Router(Config)# snmp-server contact Virsae Support Team
Router(Config)# snmp-server host 10.10.10.20 version 2c VirsaeVSM
Router(Config)# snmp-server enable traps snmp authentication linkdown linkup coldstart
Router(Config)# snmp-server enable traps cpu threshold
Router(Config)# snmp-server enable traps ipsla
Router(Config)# snmp-server enable traps config-copy
Router(Config)# snmp-server enable traps license
Router(Config)# snmp-server enable traps envmon
Router(Config)# snmp-server enable traps bgpdial-peer voice <tag> voip
Router (config-dialpeer)# media monitoring
Router (config-dialpeer)# end

RADIUS Accounting Configuration

There are two possible options for configuring RADIUS accounting 

1- VSM is the only RADIUS Server to be configured on Cisco CUBE

2- VSM is not the only RADIUS Server , There is an existing  RADIUS Server Set up on Cisco CUBE for AAA Operation 

Single RADIUS Server Option (VSM Only)

Perform the following steps to configure  CUBE as Radius client to send accounting information to VSM

Code Block
languagetext
Router    #Conf t
Router (config)# aaa new-model
Router (config)# radius server VSM
Router (config-radius-server)# address ipv4 <VSM Probe IP Address> auth-port  1812 acct-port 1813
Router (config-radius-server)# key <shared secret - this key to be used in VSM Web Portal>
Router (config-radius-server)# exit
Router (config)# aaa group server radius VSMradiusgroup
Router (config-sg-radius)#server name VSM
Router (config-sg-radius)#ip radius source-interface <Enter Interface Name that will be used to send CDR information to VSM>
Router (config-sg-radius)#exit
Router (config)#aaa accounting connection h323 start-stop group VSMradiusgroup
Router (config)#gw-accounting aaa
Router (config-gw-accounting-aaa)# acct-template callhistory-detail
Router (config-gw-accounting-aaa)# exit
Router (config)# radius-server vsa send accounting
Router (config)# exit

Multiple RADIUS Servers option

If Cisco CUBE has already been configured to use other Radius server for AAA operations make sure that this server is placed in another server group by using the following commands .

Code Block
languagetext
Router    #Conf t
Router (config)# aaa group server radius <groupname>  
Router (config-sg-radius)# server <ip-address > auth-port 1812 acct-port 1813
Router (config-sg-radius)# exit
Router (config)# aaa authentication login default group <groupname> local
Router (config)# aaa authorization exec default group <groupname> none
Router (config)# aaa accounting exec default start-stop group <groupname>
Router (config)# radius-server host <ip-address> auth-port 1812 acct-port 1813 key <shared-secret>
Router (config)# exit


ParameterValue
groupnameName of the server group which contains all the RADIUS Servers being used for AAA operations.
ip-addressThe IP address of the RADIUS Server group being used for AAA operations
<shared-secret>Secret Key used to authenticate with the RADIUS Server

Follow the steps mentioned in  Single RADIUS Server option to send call accounting details to VSM.

CUBE Syslog Configuration

Enter the IP Address of the VSM Probe as the destination for the log files.

Tip

Syslog files have logging based on the client's logging configuration.


Code Block
languagetext
Router(Config)# logging host (Enter VSM ProbCollector IP Address) 
Router(Config)# logging traps (i.e 0 1 2 3 4 5 .. according to your requirement)



Once complete you can move onto the VSM Web Portal Configuration

Web Portal Configuration

Add

...

CUBE

Log in to the VSM web portal using your VSM credentials and password.

...

A form will open which you can populate with the equipment details as per this the table below

Select the Vendor ‘Cisco Systems’ and Product ‘Unified Border Element’.

Warning

NOTICE: 'Unified Border Elements' was highlighted in the line above

Image Modified


If you are adding more than one piece of the same equipment type, check the ‘Add another’ box at the bottom of the form and the bulk of the configuration will be carried over for the next item.

Web Portal – Add CUBE Field Description

FieldSetting

Vendor

Cisco Systems

Product

Unified Boarder Border Element

Equipment Name

Friendly name for this CUBE

Username

Administrative Username

Password

Administrative Password

IP Address / Host Name

IP Address of server (Virtual in duplicated servers)

Site

Free text field, this information will be included in alarm notifications from the VSM Workflow.

Use Cisco APIs

Select if Using Cisco APIs for advanced options


Image Added

Info
Tip

Site ID information in the ‘Site’ field will advise your NOC staff of the site where the Microsoft Server (i.e. the VSM Collector) is physically located.

This is particularly helpful when the customer has multiple sites.

Warning

ADD: In the document, there is some highlighted text saying:

"[SCREEN IMAGE HERE]"

"Figure 91 - Web Portal - CUBE Configure Equipment"

SNMP

Complete the Equipment tab and then click on the ‘SNMP Query’ tab.

Click on the down arrow, and select the SNMP version you wish VSM to use for querying the CUBE:


SNMP V1 or V2

CUBE SNMP V1/V2 Field DescriptionsImage Added

FieldSetting

Version

V1, V2

SNMP Community String

Community String as administered on the CUBE

SNMP V3

CUBE SNMP V3 Field DescriptionImage Added

FieldsSetting

Version

V3

Username

SNMP V3 Username (refer to technical requirements forms)

Authentication Protocol

SHA (Recommended)

Authentication Password

Password (refer to technical requirements)

Privacy Protocol

DES (Recommended)

Privacy Password

Password (refer to technical requirements forms)

Test Access

Once all fields are populated Click on the Test Access button. This will test that VSM can connect to the CUBE using the settings you have entered:

Image Modified


Both SSH and SNMP should return success. If not, troubleshoot the configuration.

...