AP Manager interface and Virtual Interface

What do each of these interfaces do on the 526 WMAC? I am not sure I understand the functionality and did not find the answer to this in the documentation.
Thanks

Well from a WLC, the management is used to access and manage the wlc. It is also used for communication with the mobility group. AP-Manager is the interface the wlc and the ap's use and the virtual interface is used by internal dhcp, mobility group, webauth, etc. The virtual interface is not routable in your network, it is mainly used by the wlc's for various features.
Here is from a Cisco Doc:
The management interface is the default interface for in-band management of the controller and connectivity to enterprise services such as AAA server. If the service port is in use, the management interface must be on a different subnet than the service port.
The AP-Manager interface is used as the source IP address for all Layer 3 communications between the controller and the lightweight access points. The AP-Manager must have a unique IP address and should be on the same subnet as the management interface.
The virtual gateway interface is used to support mobility management, DHCP relay, and embedded Layer 3 security, like guest web authentication and VPN termination. The virtual interface must be configured with an unassigned and unused gateway IP address. If multiple controllers are configured in a mobility group, the virtual interface must be the same on all controllers for seamless roaming.
The service-port interface is mapped only to the physical service port. The service port interface must have an IP address on a different subnet from the management and AP-Manager interfaces. A default-gateway cannot be assigned to the service-port interface, but static routes can be defined through the controller command-line interface for remote network access to the service port.

Similar Messages

BadRequest: Virtual machines with secondary network interfaces and virtual machines with no secondary network

I'm trying to create an "ExtraLarge" VM with multiple NICs. The New-AzureVM returns the following error:
BadRequest: Virtual machines with secondary network interfaces and virtual machines with no secondary network
interfaces are not supported in the same deployment, also a virtual machine having no secondary network interfaces
cannot be updated to have secondary network interfaces and vice-versa.
But I have no other VMs. Or at least I did and then deleted them and all their disks. The service has no deployments (either staging or production).
Why is New-AzureVM complaining about a mismatch of VMs with and without secondary network interfaces when no other VMs exist?
I have tried many things to fix this, including the deletion of ALL of my resources. I have deleted and created the service many times, both with an affinity group and without. I have a screen print of the -debug output if your interested.
Thanks for the outstanding help.

Hi Ron,
IMPORTANT NOTE: Please do not post the CONFIDENTIAL DETAILS ever on the public forums, this is HIGH RISK action.
Please send an email with your contact details to my email
[email protected] so that I guide you on steps which help you come out of the current scenario. Thank you for understanding.
I suggest you to create a new VNET and new VM with cloud services. Create Multiple NIC VM. Let us know the results.
Ref:
http://azure.microsoft.com/blog/2014/10/30/multiple-vm-nics-and-network-virtual-appliances-in-azure/
http://blogs.technet.com/b/canitpro/archive/2014/11/04/step-by-step-create-a-vm-with-multiple-nics-in-azure.aspx
If you are unable to create a VM with multiple NIC, please open a support case as it requires more confidential information which is out of scope of FORUM support offerings.
Regards,
Girish

The difference between IEEE802.1Q Native VLAN sub-interface and Physical interface?

Hello
I think the following topologies are supported for Cisco Routers
And the Physical interface also can be using as Native VLAN interface right?
Topology 1.
R1 Gi0.1 ------ IEEE802.1Q Tunneling L2SW ------ Gi0 R2
R1 - configuration
interface GigabitEthernet0.1
encapsulation dot1Q 1 native
ip address 10.0.0.1 255.255.255.0
Topology 2.
R1 Gi0 ------ IEEE802.1Q Tunneling L2SW ------ Gi0 R2
interface GigabitEthernet0
ip address 10.0.0.1 255.255.255.0
And is it ok to use the physical interface and sub-interface with dynamic routing such as EIGRP or OSPF etc?
R1 Gi 0 ---- Point to Multipoint EIGRP or OSPF ---- Gi0 R2 / R3
Gi 0.20--- Point to Point EIGRP or OSPF --- Gi0.10 R4 (same VLAN-ID)
R1 - configuration
interface GigabitEthernet0
ip address 10.0.0.1 255.255.255.0
interface GigabitEthernet8.20
encapsulation dot1Q 20
ip address 20.0.0.1 255.255.255.0
Any information is very appreciated. but if there is any CCO document please let me know.
Thank you very much and regards,
Masanobu Hiyoshi

Hello,
The diagram is helpful.
If I am getting you correctly, you have three routers interconnected by a switch, and you want them to operate in a hub-and-spoke fashion even though the switch is capable of allowing direct communication between any of these routers.
Your first scenario is concerned with all three routers being in the same VLAN, and by using neighbor commands, you force these routers to establish targeted EIGRP adjacencies R1-R2 and R1-R3, with R1 being the hub.
Your second scenario is concerned with creating one VLAN per spoke, having subinterfaces for each spoke VLAN created on R1 as the router, and putting each spoke just in its own VLAN.
Your scenarios are not really concerned with the concept of native VLAN or the way it is configured, to be honest. Whether you use a native VLAN in either of your scenarios, or whether you configure the native VLAN on a subinterface or on the physical interface makes no difference. There is simply no difference to using or not using a native VLAN in any of your scenarios, and there is no difference to the native VLAN configuration being placed on a physical interface or a subinterface. It's as plain as that. Both your scenarios will work.
My personal opinion, though, is that forcing routers on a broadcast multi-access segment such as Ethernet to operate in a hub-and-spoke fashion is somewhat artificial. Why would you want to do this? Both scenarios have drawbacks: in the first scenario, you need to add a neighbor statement for each spoke to the hub, limiting the scalability. In the second scenario, you waste VLANs and IP subnets if there are many spokes. The primary question is, though: why would you want an Ethernet segment to operate as a hub-and-spoke network? Sure, these things are done but they are motivated by specific needs so I would like to know if you have any.
Even if you needed your network to operate in a hub-and-spoke mode, there are more efficient means of achieving that: Cisco switches support so-called protected ports that are prevented from talking to each other. By configuring the switch ports to spokes as protected, you will prevent the spokes from seeing each other. You would not need, then, to configure static neighbors in EIGRP, or to waste VLANs for individual spokes. What you would need to do would be deactivating the split horizon on R1's interface, and using the ip next-hop-self eigrp command on R1 to tweak the next hop information to point to R1 so that the spokes do not attempt to route packets to each other directly but rather route them over R1.
I do not believe I have seen any special CCO documents regarding the use of physical interfaces or subinterfaces for native VLAN or for your scenarios.
Best regards,
Peter

Difference between abstract interface and normal interface

Hello Friends,
What is the Difference between abstract interface and normal interface?....

What is the Difference between abstract interface and
normal interface?....The difference is that you didn't follow convention in the first case. All interfaces are implicitly abstract so you don't have to declare them as such.

Difference between PI/XI interface and ABAP interface

Hello Experts,
We are in the process of identifying interfaces for our current client. I am looking for some documentation or any specific information that will help me to differentiate between SAP PI interface and ABAP Interface. Basically I want to know what are the advantages of PI interface over ABAP interface. What is better? and why?
Any information would be of great help. Thanks.

PI (versus point to point ABAP) advantages are:
1)     Centralized control over data security
2)     More effective (centralized) interface failure monitoring and resolution
3)     Elimination of redundant development and maintenance costs

Could I configure local switching between sub-interface and global interface on ASR9k?

Could I configure local switching between sub-interface and global interface on ASR9k?

For 2 interfaces it is probably best to use an xconnect. It is faster and saves system resources (eg mac learning doesnt apply to xconnect).
Config example:
l2vpn
xconnect group link
p2p link
interface Bundle-Ether100.4321
interface Bundle-Ether500.4321
EFP config:
interface Bundle-Ether100.4321 l2transport
encapsulation dot1q 4000
rewrite ingress tag pop 1 symmetric
interface Bundle-Ether500.4321 l2transport
encapsulation dot1q 2000
rewrite ingress tag pop 1 symmetric
This example shows that you can link 2 EFP's with different vlan's together if you'd pop the tags.
If the EFP's are of the same vlan, then popping the tag can be done but not a must. In general it is recommended to always pop vlan tags so there is a standard EFP design, but not for any technical reasons.
When you use a bridge domain and using a BVI, you MUST pop the tags as the BVI has no notion of a vlan tag and wants to see "plain ethernet".
regards
xander

Global load balancing/active active vip and virtual interface redundancy

Is there a way to configure both of these technologies without exposing the external addressing to the internal network? I have active active within the data center and would like to have active/active across two data centers but I don't see any way to use internal addressing for my content rules and still use them for dns unless I can specify records without using content rules. Thanks.
http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_configuration_example09186a008009438a.shtml
http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_configuration_guide_chapter09186a0080157898.html

Hi Victor,
In response to your questions regarding doing Active/Active GSLB using VIP and interface redundancy.
Rule Based GSLB will not work with VIP/Interface
redundancy.
The reason is because the CSS can not set up an app session to a redundant
interface, it needs to set the app session up to a real interface. Thus, a
full mess topology must be used for GSLB and vip/interface redudancy.
Bug ID CSddw27861 reported this problem and engineering added the command
"ap-kal-vip" to support a full mess topology. This command can only be used
under zone based GSLB and not rule based.
The syntax for the command would be:
dns-record a www.work.com 5.5.5.5 0 single kal-ap-vip 1.1.1.1
rule/ACL based GSLB with vip/int redundancy will not work.
Regards,
Mark

PI 7.1 Sender Interface and Receiver Interface gets interchanged

Hi All,
I m facing a strange problem in PI 7.1
For many of my scenarios, the Sender Interface, sender namespace and receiver Interface, receiver namespace information gets interchanged and displayed incorrectly.
But sometimes its working fine.
When we analysed the Log messages, found that, after xml validation step, the sender and reciever interface gets interchanged.
Any idea why this happens?
How to rectify this error?

Aarthi,
Please check your message interfaces once again. Sender is outbound and Receiver is inbound.
Also please check your receiver determination.
Regards,
---Satish

Differences between Convensional interfaces and XI interfaces

Differences between Convensional interfaces and XI interfaces

hi,
wat do u mean my "Convensional interfaces"?
let me know.
kvr

Dialler interface and Isdn interface

Can someone tell me the difference
When bringing up an isdn interface, Am I correct in saying it has to raise the line by calling the isdn number, If so whats the difference between this and a dialler interface ?
thanks
Carl

Hi Carl,
A dialer interface is a parent interface that holds central protocol characteristics for ISDN D channels, which are part of specified dialer rotary groups. Data packets are delivered to dialer interfaces, which in turn initiate dialing for inbound calls. In most cases, D channels get their core protocol intelligence from dialer interfaces.
A dialer interface is user configurable and linked to individual B channels (such as S0:0, S0:1, S0:2), where it delivers data packets to their physical destinations. Dialer interfaces seize physical interfaces to cause packet delivery.
ISDN BRI delivers a total bandwidth of a 144-kbps via three separate channels. Two of the channels, called B (Bearer) channels, operate at 64 kbps and are used to carry voice, video, or data traffic. The third channel, the D (Data) channel, is a 16-kbps signaling channel used to carry instructions which tells the telephone network how to handle each of the B channels. ISDN BRI is often referred to as "2 B+D."
A D channel notifies the central office switch to send the incoming call to particular timeslots on the router. Each one of the bearer or B channels carries data or voice. The D channel carries signaling for the B channels. The D channel also identifies if the call is a digital call or analog call. Analog calls are decoded and then get sent off to the modems. Digital calls are directly relayed off to the ISDN processor in the router.
HTH,
-amit singh

EtherChannel configuration between Copper interface and fiber Interface

Hi,
Need to check if Giga Etherchannel can be configured between Copper 10/100/1000BaseT and SFP 1000BaseT between two blades on a Cat 6506 with either Sup 720 or Sup32.

I have configured etherchannel between two 3560G 48 port switches. Using a combination of 2 sx fiber and 2 1000tx copper interfaces. The resulting layer 2 channel supported upto 4gb. The notes from the cisco site indicate the following:
Configure all LAN ports in an EtherChannel to operate at the same speed and in the same duplex mode.
The following link refers to etherchannel for 6500 series switches:
http://www.cisco.com/en/US/customer/products/hw/switches/ps708/products_configuration_guide_chapter09186a008007e6d3.html
This link refers to etherchannel for the 3560 series:
http://www.cisco.com/en/US/customer/products/hw/switches/ps5023/products_configuration_guide_chapter09186a00801cdea1.html

Main Interface and Sub Interface

Hello,
I'm fairly new to ASA firewalls so some help is appreciated. Can anyone explain the point of the below config. I thought that normally when using Vlan's there would be no point on configuring a nameif & security level on the main interface? In this case what would configuring an ACL based NAT exemption on the Trunk interface do to traffic on the sub interfaces?
interface GigabitEthernet1/0
nameif Trunk
security-level 100
no ip address
interface GigabitEthernet1/0.100
vlan 100
nameif VLAN100
security-level 100
ip address 192.168.100.1 255.255.255.0 standby 192.168.100.2
interface GigabitEthernet1/0.101
vlan 101
nameif VLAN101
security-level 90
ip address 192.168.101.1 255.255.255.0 standby 192.168.101.2
interface GigabitEthernet1/0.102
vlan 102
nameif VLAN102
security-level 80
ip address 192.168.102.1 255.255.255.0 standby 192.168.102.2
Thanks Steve

You're right about the main interface.
If you use subinterfaces, you typically do not also want the physical interface to pass traffic, because the physical interface passes untagged packets. Because the physical interface must be enabled for the subinterface to pass traffic, ensure that the physical interface does not pass traffic by leaving out the nameif command. If you want to let the physical interface pass untagged packets, you can configure the nameif command as usual.
http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/intrface.html#wp1044006
Hope that helps

Virtual template interface vs Dialer interface?

Hi all,
I am little confusing about virtual template interface and dialer interface. I understood that both of them are logical interface and will be mapped to physical interface dynamically. What is different? When would I use virtual template interface or dialer interface?
Please suggest too.
Thanks a lot,
Nitass

hi
AFAIK we use virtual template in L2TP scenarios where you will have LAC and LNS .
the configs related to VT comes in LNS which is ur local network server for your remote clients from where the L2 tunnel gets orginated.
And about your dialer interfaces we use them very frequently in most of the situations like where you require to club 2 Physical isdn lines and to make use them as a single pipe or using single isdn line and connect it to 2 different locations using 2 B channels using 2 dialers...
if you need to know more about them would suggest to check out this link which will give fair idea about them..
http://www.cisco.com/en/US/tech/tk801/tsd_technology_support_category_home.html
hope this helps u out..
regds

Remote and Home Interfaces

Why do we need a home interface and remote interface for a ejb.
Must these interfaces be there for each ejb?

Why do we need a home interface and remote interface
for a ejb.The Home interface is like a factory for getting to your beans. The remote interface is what you use to speak "directly" to the bean. It's remote because the bean is usually on a remote server somewhere (not in the same VM as your client code). The same is true for the home interface in terms of it being remote.
The corresponding LocalHome and Local interfaces are for use when the bean in question is not remote.
Must these interfaces be there for each ejb?You need either a Home and Remote or LocalHome and Local interface for all beans except Message Driven Beans.

Motu interface and garageband problem

I've recorded in garageband before using my motu mk3 interface, but I started it up today and it wouldnt work. I have the motu connected through the usb port. I'm getting a signal on the interface, and the interface is appearing in the garageband audio preferences, but when I click on it, there is no sound when I play. The volume meter for the track doesn't move. I made sure the monitor was on, but there was no sound. I turned off/on my interface and no sound, and then I restarted my iMac, but still no sound. I'm not exactly tech savvy, or I would probably have this figured out. Any help?

Well, I've figured it out. All I needed to do was unplug the power cord from the motu, plug it back in and good as new.

AP Manager interface and Virtual Interface

Similar Messages

Maybe you are looking for