We are going to install a wave-7541-k9 and a wave 294 (CM) in the central site and wave 674 in the remote locations.
I know that´s possible to assign a specific physical interface for management purposes only, but I have some questions.
We thought in this way because we are not able to route the customer´s IP within our management environment and we also don´t want to get our management IP being routed within the customer´s environment.
We own the routers in the locations. The WAAS must optimize/accelerate traffic for 2 routers in each location.
Basically the idea is to use the primary interface for production traffic and also as source for the CM connection.
Then, use the other physical interface available to configure a /30 and connect it directly to one of our CPEs which is gone be the management.
The primary interface is going to be connected to the customer´s switch and we will use WCCP for redirection.
The management interface is going to be connected directly to one of our routers.
The plan is to monitor the equipment via that directly connected link (polling made from our monitoring tools and also as source of the traps).
I want to make sure the IP chosen by CM is the production interface´s IP and not the management one.
Also the CM interfaces must be set in the same way (one for production and one for management).
If there any best practices for that situation, recomendations or anything you guys consider valid, I would appreciate
Hi all,not sure this is the right place to raise my question..if not..beg you pardon.problem: I have to interconnect 2 datacenter with 2 links 10gb each so...10+10physical connection is DWDM (dark fiber) and each datacenter has is own nexus93108 (as ...
Learn about new product capabilities from Cisco product managers in live interactive briefings throughout October. Open to all customers through Cisco’s Customer Connection program.
Join the Cisco Customer Connection program to attend. Membership i...
Description:Fault delegate: A Fabric Node Group (fabricNodeGrp) configuration was not deployed on the fabric node 152 because: Node Not Registered for Node Group Policies Type:Config Cause:configuration-failed Change Set:deplSt:not-register...
<original blog published on cisco @ https://blogs.cisco.com/datacenter/cisco-mds-32g-fibre-channel-fabric-switches-small-doesnt-mean-less >
When we think about fabric switches, we tend to consider low-end hardware. These typically do ...
Cisco Champion Radio · S7|E34 Cisco HyperFlex with iSCSI Helps Consolidate Workloads
IT organizations that get the most out of their technology investments tend to grow faster than their peers. As a result, they are always exploring enhancements to exist...