Configuring Secure Domain Routers

Transcription

1 Secure Domain Routers (SDRs) are a means of dividing a single physical system into multiple logically separated routers. SDRs are isolated from each other in terms of their resources, performance, and availability. On NCS-6008 single-chassis, multiple SDRs (multi-sdrs) can be created and each SDR shall be independent of each other. They can be independently upgraded or downgraded and are capable of defining the SDR boundary at the line card level. Table 1: Feature History for Configuring Multiple Secure Domain Routers Release Modification Release SDR feature was introduced. Release Support was added for multi-sdrs. Configuring the XR in multi-sdr environment is same as default-sdr. This module contains the following topics: Prerequisites for Working with Multiple Secure Domain Routers, page 1 Information About, page 3 How to Configure Multiple Secure Domain Routers, page 8 Configuration Examples for Multiple Secure Domain Routers, page 12 Prerequisites for Working with Multiple Secure Domain Routers Before configuring multiple Secure Domain Routers (SDRs), the following conditions must be met: Initial Setup Router should run the Cisco IOS XR software Release

2 Upgrade or Downgrade of Software - Multi-SDR Environment XR management traffic in multi-sdr is tagged, which needs to un-tagged. For more information, see XR Management Traffic in Multi-SDR Environment, on page 5 It is recommended that all the three consoles on RP faceplate must be connected. For more information see Console Access to Named-SDRs, on page 7 Verify the basic system stability before proceeding with named-sdr configuration (before converting from Single Owner Single Tenant (SOST) to Single Owner Multiple Tenant (SOMT)) Install Calvados mandatory SMU (if any) before proceeding with named-sdr configuration Uninstall inactive pkgs/smus from XR and Calvados before converting the system from SOST to SOMT Before converting the system into multi-sdr, preserve the contents of the hard disk in default-sdr mode as the contents will be lost during the hard disk partition among the named-sdrs. Copy the contents using copy command between System Admin and XR modes. Hard disk is partitioned between the SDRs. Each named-sdr gets ~33M of the system hard disk Required Cards for Each SDR Set of physical line cards with Route Processor (RP) shared across SDRs. Software Version Requirements Multi-SDRs are supported only on NCS-6008 single-chassis running the Cisco IOS XR software Release and later. Maximum SDR Configurations A maximum of three named-sdrs can be configured on NCS Upgrade or Downgrade of Software - Multi-SDR Environment System upgrade for Release is not supported in multi-sdr. For detailed information about System Setup and Software Installation, see the System Setup and Software Installation Guide for Cisco NCS 6000 Series Routers. SysAdmin (Calvados) SysAdmin (Calvados) can be independently upgraded or downgraded in Cisco IOS XR software Release Named-SDR XR Each named-sdrs can be upgraded or downgraded to run different versions of Cisco IOS XR software Release 6.1.2, based on the XR image. For detailed information, see System Setup and Software Installation Guide for Cisco NCS 6000 Series Routers. SMU and Package Installation - Multi-SDR Environment No change with reference to SMU installation on Calvados SMU and package installation on XR of named-sdr is similar to default-sdr SMUs and packages of each SDR is independent of other SDRs 2

3 Information About Only one operation of upgrade/downgrade/smu install/smu deactivation can be performed at a time similar to default-sdr. An Orchestrated Calvados Upgrade (OCU) cannot be performed on a Multi-SDR from Release 6.1.x to later releases (Release 6.2.x onwards). USB Accessibility USB will be accessible only from Sysadmin. It is not accessible from named-sdr, hence cannot install image/smu/package from USB in multi-sdr mode. Information About Review the sections in this module before configuring secure domain routers. What Is a Secure Domain Router? Cisco routers running thecisco IOS XR software can be partitioned into multiple, and independent routers known as secure domain routers (SDRs). SDRs are a means of dividing a single physical system into multiple logically separated routers. They perform routing functions similar to a physical router, but they share resources with the rest of the system. For example, the software, the configurations, the protocols, and the routing tables, which are assigned, are unique to a particular SDR. Other functions, such as chassis-control and switch fabric, are shared with the rest of the system. On NCS-6008 single-chassis, multiple SDRs can be created and each SDR shall be independent of each other. They can be independently upgraded or downgraded and are capable of defining the SDR boundary at the line card level. Multi-SDR By default, system startup in Single Owner Single Tenant (SOST) mode, which is the default-sdr. Creating an explicitly named-sdr and assigning inventory to it, causes the system to transit from SOST mode to Single Owner Multiple Tenant (SOMT) mode, which is the multi-sdr. User configured SDR is also called as named-sdr. The following are the details of the multi-sdrs: The administration (admin) plane operators, manages the system inventory and allocates resources to each named-sdr. The Route Processors (RPs) and Line cards (LC) can be allocated or deallocated to a named-sdr without affecting other SDRs in the system. RP resources like CPU, memory and LC resources are configurable. Each named-sdr can be administered, managed, and operated independent of other named-sdrs in the system, and the admin plane. 3

4 What Is a Secure Domain Router? Each named-sdr can be run on a version of Cisco IOS XR software that is independent of the versions running on other named-sdrs and admin plane. Each named-sdr can be upgraded (non-issu) independently of other named-sdrs in the system. Permissions into the admin plane through SDR are only through the privileges provided by AAA administrator. A maximum of three named-sdrs can be configured on Cisco NCS RPs, fabric cards and other system resources are shared across multi-sdrs. Line cards cannot be shared among named-sdrs. But, multiple line cards can be allocated to a named-sdr. Depending on the named-sdr configuration, each SDR will have it's own RP pair. RPFO in a named-sdr, does not impact other SDRs as each SDR has it's own RP pair. On-the-fly modification of RP resources (CPU or memory) of a named-sdr is not recommended. To convert from SOMT to SOST, system must be USB booted. Advantages of Multi-SDR In multi-sdr, each SDR can be administered, managed, and operated independent of other SDRs, which is similar to multiple default-sdr (multiple XRs). Comparison of Default-SDR with Multi-SDRs The XR VM (SDR/named-SDR) is not aware of SOST or SOMT environment. Therefore, named-sdr behavior is similar to default-sdr. There is no difference between the default-sdr and multi-sdr with respect to the XR features, provisioning of features, or the user interaction. Default-SDR supports system upgrade, but muti-sdr does not support system upgrade. System upgrade is supported with default-sdr, but not with multi-sdr. No Credentials are required by default to access admin from XR in case of default-sdr. In case of named-sdr, to access the admin from the XR, admin of the XR in the named-sdr need admin credentials. Images can be stored in the hard disk with default-sdr. However, with multi-sdr, each SDR has ~33M of hard disk allocated. Hence, due to smaller hard disk size, images cannot be stored in the SDR. USB is accessible from sysadmin and XR with default-sdr. In case of a named-sdr, USB is accessible only from sysadmin. 4

5 What Is a Secure Domain Router? XR Management Traffic in Multi-SDR Environment Each RP has single physical management port. Hence, management traffic of the named-sdr is tagged with the VLAN-ID that is specified during named-sdr configuration. Tagged management traffic of each named-sdr needs to be segregated by the user using an external switch. As XR is unaware of the VLAN tagging or multi-sdr, there is no change in the management port configuration in the XR. Figure 1: XR Management Traffic in Default-SDR Environment In case of default-sdr, all management traffic is untagged. Figure 2: XR Management Traffic in Multi-SDR Environment In the above topology, VLAN 11 corresponds to SDR-1, VLAN 12 corresponds to SDR-2, and VLAN 13 corresponds to SDR-3. With the additional switch that is added, all the tagged traffic gets untagged. All the management ports can be in the same subnet or in a different subnet as each SDR works as a different router. Sample Configuration for XR Management Traffic in Multi-SDR Environment sdr sdr-1 resources mgmt_ext_vlan 11 resources card-type RP vm-memory 20 vm-cpu 5 location 0/0 location 0/RP0 location 0/RP1 sdr sdr-3 5

6 What Is a Secure Domain Router? resources mgmt_ext_vlan 13 resources card-type RP vm-memory 12 vm-cpu 5 location 0/1 location 0/RP0 location 0/RP1 sdr sdr-2 resources mgmt_ext_vlan 12 resources card-type RP vm-memory 10 vm-cpu 5 location 0/6 location 0/RP0 location 0/RP1 Management ports config in XR of sdr-2 : interface MgmtEth0/RP0/CPU0/0 ipv4 address interface MgmtEth0/RP1/CPU0/0 ipv4 address router static address-family ipv4 unicast / / telnet ipv4 server max-servers 10 Management ports config in XR of sdr-3: interface MgmtEth0/RP0/CPU2/0 ipv4 address interface MgmtEth0/RP1/CPU2/0 ipv4 address router static address-family ipv4 unicast / / telnet ipv4 server max-servers 10 Management ports config in XR of sdr-1: interface MgmtEth0/RP0/CPU1/0 ipv4 address interface MgmtEth0/RP1/CPU1/0 ipv4 address

7 Console Access to Named-SDRs router static address-family ipv4 unicast / / telnet ipv4 server max-servers 10 Switch connected RP0 and RP1 mgmt ports : ========================================== interface GigabitEthernet0/1 description "connected to 0/RP0 mgmt physical port" switchport trunk encapsulation dot1q switchport mode trunk interface GigabitEthernet0/2 description "connected to 0/RP1 mgmt physical port" switchport trunk encapsulation dot1q switchport mode trunk interface GigabitEthernet0/11 switchport access vlan 11 description "for sdr-1 mgmt" load-interval 30 interface GigabitEthernet0/12 description "for sdr-2 mgmt" switchport access vlan 12 switchport mode access interface GigabitEthernet0/13 description "for sdr-3 mgmt" switchport access vlan 13 switchport mode access Console Access to Named-SDRs By default, console1 on active RP is used to access XR VM. With named-sdrs, you can either use console1 or console2 of an active RP to access any of the named-sdr ( XR VM). You can connect two named-sdrs (XRs) at any given time. Active RP of an XR VM can be either RP0 or RP1 based on the RP on which XR VM gets created first, similar to default-sdr. Figure 3: Faceplate of RP 7

8 How to Configure Multiple Secure Domain Routers Item No Details Console0: SysAdmin Console Console1: XR console for both default-sdr and named-sdr Console2: XR console for named-sdr only SysAdmin Ethernet XR VM MGMT Ethernet How to Configure Multiple Secure Domain Routers To create multiple named-sdrs, delete the default-sdr and then configure an explicitly named-sdr by assigning an inventory to it. Deleting Default-SDR By default, system startup with default-sdr, which is SOST environment. To configure named-sdrs, default-sdr must be deleted which enables the system to convert from SOST to SOMT environment. Before You Begin The procedures in this section can be performed only on a router that currently runs thecisco IOS XR software. Verify all the nodes are in operational state by using the show platform command before converting it from SOST to SOMT environment. SUMMARY STEPS 1. config 2. no sdr default-sdr 3. commit DETAILED STEPS Step 1 Command or Action config Purpose Enters XR Config mode. Step 2 sysadmin-vm:0_rp0# config no sdr default-sdr Removes the default-sdr from the system. sysadmin-vm:0_rp0(config)# no sdr default-sdr 8

9 Configuring Multiple Secure Domain Routers Step 3 Command or Action commit Purpose XR VM is deleted. sysadmin-vm:0_rp0# show running-config sdr Sun Dec 13 13:17: UTC % No entries found. sysadmin-vm:0_rp0# show sdr Sun Dec 13 13:17: UTC % No entries found. sysadmin-vm:0_rp0# show vm Wed Feb 24 11:08: UTC Location: 0/0 sysadmin running NA/NA Location: 0/1 sysadmin running NA/NA Location: 0/6 sysadmin running NA/NA Location: 0/RP0 sysadmin running NA/NA Location: 0/RP1 sysadmin running NA/NA Configuring Multiple Secure Domain Routers These tasks explain how to configure a named-sdr with Route Processors (RPs) and allocate line cards. Fabric cards and other system resources are shared implicitly among named-sdrs. Before You Begin To configure named-sdrs, the default-sdr must be deleted. Default values are available for vlan-id, vm-memory and vm-cpu. 9

10 Configuring Multiple Secure Domain Routers SUMMARY STEPS 1. config 2. sdr sdr-name 3. resources mgmt_ext_vlan vlan-id 4. resources card-type RP 5. vm-memory unit 6. vm-cpu number-of-cpus 7. location node-id 8. location node-id 9. exit 10. location node-id 11. commit DETAILED STEPS Step 1 Command or Action config Purpose Enters system administration configuration mode. Step 2 sysadmin-vm:0_rp0# config sdr sdr-name Enters SDR configuration mode for the named-sdr. sysadmin-vm:0_rp0(config)# sdr sdr1 Creates a new SDR and you add the resources as described in the following steps. Step 3 resources mgmt_ext_vlan vlan-id sysadmin-vm:0_rp0(config-sdr-sdr1)# resources mgmt_ext_vlan 11 A maximum of three named-sdrs can be configured. Configures the vlan-id for tagging the XR management traffic and this confines the management traffic to the configured named-sdr in step 2. Default value for first named-sdr = 2 Default value for second named-sdr = 3 Default value for third named-sdr = 4 Configurable minimum value = 2 Configurable maximum value = 4094 Step 4 resources card-type RP Allocates RP resources. sysadmin-vm:0_rp0(config-sdr-sdr1)# resources card-type RP 10

11 Configuring Multiple Secure Domain Routers Step 5 Step 6 Step 7 Command or Action vm-memory unit sysadmin-vm:0_rp0(config-card-type-rp)# vm-memory 11 vm-cpu number-of-cpus sysadmin-vm:0_rp0(config-card-type-rp)# vm-cpu 4 location node-id Purpose Allocates RP memory to the named-sdr. Unit of VM memory size is in GB. Default value for three named-sdrs = 11 Configurable minimum value = 4 Configurable maximum value = 12 Allocates RP CPU to the named-sdr. Default value for two or three named-sdrs = 4 Configurable minimum value = 2 Configurable maximum value = 6 Allocates RP to the named-sdr. Step 8 sysadmin-vm:0_rp0(config-sdr-sdr1)# location 0/RP0 location node-id Allocates second RP to the named-sdr for redundancy. Step 9 Step 10 sysadmin-vm:0_rp0(config-location-0/rp0)# location 0/RP1 exit sysadmin-vm:0_rp0(config-location-0/rp1)# exit location node-id Exits the RP configuration mode and returns to named-sdr configuration mode. Allocates line card to the named-sdr. Step 11 sysadmin-vm:0_rp0(config-sdr-sdr1)# location 0/0 commit What to Do Next After VMs of the named-sdr get created, verify VM states using the following commands: show running-config sdr show sdr show vm 11

12 Configuring Console Access to Named-SDR Configuring Console Access to Named-SDR These tasks explain how to configure the console access to a named-sdr. You can connect to all three SDRs by applying console-attach command to both RPs. But, you cannot connect to all SDRs by completing the vty configuration on just one RP. SUMMARY STEPS 1. config 2. console attach-sdr location node-id tty-name tty-name sdr-name sdr-name 3. commit DETAILED STEPS Step 1 Command or Action config Purpose Enters system administration configuration mode. Step 2 Step 3 sysadmin-vm:0_rp0# config console attach-sdr location node-id tty-name tty-name sdr-name sdr-name sysadmin-vm:0_rp0(config)# console attach-sdr location 0/RP0 tty-name console1 sdr-name sdr2 commit Specifies the location, tty name and named-sdr that can be accessed through console of active RP. Active RP has to be configured as node-id tty-name can either be console1 or console2. sdr-name refers to the named-sdr Configuration Examples for Multiple Secure Domain Routers This section provides the following multi-sdrs configuration examples: Deleting Default-SDR: Example The following example shows how to delete a default- SDR: sysadmin-vm:0_rp0# config Thu Aug 11 00:22: UTC Entering configuration mode terminal sysadmin-vm:0_rp0(config)# no sdr default-sdr Thu Aug 11 00:22: UTC 12

13 Creating Multi-SDRs: Example sysadmin-vm:0_rp0(config)# commit Thu Aug 11 00:22: UTC Commit complete. Creating Multi-SDRs: Example The following example shows how to create a new SDR: sysadmin-vm:0_rp0# config sysadmin-vm:0_rp0(config)# sdr VRFPE-SDR1 sysadmin-vm:0_rp0(config-sdr-vrfpe-sdr1)# resources mgmt_ext_vlan 11 sysadmin-vm:0_rp0(config-sdr-vrfpe-sdr1)# resources card-type RP vm-memory 11 vm-cpu 4 sysadmin-vm:0_rp0(config-sdr-vrfpe-sdr1)# location 0/RP0 sysadmin-vm:0_rp0(config-location-0/rp0)# location 0/RP1 sysadmin-vm:0_rp0(config-location-0/rp1)# exit sysadmin-vm:0_rp0(config-sdr-sdr1)# location 0/0 sysadmin-vm:0_rp0(config-sdr-sdr1)# commit The following example shows three named-sdrs being configured, there by three XM VMs get created on the RPs and LCs: sysadmin-vm:0_rp0# config Thu Aug 11 00:22: UTC Entering configuration mode terminal sysadmin-vm:0_rp0(config)# sdr VRFPE-SDR1 sysadmin-vm:0_rp0(config-sdr-vrfpe-sdr1)# resources mgmt_ext_vlan 11 sysadmin-vm:0_rp0(config-sdr-vrfpe-sdr1)# resources card-type RP sysadmin-vm:0_rp0(config-card-type-rp)# vm-memory 11 sysadmin-vm:0_rp0(config-card-type-rp)# vm-cpu 4 sysadmin-vm:0_rp0(config-card-type-rp)# sysadmin-vm:0_rp0(config-card-type-rp)# location 0/RP0 sysadmin-vm:0_rp0(config-location-0/rp0)# sysadmin-vm:0_rp0(config-location-0/rp0)# location 0/RP1 sysadmin-vm:0_rp0(config-location-0/rp1)# sysadmin-vm:0_rp0(config-location-0/rp1)# location 0/0 sysadmin-vm:0_rp0(config-location-0/0)# sysadmin-vm:0_rp0(config-location-0/0)# sysadmin-vm:0_rp0(config-location-0/0)# sysadmin-vm:0_rp0(config-location-0/0)# sysadmin-vm:0_rp0(config-location-0/0)# sdr Internet-SDR sysadmin-vm:0_rp0(config-sdr-internet-sdr)# resources mgmt_ext_vlan 12 sysadmin-vm:0_rp0(config-sdr-internet-sdr)# resources card-type RP sysadmin-vm:0_rp0(config-card-type-rp)# vm-memory 11 sysadmin-vm:0_rp0(config-card-type-rp)# vm-cpu 4 sysadmin-vm:0_rp0(config-card-type-rp)# sysadmin-vm:0_rp0(config-card-type-rp)# location 0/RP0 sysadmin-vm:0_rp0(config-location-0/rp0)# sysadmin-vm:0_rp0(config-location-0/rp0)# location 0/RP1 sysadmin-vm:0_rp0(config-location-0/rp1)# sysadmin-vm:0_rp0(config-location-0/rp1)# location 0/6 sysadmin-vm:0_rp0(config-location-0/6)# sysadmin-vm:0_rp0(config-location-0/6)# sysadmin-vm:0_rp0(config-location-0/6)# sysadmin-vm:0_rp0(config-location-0/6)# sdr P-SDR sysadmin-vm:0_rp0(config-sdr-p-sdr)# resources mgmt_ext_vlan 13 sysadmin-vm:0_rp0(config-sdr-p-sdr)# resources card-type RP sysadmin-vm:0_rp0(config-card-type-rp)# vm-memory 11 sysadmin-vm:0_rp0(config-card-type-rp)# vm-cpu 4 sysadmin-vm:0_rp0(config-card-type-rp)# sysadmin-vm:0_rp0(config-card-type-rp)# location 0/RP0 sysadmin-vm:0_rp0(config-location-0/rp0)# sysadmin-vm:0_rp0(config-location-0/rp0)# location 0/RP1 sysadmin-vm:0_rp0(config-location-0/rp1)# sysadmin-vm:0_rp0(config-location-0/rp1)# location 0/1 sysadmin-vm:0_rp0(config-location-0/1)# sysadmin-vm:0_rp0(config-location-0/1)# sysadmin-vm:0_rp0(config-location-0/1)# 13

14 Creating Multi-SDRs: Example sysadmin-vm:0_rp0(config-location-0/1)# sysadmin-vm:0_rp0(config-location-0/1)# sysadmin-vm:0_rp0(config-location-0/1)# sysadmin-vm:0_rp0(config-location-0/1)# commit Thu Aug 11 00:31: UTC Commit complete. sysadmin-vm:0_rp0(config-location-0/1)# System message at :31:21... Commit performed by admin via tcp using system. sysadmin-vm:0_rp0(config-location-0/1)# end Thu Aug 11 00:31: UTC sysadmin-vm:0_rp0# 0/6/ADMIN0:Aug 11 00:32: : vm_manager[2907]: %INFRA-VM_MANAGE Info: vm_manager started VM Internet-SDR--1 0/0/ADMIN0:Aug 11 00:32: : vm_manager[2902]: %INFRA-VM_MANAGER-4-INFO : Info: vmtarted VM VRFPE-SDR1--1 0/RP1/ADMIN0:Aug 11 00:33: : vm_manager[3162]: %INFRA-VM_MANAGER-4-INFO : Info: started VM Internet-SDR--1 0/RP0/ADMIN0:Aug 11 00:33: : vm_manager[3183]: %INFRA-VM_MANAGER-4-INFO : Info: started VM Internet-SDR--1 0/1/ADMIN0:Aug 11 00:33: : vm_manager[2917]: %INFRA-VM_MANAGER-4-INFO : Info: vmtarted VM P-SDR--1 0/RP1/ADMIN0:Aug 11 00:34: : vm_manager[3162]: %INFRA-VM_MANAGER-4-INFO : Info: started VM P-SDR--2 0/RP0/ADMIN0:Aug 11 00:35: : vm_manager[3183]: %INFRA-VM_MANAGER-4-INFO : Info: started VM P-SDR--2 0/RP1/ADMIN0:Aug 11 00:36: : vm_manager[3162]: %INFRA-VM_MANAGER-4-INFO : Info: started VM VRFPE-SDR1--3 0/RP0/ADMIN0:Aug 11 00:36: : vm_manager[3183]: %INFRA-VM_MANAGER-4-INFO : Info: started VM VRFPE-SDR1--3 Running Configuration: Example The following example shows the running configuration of three named-sdrs: sysadmin-vm:0_rp0# show run sdr Tue Aug 16 18:50: UTC sdr Internet-SDR resources mgmt_ext_vlan 12 resources card-type RP vm-memory 11 vm-cpu 4 location 0/6 location 0/RP0 location 0/RP1 sdr P-SDR resources mgmt_ext_vlan 13 resources card-type RP vm-memory 11 vm-cpu 4 location 0/1 location 0/RP0 location 0/RP1 sdr VRFPE-SDR1 resources mgmt_ext_vlan 11 resources card-type RP vm-memory 11 vm-cpu 4 location 0/0 location 0/RP0 14

15 Creating Multi-SDRs: Example location 0/RP1 Verification: Example The following example shows the details of the three named-sdrs: sysadmin-vm:0_rp0# show sdr Wed Aug 17 16:01: UTC SDR: Internet-SDR Location IP Address Status Boot Count Time Started /RP0/VM RUNNING 1 08/11/ :33:12 0/RP1/VM RUNNING 1 08/11/ :33:01 0/6/VM RUNNING 1 08/11/ :32:48 SDR: P-SDR Location IP Address Status Boot Count Time Started /RP0/VM RUNNING 2 08/11/ :24:43 0/RP1/VM RUNNING 2 08/11/ :24:32 0/1/VM RUNNING 2 08/11/ :25:26 SDR: VRFPE-SDR1 Location IP Address Status Boot Count Time Started /RP0/VM RUNNING 2 08/11/ :32:15 0/RP1/VM RUNNING 2 08/11/ :32:23 0/0/VM RUNNING 2 08/11/ :32:40 The following example shows the details of the VM: sysadmin-vm:0_rp0# show vm Wed Aug 17 16:01: UTC Location: 0/0 sysadmin running NA/NA VRFPE-SDR1 running /58375 Location: 0/1 sysadmin running NA/NA P-SDR running /58360 Location: 0/6 sysadmin running NA/NA Internet-SDR running /58401 Location: 0/RP0 sysadmin running NA/NA Internet-SDR running / P-SDR running / VRFPE-SDR1 running / Location: 0/RP1 sysadmin running NA/NA Internet-SDR running /

16 Creating Multi-SDRs: Example P-SDR running / VRFPE-SDR1 running / sysadmin-vm:0_rp0# show sdr Internet-SDR detail Wed Aug 17 16:07: UTC SDR Detail at location 0/RP0/VM SDR Id 2 IP Address of VM MAC address of VM 64:F6:9D:78:FD:36 Boot Partition /dev/panini_vol_grp/xr_lv0 Data Partition /dev/pci_disk1/xr_data_lv0 Big Disk Partition /dev/pci_disk1/ssd_disk1_xr_2 VM Id 1 VM CPUs 4 VM Memory[in MB] Card Type RP_Card Card Serial SAL19058TGE Rack Type Line_Card_Controller Chassis Serial FLM184073K4 Hardware Version 0.4 Management External VLAN 12 VM State RUNNING Start Time "08/11/ :33:12" Reboot Count(Since VM Carving) 1 Reboot Count(Since Card Reload) 1 08/11/ :33:12 FIRST_BOOT SDR Detail at location 0/RP1/VM SDR Id 2 IP Address of VM MAC address of VM 4C:4E:35:B6:94:BC Boot Partition /dev/panini_vol_grp/xr_lv0 Data Partition /dev/pci_disk1/xr_data_lv0 Big Disk Partition /dev/pci_disk1/ssd_disk1_xr_2 VM Id 1 VM CPUs 4 VM Memory[in MB] Card Type RP_Card Card Serial SAL1830XFD5 Rack Type Line_Card_Controller Chassis Serial FLM184073K4 Hardware Version 0.4 Management External VLAN 12 VM State RUNNING Start Time "08/11/ :33:01" Reboot Count(Since VM Carving) 1 Reboot Count(Since Card Reload) 1 08/11/ :33:01 FIRST_BOOT SDR Detail at location 0/6/VM SDR Id 2 IP Address of VM MAC address of VM E2:3B:46:4F:8D:05 Boot Partition /dev/panini_vol_grp/xr_lv0 Data Partition /dev/panini_vol_grp/xr_data_lv0 Big Disk Partition (null) VM Id 1 VM CPUs 3 VM Memory[in MB] 6383 Card Type LC_Card Card Serial SAD161300T5 Rack Type Line_Card_Controller Chassis Serial FLM184073K4 Hardware Version 0.2 Management External VLAN 12 VM State RUNNING Start Time "08/11/ :32:48" Reboot Count(Since VM Carving) 1 Reboot Count(Since Card Reload) 1 08/11/ :32:48 FIRST_BOOT 16

17 Configuring Console Access to Named-SDRs: Example Configuring Console Access to Named-SDRs: Example The following example shows how to configure console access to named-sdrs: The following example shows the console details: sysadmin-vm:0_rp0# config sysadmin-vm:0_rp0(config)# console attach-sdr location 0/RP0 tty-name console1 sdr-name VRFPE-SDR1 sysadmin-vm:0_rp0(config)# console attach-sdr location 0/RP1 tty-name console1 sdr-name VRFPE-SDR1 sysadmin-vm:0_rp0(config)# console attach-sdr location 0/RP0 tty-name console2 sdr-name P-SDR sysadmin-vm:0_rp0(config)# console attach-sdr location 0/RP1 tty-name console2 sdr-name P-SDR sysadmin-vm:0_rp0(config)# commit sysadmin-vm:0_rp0# show run console console attach-sdr location 0/RP0 tty-name console1 sdr-name VRFPE-SDR1 console attach-sdr location 0/RP1 tty-name console1 sdr-name VRFPE-SDR1 console attach-sdr location 0/RP0 tty-name console2 sdr-name P-SDR console attach-sdr location 0/RP1 tty-name console2 sdr-name P-SDR The following table provides the example of console access to the three named-sdrs: Command On system boot-up Console0 Access sysadmin Console1 Access to default sdr-xr Console2 Unused no sdr delete-sdr Access sysadmin Unused Unused console attach-sdr location 0/RP0 tty-name console1 sdr-name sdr1 Access sysadmin Access to named-sdr1 XR Unused (assuming 3 named-sdrs are configured) console attach-sdr location 0/RP0 tty-name console2 sdr-name sdr2 Access sysadmin Access to named-sdr1 XR Access to named-sdr2 XR (assuming 3 named-sdrs are configured) On system reload Access sysadmin Access to named-sdr1 XR Access to named-sdr2 XR (assuming 3 named-sdrs are configured) 17

18 Configuring Console Access to Named-SDRs: Example Command Console0 Console1 Console2 console attach-sdr location 0/RP0 tty-name console2 sdr-name sdr3 Access sysadmin Access to named-sdr1 XR Access to named-sdr3 XR (assuming 3 named-sdrs are configured) console attach-sdr location 0/RP0 tty-name console1 sdr-name sdr2 Access sysadmin Access to named-sdr2 XR Access to named-sdr3 XR (assuming 3 named-sdrs are configured) no sdr Access sysadmin Unused Unused (all named-sdr removed) console attach-sdr location 0/RP0 tty-name console2 sdr-name sdr1 Access sysadmin Unused Access to named-sdr1 XR (assuming only one sdr (sdr1) is configured) 18