Tuesday, 29 December 2015

Apple's iPhones and iPads will work better with Cisco enterprise networks

Apple and Cisco have, through a joint statement, announced a partnership which will see Apple’s apps and devices become more productive in enterprise networks.

The goal of the partnership is to optimize Cisco’s networks for iOS devices and apps and integrate the iPhone with Cisco enterprise environments. That will create a "fast lane" for iOS business users, Apple has said in a press release.

Cisco will provide services specially optimized for iOS devices across mobile, cloud, and on premises-based collaboration tools such as Cisco Spark, Cisco Telepresence and Cisco WebEx.

"iOS is the world’s best mobile platform, and nearly every Fortune 500 and Global 500 company today has put iOS at the centre of their mobile strategy", said Tim Cook, Apple’s CEO. "iPhone and iPad have become essential tools for the modern workforce and are changing the way work gets done. Together with Cisco, we believe we can give businesses the tools to maximize the potential of iOS and help employees become even more productive using the devices they already love".

Apple and Cisco are also working together to make iPhone an even better business collaboration tool in Cisco voice and video environments, with the goal of providing employees with a seamless experience between iPhone and their desk phone.

"Ninety-five percent of companies in the Fortune 500 count on Cisco Collaboration and Cisco networks to help their teams be more productive", said Cisco Executive Chairman John Chambers. "Through this engineering and go-to-market partnership, we’re offering our joint customers the ability to seamlessly extend that awesome Cisco environment to their favorite iOS devices. Together, we’re going to help teams achieve higher levels of productivity and effectiveness".
Certkingdom 20% Discount Promotion Coupon Code: 45K2D47FW4

Thursday, 10 December 2015

210-065 Implementing Cisco Video Network Devices v1.0


QUESTION 1
Refer to the exhibit.



Which configuration item shown in the exhibit should be used to assign the internal and external video communication server address for this group of users?

A. User Settings > Video Address pattern
B. Administrative Tools > User Settings
C. Configuration Template > Edit Template
D. User Import > Configuration

Answer: C


QUESTION 2
Which three features are supported by Cisco TMSPE? (Choose three.)

A. Simplified provisioning
B. LDAP user import
C. Scheduling via Microsoft Outlook
D. FindMe
E. Jabber for Windows
F. Automatic endpoint upgrades

Answer: A,B,D


QUESTION 3
Which four features are provided by Cisco TelePresence Management Suite? (Choose four.)

A. Scheduling of video conference calls
B. Built-in-bridge functionality for multiparty video conferences
C. SIP-H.323 protocol interworking
D. Centralized management of conference resources
E. SMTP email event notification
F. Endpoint configuration backup and restore
G. Cisco TelePresence endpoint automated redundancy
H. Automated resource optimization

Answer: A,D,E,F


QUESTION 4
Management wants to modify Cisco TMS to allow users to configure the call behavior with their associated devices and dial from a single ID. Which feature needs to be enabled and configured?

A. Smart Scheduler
B. Low-touch Provisioning
C. FindMe
D. CMR Provisioning

Answer: C


QUESTION 5
A network engineer wants to automate the monitoring of Cisco TelePresence TX systems. Which step should the engineer take first?

A. Configure Cisco TMS on the codec.
B. Configure Medianet on the codec.
C. Configure NTP on the codec.
D. Configure Multiway on the codec.
E. Configure SNMP on the codec.

Answer: E


Friday, 4 December 2015

Cisco SDN user plans OpenStack integration

Cloud provider merging ACI's network fabric with open source storage and compute framework

At last count, only 15% of the now 2,000 combined customers for Cisco System’s Application Centric Infrastructure (ACI) and VMware’s NSX SDN products were using them in production mode.

One such Cisco customer, cloud provider Key Information Systems of Agoura Hills, CA, is using ACI to provide cloud-enabled data center services to organizations in Southern California. KeyInfo is looking for ACI to provide it with multi-tenancy security, automated application-based network provisioning, and scalability of virtualized and non-virtualized workloads.

Over time, KeyInfo will combine ACI with an OpenStack managed hosting offering to provide an application policy-based networking component to OpenStack’s compute and storage-centric cloud fabric, says Clayton Weise, director of cloud services at KeyInfo. But for now, ACI and Cisco’s Nexus 9000 switches are replacing an aged Catalyst 6500 infrastructure with a higher performance fabric, and setting the foundation for new network-as-a-service offerings from the KeyInfo cloud.

“We did some fairly limited deployments of it early on,” Weise said, describing KeyInfo’s current ACI deployment as 12 leaf switches, four spines and three APIC controllers clustered together. “We were using it to replace Cat 6500 chassis. It was a migration in terms of moving the cabling and everything over. The next phase for us is we’re really going to use some of the functionality more heavily in our environment.”

That next phase is a bit more of a transition, Weise says, because KeyInfo also has an existing investment of Cisco Nexus 5000s to be migrated to the Nexus 9000s. It will take a bit more time because KeyInfo has to do a lot more design work to take advantage of more ACI functionality, he says.

After evaluating Cisco ACI, Juniper Networks’ Contrail and Arista Networks’ Software Defined Cloud Networking, KeyInfo selected ACI because of Cisco’s incumbency with the cloud provider, but also to instill some switch-based policy management of a hybrid, multivendor environment of server colocation, virtual infrastructure and legacy IBM AS/400 and AIX systems that need to participate in VXLANs.

“Having that type of encapsulation and de-encapsulation of what they’re doing in the VXLAN, doing that at the switch made a lot more sense for us,” Weise says. “It allowed us to merge those environments without a whole lot of difficulty.”

KeyInfo is also looking at extending the ACI fabric out across its DWDM optical network and into the customer premises. So longer term, ACI will be offered as a service from KeyInfo in addition to supporting the cloud provider’s own infrastructure.

And that service will ostensibly be application policy-based networking integrated with OpenStack’s compute and storage capabilities.

“OpenStack is pretty modular when it comes to compute and storage,” Weise says. “But when it comes to networking it’s a little bit more monolithic. ACI is the direction we’re going to go because it gives us the best flexibility.”

It will also ease implementation of firewalls and other security services that go beyond OpenStack’s “namespaces on a Linux box” security, he says.

“For a lot of our client base, that is totally unacceptable,” Weise says. "Plus, some might have specific reasons for why they want to use Palo Alto Networks (firewalls) or (Cisco) ASA with intrusion protection. That kind of capability doesn’t come easy with the way OpenStack is now so we have to use ACI to add network security-as-a-service on top of the services that are already there.”

Weise says a mix of different technologies will be used in conjunction with OpenStack group-based policy and ACI group-based policy to meet the “stringent requirements” of KeyInfo’s customers.

KeyInfo is not using the OpFlex policy protocol, developed by Cisco, Microsoft, IBM, Citrix and Sungard, to push group-based policies out to the infrastructure, though it is an option, Weise says. Another is middleware from a third-party vendor to do that through ACI API calls, he says.

“We’re trying to stay away from being too much of a middleman” for translating and instantiating policies, Weise says.

The biggest challenge in implementing ACI was leaving the old CLI routines behind when defining, configuring and administering group-based policy, Weise says. The biggest benefit is the automation of configuring end point groups vs. manually touching each device in that group.