About this Guide

This preface describes the VPC-SI System Administration Guide, how it is organized and its document conventions.

Cisco Virtualized Packet Core-Single Instance (VPC-SI) consists of a single StarOS instance running in a virtual machine (VM) on a commercial off-the-shelf (COTS) server. This guide describes how to configure and administer the StarOS instance running within a hypervisor-controlled VM.


Note
Control and User Plane Separation (CUPS) represents a significant architectural change in the way StarOS-based products are deployed in the 3G, 4G, and 5G networks. Unless otherwise specified, it should not be assumed that any constructs (including, but not limited to, commands, statistics, attributes, MIB objects, alarms, logs, services) referenced in this document imply functional parity with CUPS products. References to any CUPS products or features are for informational purposes only. Please contact your Cisco Account or Support representative for any questions about parity between this product and any CUPS products.

Note

The documentation set for this product strives to use bias-free language. For purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product.


Note

The current release does not comply fully with Cisco’s Security Development Lifecycle. Cisco has analyzed and identified the security vulnerabilities related to this release and closed the high-impacting vulnerabilities. Vulnerabilities will be disclosed in accordance with Cisco’s Security Vulnerability Policy.

This guide describes how to generally configure and maintain StarOS running on an virtualized platform. It also includes information on monitoring system performance and troubleshooting. Supplemental information related to general StarOS operation and supported network gateway functions can be found in the StarOS documentation.

Conventions Used

The following tables describe the conventions used throughout this documentation.

Notice Type Description

Information Note

Provides information about important features or instructions.

Caution

Alerts you of potential damage to a program, device, or system.

Warning

Alerts you of potential personal injury or fatality. May also alert you of potential electrical hazards.

Typeface Conventions Description

Text represented as a screen display

This typeface represents displays that appear on your terminal screen, for example:

Login:

Text represented as commands

This typeface represents commands that you enter, for example:

show ip access-list

This document always gives the full form of a command in lowercase letters. Commands are not case sensitive.

Text represented as a command variable

This typeface represents a variable that is part of a command, for example:

show card slot_number

slot_number is a variable representing the desired chassis slot number.

Text represented as menu or sub-menu names

This typeface represents menus and sub-menus that you access within a software application, for example:

Click the File menu, then click New

Command Syntax Conventions

Description
{ keyword or variable }

Required keyword options and variables are those components that are required to be entered as part of the command syntax.

Required keyword options and variables are surrounded by grouped braces { }. For example: 

sctp-max-data-chunks { limit max_chunks | mtu-limit }

If a keyword or variable is not enclosed in braces or brackets, it is mandatory. For example:

snmp trap link-status
[ keyword or variable ]

Optional keywords or variables, or those that a user may or may not choose to use, are surrounded by brackets.

|

Some commands support multiple options. These are documented within braces or brackets by separating each option with a vertical bar.

These options can be used in conjunction with required or optional keywords or variables. For example:

action activate-flow-detection { intitiation | termination }
or
ip address [ count number_of_packets | size number_of_bytes ]

Related Documentation

The most up-to-date information for this product is available in the product Release Notes provided with each software release.

The following user documents are available on www.cisco.com:

  • AAA Interface Administration and Reference
  • Command Line Interface Reference
  • GTPP Interface Administration and Reference
  • IPSec Reference
  • Release Change Reference
  • SNMP MIB Reference
  • Statistics and Counters Reference
  • Thresholding Configuration Guide
  • Product-specific and feature-specific Administration guides

Contacting Customer Support

Use the information in this section to contact customer support.

Refer to the support area of http://www.cisco.com for up-to-date product documentation or to submit a service request. A valid username and password are required to access this site. Please contact your Cisco sales or service representative for additional information.