RJP INFOTEK - CORPORATE VIDEO

ENHANCEMENT IN XENDESKTOP

The general idea

The FMA is primarily made up out of Delivery Controllers and Agents. Delivery Agents are installed on all virtual and or physical machines provisioned by XenDesktop 7, they communicate (and register themselves) with the Delivery Controller(s) and the license server. The Controllers on their turn communicate with a central (SQL) database. This database is very important, next to things like XenDesktop Site policies, Machine Catalogs, Delivery Groups and published applications and or (hosted) desktops, it also contains all live dynamic ‘runtime’ data like: who is connected to which resource, on which server, server load and connection statuses used to make load balance decisions and so forth. Make sure you implement some kind of database redundancy like SQL replication or clustering of some sort. If the database isn’t reachable for some reason running sessions will keep working but new sessions cannot be established and configuration changes aren’t possible, keep that in mind. More on the overall architecture and its components in a minute. The picture below, owned by Citrix, isn’t new but it does still provides us with a clear overview on the overall XD7 architecture.

A quote from Citrix: “Unlike XenApp, the Delivery Agent communicates only with the controllers in the site and does not need to access the site database or license server directly” Having quoted that, XenApp workers (session host only servers) offer the same sort of benefit. As they only host user sessions and will (or can) never be  ‘elected’ as an Data Collector for their zone they won’t get all the IMA store (database) information pushed into their LHC enhancing overall performance. However, these workers still consist of the same bits and bytes as installed on a Data Collector compared to ‘just’ a Delivery Agent which are lighter weight, as Citrix puts it.

FMA vs IMA

With the introduction of XenDesktop 7 IMA is gone! But what does this tell us? Well… It basically means that Zones together with their Zone Data Collectors are gone (it’s now one big Site) so no more Zone preference policies and Load Balance policies are now applied at Site level instead of Zones. No more IMA protocol and Service, these are replaced by the XD7 Virtual Agents that get installed on all Virtual and or Physical machines provisioned through XenDesktop 7. Since Data Collectors (and thus Zones) are no longer part of the overall architecture and all virtual and or physical servers in XD7 basically function as ‘Workers’ or ‘Session only Mode’ (as far as the former XenApp servers are concerned anyway) this also means that most of our old XenApp designs don’t apply anymore and it might be time to re-think and re-design them. Data flow has changed and in some designs different rules now apply.

LHC

XD7 Delivery Controllers don’t have a Local Host Cache (LHC) this means that user authentication, application enumeration (and requests) and user connection requests, plus a few more :-) all need to come from the central SQL DB, including server Load Balance information. XenDesktop has been doing it this way for a while now so it should be ok.

Improved

In XenDesktop 7 the FMA now combines provisioning and personalization tools for both desktops and applications. New and improved features include: Windows 8 and Windows Server 2012 support, Application publishing, XenApp is merged into XD or FMA if you will, allowing you to publish applications and or hosted shared desktops from Server OS’s. As of this release Machine Creation Services can also be used to provision virtual server machines (also called Workloads) not just desktops, a big step forward! Note that Citrix Provisioning Services (PVS) can still be used, no real changes there.

The best thing is, all Agents communicate with the same controller no matter which OS is installed! This is what makes the diversity in operating systems possible especially for XenApp. For example, you can have one Delivery Group (again, we already had these in previous versions of XD, the same goes for Machine Catalogs as well) applied to multiple different Machine Catalogs. See below and as opposed to XenApp, the Delivery Controller (former Data Collector) no longer needs to have Terminal Services installed.

Machine Creation Services

Big part of the overall FMA. As you know MCS within XD7 and earlier version takes care of the provisioning of virtual machines, multiple (tens, hundreds, thousands even) at once  on your underlying Host Infrastructure (your Hypervisor of choice) which in the case of XD7 can either be desktop or server workloads, Windows 8 and Server 2012 included. Some cool new features have been announced recently, I picked them up during one of Citrix’s Master Classes, read on below.

With the introduction of Hyper-V 3.0 in Server 2012 new features have become available. MCS as well as PVS can now both leverage SMB 3.0 shared folders on file servers with clustered shared volumes and SAN’s and use them as shared storage.

When Hyper-V 3.0 is used as the underlying Hypervisor MCS supports the VHDX format. Secondary disks attached to the virtual machine destined for PVS Write cache for example will also automatically leverage the ‘new’ VHDX format, the same goes for PVS Personal vDisks. PVS disks that are accessed and managed directly from the Provisioning Server itself will continue to use the VHD format since PVS is and can still be used on Windows Server 2008 R2 as well.

MCS can take advantage of another Hyper-V 3.0 feature called: Clustered Shared Volume Read Caching. I got this from one of the Citrix Blogs: XenDesktop 7 can take advantage of this capability to reduce storage IO for MCS catalogs during boot and logon storms.  The effect is similar to that of the caching that takes place on PVS hosts, except that the blocks are delivered once to each Hyper-V host and then shared among the VMs on that host. CSV cashing makes use of host RAM for this cache so there will be some tradeoff between cache size and the amount of RAM available to VM’s.

MCS now also supports KMS during the image creation process. It enables the KMS system to record each VM as a separate machine. Each machine created provides unique activation for Windows as well as Office 2010 installations.

When creating a master image and Personal vDisks are involved, it’s no longer necessary to manually run an inventory at the end of the image creation process. Also, during the image preparation process DHCP is now automatically enabled.

Storage Superseding. A new concept to MCS, you can configure certain storage in a way so that existing virtual machines on there will keep functioning but new provisioned virtual machines won’t be created on that specific storage. A nice feature to use when your storage is almost full.

PVS and MCS go hand in hand: you can create a Delivery Group containing both PVS and MCS provisioned machines. Perhaps not something you will implement in ‘real life’ but it shows you just how flexible the product is. Could be nice for POC’s though.

Catalogs

As far as XenDesktop goes a Catalog is still a catalog, you can have a Windows 7 catalog, a Windows 8 catalog etc… For XenApp however, things are different. From a XenApp point of view you can compare a Catalog with a Worker group with a few exceptions… As you probably know, in a XenApp Farm all the server systems need to have the same operating system installed, no exceptions. So if you have 2 or more Worker groups then all the systems within those groups will have the same OS installed. In XD7 things work different, for example, you can create two different Catalogs (Worker groups) for use with XenApp in which you can have one Catalog with Windows Server 2008R2 installed and another with Windows Server 2012 and publish two separate hosted shared desktops, all within the same infrastructure, a big change!

Delivery Groups

Delivery groups are not a new concept just a name change, used to be called Desktop groups in XenDesktop, they are still created from, or applied to, Catalogs and pretty much fulfill the same tasks. There is a big change though… In earlier versions of XenDesktop you assigned a Desktop Group to a Catalog or multiple Catalogs if needed, but the Catalogs all needed to be exactly the same, meaning that they all shared the same common image, 2008R2 for example. Now, in XD7 it is possible to assign a single Delivery group to multiple different Catalogs, as mentioned earlier. Think back to the example above, two Catalogs with two different operating systems installed same here but with just one Delivery group assigned to them. Simplified management! The same goes for XenApp, two different Catalogs: 2008R2 and 2012 (which already is a big new feature on its self), one Delivery group.

A quick note one the above, I haven’t got the chance to look at the final product yet, but during one of Citrix’s Masterclasses it showed that Delivery Groups can be used to either publish applications or (VDI) desktop or both from the same Delivery Group. This process is slightly different from the App publishing feature in the Excalibur Tech Preview release where Delivery Groups get added during the application publishing process. So I’m not sure if both options are still in there.

All under one roof

No more separate infrastructures for desktops and applications, it’s one install, architecture and console (Citrix Studio) to meet all your delivery needs. It includes several workflows which simplify and speed up the process of delivering desktops and applications to users. Delivery Agents in XD7 are configured via policies.  Any combination of Active Directory GPOs, the Studio console (HDX Policy), and Local GPO settings can be used.

This comes from one of the Citrix Blogs regarding FMA: The biggest difference between the two Delivery Agents (there are desktop and server DA’s) is the ICA protocol stack used.  For desktop machines, Citrix ships a single-user ICA stack (internally known as PortICA) which allows only one ICA session at a time.  This version connects users to the machine’s console session, similar GoToMyPC or other Remote Access products for a Desktop OS.  It also includes additional HDX features such as USB and Aero redirection, which are only available on a single-user machine.  For server machines, Citrix includes a multi-user ICA stack, which extends Windows Remote Desktop Services with the HDX protocol.  This is the same ICA protocol stack developed for Citrix XenApp, just with a different management interface to make it compatible with Excalibur controllers. I couldn’t have said it any better :-)

Other high level FMA changes

Some new services are introduced # The delegated admin service providing the Roles and Scopes # Configuration Logging # Monitor Service # Environment Tests # StoreFront integration # Machine Creation Services has been reduced to two services in total.

Some more changes:

There is a secondary database specifically for Configuration Logging and the Monitor Service # Remote PC is fully integrated into the Catalogs and Delivery Groups # Load Balancing is controlled via Group Policy, on Site level that is # Applications are now associated with Delivery Groups and application attributes like color depth and audio are also configured through Delivery Groups.

FlexCast Delivery Technology

FlexCast delivery technology… Desktop virtualization for everyone. One of the many marketing term out there. FlexCast offers you several delivery models, one solution to meet al use cases. It is designed to support all type of workers (as Citrix likes to call them) out there. For example, Task Workers access a small set of applications but at the same time they interact with customers, partners and employees. As a result they have access to critical data. A local Virtual Machine might be the best solution, here’s where FlexCast comes in. Another example, so called Road Warriors need access to their desktop from anywhere, here a Hosted VDI of Hosted Shared desktop might do the trick, again… FlexCast! Of-course it’s all up to you, you decide which model best suites the use case at hand! FlexCast offers you the following desktop delivery models:

• Local Virtual Machine
• Streamed VHD
• Hosted VDI
• Hosted Shared
• On-Demand Apps

Here’s a nice quote from one of the Citrix Blogs written almost four years ago but still valid “I find that it helps me to think of FlexCast more as a strategy for delivering desktops, than as a specific technology. It’s about thinking of all your virtual desktop and application delivery methods as a toolbox that enable you to directly address the different performance, security, personalization and mobility requirements of all your users” Nice one right?! Below is a  graphical overview, well… of FlexCast Delivery in combination with the ICA / HDX protocol.

Detailed overview

Conclusion

That’s it, I hope this has been somewhat informative. If you have any doubt, send mail to raghu@rjpinfotek.com

Reference materials used: Citrix.com, Google.com and the E-Docs website.

Collection of RUN commands

Hello everyone,Today we will see all Run commands that can be used in you windows pc.

These Run commands will help you to run the Program without any difficulties.
just click on start>run and type the run command for that particular program you want to run. that's it.

Following are the program name and their Run commands.

[A]

Add/Remove Programs = appwiz.cpl
Administrative Tools = control admintools
Authorization Manager= azman.msc “New”

[C]

Calculator = calc
Certificate Manager = certmgr.msc
Character Map = charmap
Check Disk Utility = chkdsk
Control Panel = control “New”
Command Prompt = cmd.exe
Component Services = dcomcnfg
Computer Management = compmgmt.msc = CompMgmtLauncher “New”

[D]

Date and Time Properties = timedate.cpl
Downloads = Downloads ”New”
Device Manager = devmgmt.msc
Direct X Troubleshooter = dxdiag
Disk Cleanup Utility = cleanmgr
Defragment User Interface = dfrgui ”New”
Digitilizer Calibration Tool = tabcal ”New”
Disk Management = diskmgmt.msc
Disk Partition Manager = diskpart
Display Properties = control desktop or desk.cpl
DPI Scaling = dpiscaling ”New”
Driver Package Installer = dpinst ”New”
Driver Verifier Utility = verifier or /reset
DVD Player = dvdplay ”New”

[E]

Encryption File System = rekeywiz ”New”
Event Viewer = eventvwr.msc

[F]

Fax Cover Sheet Editor = fxscover ”New”
File Signature Verification Tool = sigverif
Folders Properties = control folders
Fonts = control fonts
Free Cell Card Game = freecell

[G]

Game Controllers | joy.cpl
Group Policy Editor = gpedit.msc

[I]

Internet Explorer = iexplore
Iexpress Wizard = iexpress
Internet Properties = inetcpl.cpl
IP Configuration = ipconfig.exe
iSCSI Initiator = iscsicpl ”New”

[K]

Keyboard Properties = control keyboard

[L]

Libraries = explorer or Windows key + E
Local Security Settings = secpol.msc
Local Users and Groups = lusrmgr.msc
Logs You Out Of Windows = logoff

[M]

Microsoft Support Diagnostic Tool = msdt ”New”
Microsoft Paint = mspaint.exe
Mouse Properties = control mouse
Mouse Properties = main.cpl
Mobility Center (only on mobile) = mblctr or Windows key + X

[N]

Network Connections = control netconnections
Network Connections = ncpa.cpl
Notepad = notepad 

[O]

ODBC Data Source Administrator = odbcad32 “New”
Optional Features Manager = optionalfeatures “New”
On Screen Keyboard = osk or Windows key + U

[P]

Package Installer = dpinst
Pen & Touch Options = tabletpc.cpl
People Near Me Identifier = collab.cpl
Performance Monitor = perfmon.msc
Phone and Modem Options = telephon.cpl
Power Configuration = powercfg.cpl
Printers and Faxes = control printers
Printer Migration = PrintBrmUi ”New”
Private Character Editor = eudcedit
Problem Steps Recorder = psr.exe
Programs and Features = appwiz.cpl

[R]

Regional Settings = intl.cpl
Registry Editor = regedit.exe
Remote Assistance = msra “New”
Remote Desktop = mstsc
Resultant Set of Policy = rsop.msc

[S]

Scheduled Tasks = control schedtasks
Screen Resolution = desk.cpl
Security Center = wscui.cpl
Services = services.msc
Shared Folders/MMC = fsmgmt.msc
Shuts Down Windows = shutdown
Snipping Tool = snippingtool ”New”
Sounds and Audio = mmsys.cpl
Sound Recorder = soundrecorder ”New”
Sound Volume = sndvol ”New”
Spider Solitare Card Game = spider
SQL Client Configuration = cliconfg
Stored User Names and Passwords = credwiz ”New”
Sticky Note = StikyNot ”New”
System Configuration Editor = sysedit
System Configuration Utility = msconfig
System File Checker Utility = sfc
System Information = msinfo32
System Properties = sysdm.cpl or Windows key + Pause/Break
System Restore = rstrui.exe

[T]   

Task Manager = taskmgr
Trusted Platform Module = TpmInit ”New”

[U]

Utility Manager = utilman
User Accounts = netplwiz or control userpasswords2

[W]

Windows Activation = slui ”New”
Windows Backup Utility = sdclt ”New”
Windows Fax and Scan = wfs ”New
Windows Firewall = firewall.cpl
Windows Firewall with Advanced Security = wf.msc ”New
Windows Image Acquisition = wiaacmgr ”New”
Windows Media Player = wmplayer
Windows Magnifier = magnify
Windows Management Infrastructure = wmimgmt.msc
Windows Update App Manager = wuapp ”New”
Windows Standalong Update Manager = wusa ”New’
Windows System Security Tool = syskey
Windows Share Creation Wizard = shrpubw ”New”
Wordpad = write

So with this you get all the run commands which will help you.

Read more: http://geekofreak.com/2013/01/collection-of-run-commands-for-windows.html#ixzz2leiD3iQn

New Features of Hyper-V in Windows Server 2012

Private virtual local area network or PVLAN

PVLANs allow Hyper-V administrators to isolate virtual machines from each other (for example, virtual machines cannot contact other virtual machines over the network), while still maintaining external network connectivity for all virtual machines. Hence it increases virtual machine isolation in a multitenant environment, while not degrading access to public network resources.

DHCP guard

DHCP guard drops server messages from unauthorized virtual machines that are acting as DHCP servers. DHCP server traffic from other virtual switch ports is automatically dropped. Thus it protects against rogue DHCP servers.

Router guard

Router guard drops router advertisement and redirection messages from unauthorized virtual machines that are acting as routers. Hence it provides better security and an authorization check for virtual machines.

Hyper-V Extensible Switch

The Hyper-V Extensible Switch is a Layer 2 virtual network switch that provides programmatically managed and extensible capabilities to connect virtual machines to the physical network. The Hyper-V Extensible Switch is an open platform that lets vendors provide extensions written to standard Windows application programming interface (API) frameworks.

Extension monitoring

Multiple monitoring and filtering extensions can be supported at the entrance and outlet portions of the Hyper-V Extensible Switch. It Provides traffic visibility at different layers and enables statistical traffic data to be gathered.

Non-Uniform Memory Access (NUMA) support inside virtual machines

Provides enhanced  performance on large virtual machines by enabling the guest operation system and applications to access local memory faster than remote memory.

Single Root I/O Virtualization (SR-IOV) networking devices

Reduces network latency and host CPU overhead (for processing network traffic); increases network throughput. Windows Server 2012 Hyper-V enables support for SR-IOV-capable network devices and allows the SR-IOV virtual function of a physical network adapter to be assigned directly to a virtual machine.

Hyper-V smart paging

Provides a reliable way to keep virtual machines running when there is not enough physical memory available. If a virtual machine is configured with a lower minimum memory than its startup memory and Hyper-V needs additional memory to restart it, Hyper-V smart paging is used to bridge the gap between minimum and startup memory.

Runtime memory configuration

Provides flexibility to use Dynamic Memory as needed, without affecting other virtual machines. Users can make configuration changes to Dynamic Memory (increase maximum memory or decrease minimum memory) when a virtual machine is running.

Resource Metering in Hyper-V 

Resource Metering allows users to track how many CPU, memory, storage, and network resources are consumed by a virtual machine over time. This information is gathered automatically (without the need to constantly collect data from the virtual machine) and persists with the virtual machine through live migration/other mobility operations. Windows Server 2012 Hyper-V can track and report the amount of data transferred per IP address or virtual machine.

 

Virtual hard disk format

VHDX supports up to 64 TB of storage. It helps to provide protection from corruption due to power failures by logging updates to the VHDX metadata structures. It also helps to prevent performance degradation on

 large-sector physical disks by optimizing structure alignment.  Helps to ensure high quality performance on large-sector disks.

Offloaded data transfer

Windows Server 2012 Hyper-V uses SAN copy offload to copy large amounts of data from one location to another.  Allows the CPU to concentrate on the processing needs of an application.  Provides rapid provisioning and migration of virtual machines.

Data Center Bridging (DCB)

Windows Server 2012 Hyper-V uses DCB capable hardware to converge multiple types of network traffic onto a single network adapter, with a maximum level of service to each. Helps to reduce the cost and complexity of maintaining separate traffic for network, management, live migration, and storage.  Makes it easy to change allocations to different traffic flows.

Virtual Fibre Channel in Hyper-V

Virtual Fibre Channel in Hyper-V provides Fibre Channel ports within the guest operating system.

Multipath I/O (MPIO) functionality

Windows Server 2012 Hyper-V uses MPIO functionality for proper connectivity to Fibre Channel storage within a virtual machine.

Support for 4 KB disk sectors in Hyper-V virtual hard disks

This reduces the impact of 512e disks on the virtual hard disk stack. Uses emerging innovation in storage hardware to increase capacity and reliability.

Quality of Service (QoS)

Windows Server 2012 Hyper-V uses minimum bandwidth to assign specific bandwidth for each type of traffic and to ensure fair sharing during congestion. Enables hosting providers and enterprises to deliver services with predictable network performance to virtual machines on servers running Hyper-V. Reduces the need for expensive network adapters.

to know more about server 2012, join course http://www.rjpinfotek.com/mcse.php

CISCO - IPv6 - Frequently Asked Questions (FAQ)

Introduction

This document contains Frequently Asked Questions(FAQ's) about Internet  Protocol Version 6(IPv6).

Q. How to limit clients getting an  IPv6 address without using a DHCP server ?

A. Use the command"ipv6nd prefix <prefix> no-advertise".This will set a bit in theIPv6 NA packets to tell hosts not to use this prefix for  autoconfiguration.
.

Q. When configuring  Dual Stack VRF,IPv6 address family is not listed as shown in the  example

Ex:  Router(Config-vrf)#address-family

      ipv4  Address  family                          
      Router(config)#interface  GigabitEthernet0/0.901
      Router(config-subif)#ipv6 en
       Router(config-subif)#ipv6 enable
      %GigabitEthernet0/0.901 is  linked to a VRF. Enable IPv6 on thatVRF first.

A. In ""show version"",  check if  the Data license is activated.

Router#  show  version

Technology  Package License Information for Module:'c2900'

Technology	Technology-package	Technology-package	Technology-package
	Current	Type	Next   reboot
ipbase	ipbasek9	permanent	ipbasek9
security	None	None	None
uc	None	None	None
data	None	None	None

Activate the data   license then check, the IPv6 address family will be enabled
Router(config-vrf)#address-family   ?
   ipv4  Address family
   ipv6  Address family

Q. What is the  equivalent command in IPv6 to the "ip igmp helper-address"command?

A. The command is "ipv6 mld host-proxy".MLD proxy feature works in 15.1.2T  or later IOS release.

Q. Why Windows  2003 machine not getting IPv6 address from a DHCP server configured on  Cisco 1800 series router?

A. Windows XP and Windows Server 2003 do not support DHCPv6-based IPv6  address configuration. For further information
refer http://technet.microsoft.com/en-us/library/bb726956.aspx

Q. In a dual  stack network, does the HSRP configuration for an existing interface use  the same group ID as the IPv4 group?

A. HSRP for IPv4 and IPv6 do not have the same group number. One can use  any valid group number for either protocol

Q. Is MHSRP supported on IPv6?

A. Yes,here is a sample IPv6 MHSRP (Multi HSRP)  configuration.

Rtr1  Configuration
------------------
interface Vlan10
ipv6 address  2620:A3::188/64
standby 100 ipv6 FE80:2620:A3::189
standby 100  timers 1 4
standby 100 priority 101
standby 101 ipv6  FE80:2620:A3::190
standby 101 timers 1 4
standby 101 priority 200
standby  101 preempt
!

Rtr2 Configuration
------------------
interface  Vlan10
ipv6 address 2620:A3::187/64
standby 100 ipv6  FE80:2620:A3::189
standby 100 timers 1 4
standby 100 priority 200
standby  100 preempt
standby 101 ipv6 FE80:2620:A3::190
standby 101 timers  1 4
standby 101 priority 101
!

On Router 1

Router1#show standby brief
                      P indicates configured to preempt.
                     |
Interface    Grp  Pri P State   Active          Standby         Virtual IP
Vl10         100  101   Standby FE80::5675:D0FF:FE39:F77F
                                                local           FE80:2620:A3::189

For IPv6 HSRP Configuration example, refer document "IPv6 HSRP Configuration Example"

Q. What's the recommended method to  inform IPv6 clients about a dhcpv6 server?

A. The command that enables IPv6 Relay Agent on an interface:ipv6 dhcp  relay destination <IPv6 address>
For more information on this  command refer :http://www.cisco.com/en/US/partner/docs/ios/ipv6/configuration/guide/ip6-dhcp.html#wp1054443

Q. Getting  Error Message when creating address-family for IPv6 on the 7600 as shown  in the example:

Example : Router(config-vrf)#address-family ipv6
% VRF address family  ipv6 is not supported or not enabled
% Can't activate address-family  'ipv6'

A. In order to enable IPv6 in a VRF, enter the ""mls ipv6 vrf"" command  in global configuration mode. If this command is not used, a VRF is  supported only for the IPv4 address family. Example: Router(config)# mls  ipv6 vrf.For further information on this command refer:
http://www.cisco.com/en/US/docs/ios/ipv6/command/reference/ipv6_09.html#wp2335362

Q. Can I use  two different BGP public AS's like 13445 and 109, one for IPv4 and one  for IPv6.

A. No, for ASes one can only configure one  BGP instance(AS) per box. This is a restriction of both IPv4 and IPv6.

Q. What is the  different between IPv6 Multicast Address and Anycast Address ?

A. Both Multicast address and Anycast  Address identifies a group of nodes or interfaces.Traffic destined for a  multicast address is forwarded to
all the nodes in the group where as  the traffic destined to an anycast address is forwarded to the nearest  node in the group. An anycast address
is essentially a unicast address assigned to more than one interface. For example to identify the set of routers attached    to a particular subnet,
Subnet-Router anycast address is used. The Subnet-Router anycast address is represented by which has a host ID of 0  (0000:0000:0000:0000)
and "subnet prefix" in an anycast address is the prefix that    identifies a specific link.

Q. Does a 7206VXR router support IPV6 Dual Stack Implementation?

A. Yes. It is supported.
.

Q. On configuring an IPv6 HSRP standby group, run into an error message: "%FHRP group not consistent with already configured groups on the switch stack."

A. Only HSRP version 2 supports both IPv4 and IPv6. So configure "standby version 2" under interface.

Q. Error message: "% BGP context not been initialized properly." when Configuring neighbor under address-family IPv6

A. The issue is with the feature set. If the feature set is SP services, the following services are not supported.

• IPv6 Routing: Multiprotocol BGP Extensions for IPv6
• IPv6 Routing: Multiprotocol BGP Link-local Address Peering 

To use these features,change the feature set to Advanced Enterprise Services.
.

Q. How to configure IPv6 netflow?

A. Configuring IPv6 netflow means configuring collection of hardware-routed IPv6 flows. IPv6 netflow is independent of IPv4 netflow except for export configuration, which is same for both. For commands and configuration example, check: How to configure Netflow v9 for IPv6

Q. When configuring IPv6 Netflow on Catalyst 6500 at the interface level,there is no ability to specify the direction of flow export !

A. 6500 platform cannot support egress netflow due to platform limitation, only ingress is supported.For more information, check NDE Configuration Guidelines and Restrictions.

Q.How to configure ICMP rate limiting in an IPv6 environment?

A. ICMP rate limiting is enabled by default with a default interval between error messages of 100 milliseconds and a bucket size (maximum number of tokens to be stored in a bucket) of 10. The command is "ipv6 icmp error-interval". This can be checked by giving "show ip interface <Interface Type> and the output is shown as below:

For further information refer http://www.cisco.com/en/US/docs/switches/lan/catalyst2350/software/12.2_46_ey/configuration/guide/swipv6.html#wp1117074

Q. How is summarization done for IPV6 OSPF?

A. The command for IPv6 summarization is summary-prefix.
In the following example, the summary prefix FEC0::/24 includes addresses FEC0::/1 through FEC0::/24. Only the address FEC0::/24 is advertised in an external link-state advertisement.

ipv6 router ospf 1
router-id 172.16.3.3
summary-prefix FEC0::/24
redistribute static

Native ospf (non-external) routes are summarized using the Area range command. For more information refer to
http://www.cisco.com/en/US/docs/ios/ipv6/command/reference/ipv6_01.html#wp2113662

The following example specifies one summary route to be advertised by the ABR to other areas for all subnets on network 10.0.0.0 and for all hosts on network 192.168.110.0:

interface Ethernet0/0
no ip address
ipv6 enable
ipv6 ospf 1 area 1
!
ipv6 router ospf 1
router-id 192.168.255.6
log-adjacency-changes
area 1 range 2001:1DB8:0:1::/64

Q.How to configure IPv6 under vrf  as we need to activate bgp?

A. Here is a configuration guide for Multiprotocol VRF Configuration.

http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_vpn_ipv4_ipv6_xe.html#wp1055416

Q.On a 3750 Catalyst switch, IPv6 ping doesn't work when "switchport block multicast" is configured.

A. Change the sdm template on switch to "dual-ipv4-and-ipv6 routing". To check the current sdm template, use the command show sdm prefer
To change the sdm template, in the config mode use the command sdm prefer dual-ipv4-and-ipv6 routing.

Note that changing the sdm template requires a reload.

Example:
Switch_3750(Config)# sdm prefer dual-ipv4-and-ipv6 routing
Switch_3750(Config)# exit
Switch_3750# reload

For more information on configuring the sdm templates refer Configuring SDM Templates

Q.Is IPv6 NAT-PT supported by IPv6 cef?

A. NAT-PT is not supported in IPv6 cef path, disable IPv6 cef for NAT-PT. Other option is to go for NAT64, which is available in ASRs currently.

Q.Error message: "% VRF address-family IPv6 is not supported or not enabled" is received when configuring IPv6 address-family within a VRF?

A. Configure the command "mls ipv6 vrf" in the global configuration mode in order to enable IPv6 in VRF.

Q.Can I configure a vlan for IPv6?  How do I go about doing this?

A. To configure a vlan for IPv6, you can change your /48 into /64s (per RFC). /64 can be configured on the  SVI by doing the following steps:

1.) Enable IPv6 Unicast routing
"ipv6 unicast-routing"

2.) Enable IPv6 CEF
"ipv6 cef"

3.) Configure the IPv6 address
  interface vlan 100
   ipv6 address 2620:0046::1/64

Q.When peering with eBGP peer using link local IPv6 address an error message is followed:

% BGP(v6): Invalid scope. Unable to configure link-local peer.

Router(config-router)#neighbor FE80::222:83FF:FEDF:5852%te2/2 remote-as 65222
% BGP(v6): Invalid scope. Unable to configure link-local peer.
A. The correct syntax for establishing BGP session with link-local IPv6 address is as follows:

neighbor link-local-address%interface-name remote-as #

Please note that the %interface-name must be the complete interface name:

Router(config-router)#neighbor FE80::A8BB:CCFF:FE00:C800%Ethernet0/0 remote-as 1

Q.Do you have a chart or documentation on the compatibility of routing protocols, including IPv4 and IPv6, running in the same router?

A. IPv6 and IPv4 routing protocols do co-exist on the same device and there is no compatibility issues between two.

Q.Not able to enable IPv6 addressing scheme on a port-channel interface.

Example:

Router(config)#int port-channel 1
Router(config-if)#ipv6 ?
% Unrecognized command
Router(config-if)#ipv6
                          ^
% Invalid input detected at '^' marker.
A. IPv6 Addresses on a port-channel are unsupported at this time.

Q.Does the Catalyst 3560/3750 supports IPv6 policy based routing (PBR)?

A. Catalyst 3560/3750 does not supports IPv6 policy based routing (PBR). For more details please refer to Unsupported IPv6 Unicast Routing Features on Catalyst 3750 guidelines.

Q. What are major differences between IPv4 and IPv6?

A. A detailed journal is available; please read IPv6 Internal.

Q. What is the default route in IPv6.

A. The default route (any) in IPv6 is specified by ::/0. For example, route to any network in IPv6 (static) will be configured as
Router(config)# ipv6 route ::/0 serial 1/0

Q. Does ASR1K supports tunnel mode gre IPv6?

A. As of now the feature is not available on ASR1K platform. For complete configuration refer to Implementing Tunnels.

Q. Is GLBP for IPv6 supported on 3560E?

A. No, please see Configuring IPv6 Unicast Routing section of configuration for 3560E switches.

Q. What is the feature on IPv6 on Catalyst 6500 similar to ip-helper address?

A. A DHCP relay agent, which may reside on the client's link, is used to relay messages between the client and server. DHCP relay agent operation is transparent to the client. A client locates a DHCP server using a reserved, link-scoped multicast address. Therefore, it is a requirement for direct communication between the client and the server that the client and the server be attached to the same link. However, in some situations in which ease of management, economy, or scalability is a concern, it is desirable to allow a DHCP client to send a message to a DHCP server that is not connected to the same link.

Perform this task to enable the DHCPv6 relay agent function and specify relay destination addresses on an interface.

SUMMARY STEPS
1. enable
2. configure terminal
3. interface type number
4. ipv6 dhcp relay destination ipv6-address [interface-type interface-number]

For a detailed information on when and where to configure the above command, please click on the following link: Implementing DHCP For IPv6

Q. How to find the IPv6 address assigned to a host via DHCP over VPDN?

A. Use command "show ipv6 int virtual-access 2.1 prefix".

For example,

Router# show ipv6 int virtual-access 2.1 prefix

IPv6 Prefix Advertisements Virtual-Access2.1

Codes for 1st column:
        A - Address, P - Prefix-Advertisement, O - Pool
        U - Per-user prefix
Codes for 2nd column and above:
        D - Default
        N - Not advertised, C - Calendar

PD default [LA] Valid lifetime 2592000, preferred lifetime 604800

OD 2404:B800:AD32::/64 [LA] Valid lifetime 2592000, preferred lifetime
604800

Q. IPv6 VRF support is available from which IOS release?

A. The feature is available on IOS XE 3.1.0S onwards on ASR 1000 platform.
Also, check Cisco Feature Navigator for further validation (Requires user id and password).

Q. What is the command that can be used to re-sequence IPv6 access control list (ACL)?

A. IPv6 acl re-sequence feature is not available in IOS.

Q. What are the ICMPv6 messages used by the neighbor discovery protocol?

A. There are 5 ICMPv6 messages used by the neighbor discovery protocol. They are listed as below:

• Router Solicitation (RS)
• Router Advertisement (RA)
• Neighbor Solicitation (NS)
• Neighbor Advertisement (NA)
• Redirect

Q. IPv4 to IPv6. What happened to IPv5?

A. According to Wikipedia, Internet Protocol Version 5 was used by the Internet Stream Protocol, an experimental streaming protocol.  The second version (of Internet Stream Protocol), known variously as ST-II or ST2, distinguishes its own packets with an Internet Protocol version number 5, although it was never known as IPv5.  The Internet Stream Protocol family was never introduced for public use, but many of the concepts available in ST are similar to later Asynchronous Transfer Mode protocols and can be found in Multiprotocol Label Switching (MPLS). They also presaged Voice over IP.   Since the number 5 was already allocated, this number was not considered for the successor to IPv4. Several proposals were suggested as the IPv4 successor, and each was assigned a number. In the end, it happened that the one with version number 6 was selected.

Q. Not able to configure IPv6 on a WS-SUP32-GE-3B with IP Services Cisco IOS. Does Sup32 supports IPv6?

Switch(config)#ipv6?
% Unrecognized command

A. Sup32 does support IPv6 but on 12.2(33) SXI or later then you can use IP services.

Q. Does the Cisco IPSec VPN Client support IPv6 ?

A.The IPSEC client can only form tunnels between IPv4 endpoints, and will only transport IPv4 packets inside the tunnel.If  you are using something 
that will tunnel IPv6 inside IPv4 (ISATAP,6in4),the IPv6 will be transported but only because it looks like an  IPv4 packet at the driver layer.
The classic Cisco VPN client only carries IPv6 over IPSEC if the IPv6 is tunneled inside IPv4.For native IPv6 transport, you can use
Cisco AnyConnect VPN client.

Q. What is the reason for a dedicated link local address for each VLAN?

A. One of the advantages of IPv6 is the fact that every link has a link  local addresses that are significant only for that link, in addition to  having at least one global address.  The fact that the same link-local  address can appear on multiple different links should be embraced as a  benefit.

The  ability to have many different addresses on an interface is one of the  useful traits of IPv6 that can provide an advantage over IPv4

for Further reading visit - https://supportforums.cisco.com/docs/DOC-16506
to learn about CCNA course visit www.rjpinfotek.com