Viewing And Verifying Contexts; Ethernet Interfaces And Ports - Cisco ASR 5500 Administration Manual

Viewing and Verifying Contexts

Viewing and Verifying Contexts
Step 1 Verify that your contexts were successfully created by entering the following command:
host_name
[local]
The output is a two-column table similar to the example below. This example shows that two contexts were created: one
named source and one named destination.
Context Name
------------
local
source
destination
The left column lists the contexts that are currently configured. The center column lists the corresponding context ID
for each of the configured contexts. The third column lists the current state of the context.
Step 2
Save your configuration as described in the Verifying and Saving Your Configuration chapter.
Step 3 Now that the context has been created, interfaces and specific functionality can be configured within the context. Proceed
to other sections for instructions on configuring specific services and options.

Ethernet Interfaces and Ports

Regardless of the type of application interface, the procedure to create and configure it consists of the following:
Step 1 Create an interface and assign an IP address and subnet mask to it by applying the example configuration in
Interface, on page
Step 2
Assign a physical port for use by the interface and bind the port to the interface by applying the example configuration
in Configuring a Port and Binding It to an Interface, on page
Step 3 Optionally configure a static route for the interface by applying the example configuration in
for an Interface, on page
Step 4 Repeat the above steps for each interface to be configured.
This section provides the minimum instructions for configuring interfaces and ports to allow the system to communicate
on the network. Commands that configure additional interface or port properties are described in the Ethernet Port
Configuration Mode Commands and Ethernet Interface Configuration Mode Commands chapters of the Command Line
Interface Reference.
To ensure that system line card and port-level redundancy mechanisms function properly, the Spanning Tree protocol
must be disabled on devices connected directly to any system port. Failure to turn off the Spanning Tree protocol may
result in failures in the redundancy mechanisms or service outage.
ASR 5500 System Administration Guide, StarOS Release 19
76
show context all
#
ContextID State
--------- -----
1 Active
2 Active
3 Active
77.
77.
77.
System Interfaces and Ports
Creating an
Configuring a Static Route