PoAP message on Nexus switch

Hi,
We are seeing this message continually coming from our new Nexus switch. Is this a problem?
how do we subdue this.
2013 Aug 13 04:05:34 switch %$ VDC-1 %$ %POAP-2-POAP_DHCP_DISCOVER_START: POAP DHCP Discover phase started
2013 Aug 13 04:05:34 switch %$ VDC-1 %$ %POAP-2-POAP_INFO: Abort Power On Auto Provisioning and continue with normal setup ?(yes/no)[n]:
2013 Aug 13 04:05:34 switch %$ VDC-1 %$ %POAP-2-POAP_FAILURE: POAP DHCP discover phase failed
2013 Aug 13 04:05:34 switch %$ VDC-1 %$ %POAP-2-POAP_INFO: Abort Power On Auto Provisioning and continue with normal setup ?(yes/no)[n]:
2013 Aug 13 04:05:39 switch %$ VDC-1 %$ %POAP-2-POAP_DHCP_DISCOVER_START: POAP DHCP Discover phase started
Thanks for all inputs.

Hi,
The message is caused by the Cisco PowerOn Auto Provisioning process. This is a feature that simplifies upgrading software and installing configuration files on new Cisco Nexus switches. This is not a problem assuming the switch has just been installed and has not yet been configured.
To stop the messages you simply press Y and return at the prompt "%POAP-2-POAP_INFO: Abort Power On Auto Provisioning and continue with normal setup ?(yes/no)[n]:"
Regards

Similar Messages

How to show module and SFP information include hardware serial number on Nexus switch?

How to show module and SFP information include hardware serial number on Nexus switch? Thanks.

Hi,
The show inventory command will give you details of the Nexus chassis, power supplies, Supervisor, Fabric, I/O modules (including FEX if you have them) etc. To get the details of the installed SFP/SFP+ then you'll need to use the show interface transceiver command.
Regards

Error message on 4500 switch please help me rectify this issue .

LLog Buffer (4096 bytes):
valid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
4d15h: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 2 times)Packet recei ved with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
4d21h: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 5196 times)Packet re ceived with invalid source MAC address (00:00:00:00:00:00) on port Po1 in vlan 1
5d04h: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 58415 times)Packet r eceived with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vla n 1
5d10h: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 44163 times)Packet r eceived with invalid source MAC address (00:00:00:00:00:00) on port Po1 in vlan 1
5d17h: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 18786 times)Packet r eceived with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vla n 1
5d23h: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 4897 times)Packet re ceived with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
6d06h: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 7 times)Packet recei ved with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
6d14h: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 16 times)Packet rece ived with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
6d22h: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 8 times)Packet recei ved with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w0d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 6 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w0d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 6 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w0d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 27713 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w1d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 89677 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w1d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 38722 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w1d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 7 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w1d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 22133 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w2d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 46596 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w2d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 11 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w2d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 10 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w2d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 26497 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Po1 in vlan 1
1w3d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 61085 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w3d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 5 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Gi2/1 in vlan 1
1w3d: %C4K_L2MAN-6-INVALIDSOURCEADDRESSPACKET: (Suppressed 11 times)Packet received with invalid source MAC address (00:00:00:00:00:00) on port Po2 in vlan 1
1w3d: %C4K_REDUNDANCY-5-CONFIGSYNC: The private-config has been successfully synchronized to the standby supervisor
1w3d: %C4K_REDUNDANCY-5-CONFIGSYNC: The startup-config has been successfully synchronized to the standby supervisor
1w3d: %SYS-5-CONFIG_I:
Please help me with trouble shooting steps and also commands..........

Hi,
Please ask the question in LAN SWITCHING community for speedy response but it looks like a message indicating that Switch is seeing a packet with src mac 00.00.00.00.00.00 which obviously is Invalid. Switch learns the mac from src in the frame and it is wrong. Looks like Mac-spoofing.
Regards,
KANWAL

VPC between server and nexus switches

Hi all,
I would like to ask following question:
We are using virtual portchannels to connect e.g. ESXi-Servers with trunks on two Nexus switches. When the switch "rz2sw1" has gone faulty, we expect that the trunk connections between switch rz2sw2 would still work. That's the reason why they are built. But they didn't as you can see in the screenshot (attaced) former mail.
Do you know what can be problem.. thank you

It appears that the peer-link was down. If the peer-link is down and the keep-alive is still up, the secondary device will shutdown all of it's VPC links to ensure dual active (split brain) is avoided.
On a Nexus 7000, its recommended to use a front panel (data port) for the keep-alive instead of the management port. My assumption would be that you are using the MGMT0 for keep-alive and all front panel ports went off-line. If you use a front panel port for keep-alive and all line cards go off line on the primary, the secondary will take over as expected.

Connecting two Nexus switches with link

Hi,
I would like to connect two nexus switches with a link. Like one c5020 and one c5548p. How do i need to configure the ports at both the switches which will be joined with a fiber cable.
For MDS switches such links becomes E-port and fabric is merged. Not sure what happenes at the Nexus swictches. Any input will be appreciated.
Thanks,

Do you have fc modules in each nexus? If so, they act much like the MDS 9148. All ports should be default auto speed and auto switchport mode. Insert fc-sfp's and a regular multimode fc cable between them. Default mode is fc switch.
If that doesn't work, configure the mode on each port as E.
Once done, the fc switch portion of each nexus will merge.
Dave

ACI-How are the new advancements in ACI helping the drawbacks in nexus switching?

ACI-How are the new advancements in ACI helping the drawbacks in nexus switching?

ACI is a paradigm shift in data centre designs.
According to this solution overview ACI is the next generation of Software Defined Networking:
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/guide-c07-731461.html
Having worked with Nexus switches for a couple of years now I haven't encountered any serious drawbacks with these devices.

Nexus switch for storage

we are currently evaluating solutions for our storage upgrade.
we required 10GbE connection from storage to our servers.
there are 2 proposals that uses nexus switch.
1 uses nexus 5548 while the other one uses 3524.
i understand that 5548 is of a higher grade than the 3524.
i have 7 dell servers that will be connected to the switch using 10GbE NIC.
which nexus switch is more suitable for my environment.
7 servers -> 2 10GbE iSCSI switch -> 1x iSCSI storage(20TB)

Well...you're on a Cisco forum, so we'd be remiss in not recommending Cisco gear.
The Nexus 5548UP is around 17k for the base model without any special layer 3 licenses.
http://www.softchoice.com/catalog/en-us/hubs-switches-cisco-nexus-5548up-switch-managed-N5K-C5548UP-FA-HV7684
If you don't use layer 3 on the Nexus (which I wouldn't), they've got pretty good port density for the cost. NXOS takes little bit of getting used to and, for us, the copper SFPs have been a royal pain in the ass, but otherwise, they're pretty solid devices.

Adapter-fex Supported VICs and Nexus Switches

HI,
I am thinking of using C220M4 in standalone mode. I have been reading about adapter-fex and I am wondering which Cisco VIC supports adapter-fex and which Nexus Switch will support adapter-fex.
I am thinking of using a VIC1225 and Nexus 3000.
Thanks.

I believe that adaptor fex is supported only with Nexus 5k and N2k:
Network Adapter Virtualization Design (Adapter-FEX) with Cisco Nexus 5500 Switches and Cisco Nexus 2232 Fabric Extenders
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/guide_c07-690080.html
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/data_sheet_c78-657397.html

Nexus-switches issues no arp-requests.

Hallo all,
I see a very strange behavior on my two nexus switches.
Both are Nexus 5548 with L3-daughter-cards. Both do l2 and l3-switching, ACL-filtering and other things. Furthermore I have a set of servers connected to both switches in a vPC-setup. All in all I do nothing special.
After reloading the primary switch (vpc-primary, root-bridge for all vlans and hsrp-active with preemption for all SVIs) the switche comes back online and after getting up all links and reconverging everthing the network breaks. After a lot of debugging and curses and connection tries and a few additional gray hairs later I have got it to work by pinging all ip-addresses from the switch that I have previously rebooted.
Later I do some tests to find out what was going wrong. I found out that if I clear the arp-cache I will get the same issue. Pinging from server A in one subnet to server B in another subnet doesn't lead to success, because the switch issues no arp-requests. To make it work just ping server B from the switch and all works fine. The switch does arp, the arp-table is updated and the pings from the server A will reach the server B.
Any ideas?
Regards
Thomas
^^°-°^^

I can post a extraction of the relevant config items.
   - --[ vpc-primary
cfs01# sh run
!Command: show running-config
!Time: Wed Nov 13 08:46:18 2013
version 5.2(1)N1(1b)
cfs eth distribute
vrf context CEPH
vrf context management
ip route 172.31.0.0/20 172.31.8.190
vlan 14
name 172.31.50.0/26_CN/NN/OSDs@DMZ
vlan 4080
name 172.31.48.64/26_NAS.Infrastr@DMZ
spanning-tree vlan 1-129,131-3967,4048-4093 priority 0
udld aggressive
vpc domain 1
role priority 1
peer-keepalive destination 172.31.8.179 source 172.31.8.178
peer-config-check-bypass
delay restore 150
peer-gateway
auto-recovery
ip arp synchronize
interface Vlan14
no shutdown
mtu 9216
description CN/NN/OSDs@DMZ
ip access-group acl-vl14-in in
vrf member CEPH
no ip redirects
ip address 172.31.50.61/26
no ip port-unreachable
hsrp version 2
hsrp 3
    authentication md5 key-string 3-14
    preempt delay minimum 30 reload 60
    priority 255
    ip 172.31.50.62
interface Vlan4080
no shutdown
mtu 9216
description NAS.Infrastr@DMZ
ip access-group acl-vl4080-in in
vrf member CEPH
no ip redirects
ip address 172.31.48.125/26
no ip port-unreachable
hsrp version 2
hsrp 3
    authentication md5 key-string 3-4080
    preempt delay minimum 30 reload 60
    priority 255
    ip 172.31.48.126
interface port-channel7
switchport mode trunk
switchport trunk native vlan 991
spanning-tree port type network
speed 10000
vpc peer-link
interface port-channel100
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14-19,991,4078-4080
speed 10000
vpc 100
interface port-channel102
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14,18,991,1299-1400
speed 10000
vpc 102
interface Ethernet1/1
no cdp enable
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14-19,991,4078-4080
channel-group 100 mode active
interface Ethernet1/3
no cdp enable
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14,18,991,1299-1400
channel-group 102 mode active
interface Ethernet1/29
description cfs02_Eth29
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/30
description cfs02_Eth30
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/31
description cfs02_Eth31
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/32
description cfs02_Eth32
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface mgmt0
description oam01_Gi0/19
ip address 172.31.8.178/26
cfs01#
   - --[ vpc-secondary
cfs02# sh run
!Command: show running-config
!Time: Wed Nov 13 08:46:05 2013
version 5.2(1)N1(1b)
cfs eth distribute
vrf context CEPH
vrf context management
ip route 172.31.0.0/20 172.31.8.190
vlan 14
name 172.31.50.0/26_CN/NN/OSDs@DMZ
vlan 4080
name 172.31.48.64/26_NAS.Infrastr@DMZ
spanning-tree vlan 1-129,131-3967,4048-4093 priority 4096
udld aggressive
vpc domain 1
role priority 2
peer-keepalive destination 172.31.8.178 source 172.31.8.179
peer-config-check-bypass
delay restore 150
peer-gateway
auto-recovery
ip arp synchronize
interface Vlan14
no shutdown
mtu 9216
description CN/NN/OSDs@DMZ
ip access-group acl-vl14-in in
vrf member CEPH
no ip redirects
ip address 172.31.50.60/26
no ip port-unreachable
hsrp version 2
hsrp 3
    authentication md5 key-string 3-14
    priority 254
    ip 172.31.50.62
interface Vlan4080
no shutdown
mtu 9216
description NAS.Infrastr@DMZ
ip access-group acl-vl4080-in in
vrf member CEPH
no ip redirects
ip address 172.31.48.124/26
no ip port-unreachable
hsrp version 2
hsrp 3
    authentication md5 key-string 3-4080
    priority 254
    ip 172.31.48.126
interface port-channel7
switchport mode trunk
switchport trunk native vlan 991
spanning-tree port type network
speed 10000
vpc peer-link
interface port-channel100
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14-19,991,4078-4080
speed 10000
vpc 100
interface port-channel102
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14,18,991,1299-1400
speed 10000
vpc 102
interface Ethernet1/1
no cdp enable
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14-19,991,4078-4080
channel-group 100 mode active
interface Ethernet1/3
no cdp enable
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14,18,991,1299-1400
channel-group 102 mode active
interface Ethernet1/29
description cfs01_Eth29
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/30
description cfs01_Eth30
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/31
description cfs01_Eth31
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/32
description cfs01_Eth32
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface mgmt0
description oam02_Gi0/19
ip address 172.31.8.179/26
cfs02#

New to Nexus switches

Hello,
I am very familiar with Catalyst switches but new to nexus switching.
We have a 7k up and running. 5k and 2k are on order. Once they arrive, how do I join/extend all 3 switches?
How does a 5k or 2k know which fabric or 7k to join?

Sudip -
The 5K will connect into your 7K just like a normal switch with a trunk link. The 2K can be thought of as an external linecard for the 5K. In order to configure the interfaces that you select to integrate the FEX with, you will need to configure them for FEX fabric mode:
N5K(config)# interface eth2/1
N5K(config-if)# switchport mode fex-fabric
Jen

Error Logs on 1000v Nexus Switch

Hi Team,
We are below errors from one of our Nexus 1000v switch.
Please advice me why we are getting this kind of errors.
I can see the operational status is disconnected(Show Svs Connection)
Logs:
2012 Dec 2 22:40:15 NODIPXX-N1KVM11 %VMS-3-CONN_CONNECT_ERR: Connection 'vwdixx-vcsem' failed to connect to the vCenter Serve
r.
2012 Dec 2 22:43:15 NODIPXX-N1KVM11 %VMS-3-CONN_CONNECT_ERR: Connection 'vwdixx-vcsem' failed to connect to the vCenter Serve
r.
2012 Dec 2 22:46:15 NODIPXX-N1KVM11 %VMS-3-CONN_CONNECT_ERR: Connection 'vwdixx-vcsem' failed to connect to the vCenter Serve
r.
2012 Dec 2 22:49:14 NODIPXX-N1KVM11 %VMS-3-CONN_CONNECT_ERR: Connection 'vwdixx-vcsem' failed to connect to the vCenter Serve
r.
2012 Dec 2 22:52:14 NODIPXX-N1KVM11 %VMS-3-CONN_CONNECT_ERR: Connection 'vwdixx-vcsem' failed to connect to the vCenter Serve
r.
show svs connections
connection vwdixx-vcsem:
    ip address: ---------------------
    remote port: 80
    protocol: vmware-vim https
    certificate: default
    datacenter name: -----------------
    admin:
    max-ports: 8192
    DVS uuid: 53 8a 35 50 99 ba e3 cf-5f 5f fc 1c bd 54 50 f9
    config status: Enabled
   operational status: Disconnected
    sync status: -
    version: -
    vc-uuid: -
Regards,
Sen

Hi,
As per request please check the logs below..........
Logs:
NODEPXX-N1KVM11# sh vm
vms      vmware
NODEPXX-N1KVM11# sh vms internal event-history errors
1) Event:E_DEBUG, length:68, at 126416 usecs after Tue Dec 4 23:40:09 2012
    [102] vms_vim_connect_extension(506): connection failed. returning -1
2) Event:E_DEBUG, length:193, at 126411 usecs after Tue Dec 4 23:40:09 2012
    [102] convert_soap_fault_to_err(1762): SOAP 1.1 fault: SOAP-ENV:Client [VMWARE-VIM] Operation could not be completed due t
o connection failure.Connection refused. connect failed in tcp_connect()
3) Event:E_DEBUG, length:68, at 160081 usecs after Tue Dec 4 23:37:09 2012
    [102] vms_vim_connect_extension(506): connection failed. returning -1
4) Event:E_DEBUG, length:193, at 160075 usecs after Tue Dec 4 23:37:09 2012
    [102] convert_soap_fault_to_err(1762): SOAP 1.1 fault: SOAP-ENV:Client [VMWARE-VIM] Operation could not be completed due t
o connection failure.Connection refused. connect failed in tcp_connect()
5) Event:E_DEBUG, length:68, at 194044 usecs after Tue Dec 4 23:34:09 2012
    [102] vms_vim_connect_extension(506): connection failed. returning -1
6) Event:E_DEBUG, length:193, at 194039 usecs after Tue Dec 4 23:34:09 2012
    [102] convert_soap_fault_to_err(1762): SOAP 1.1 fault: SOAP-ENV:Client [VMWARE-VIM] Operation could not be completed due t
o connection failure.Connection refused. connect failed in tcp_connect()
7) Event:E_DEBUG, length:68, at 227797 usecs after Tue Dec 4 23:31:09 2012
    [102] vms_vim_connect_extension(506): connection failed. returning -1
8) Event:E_DEBUG, length:193, at 227791 usecs after Tue Dec 4 23:31:09 2012
    [102] convert_soap_fault_to_err(1762): SOAP 1.1 fault: SOAP-ENV:Client [VMWARE-VIM] Operation could not be completed due t
o connection failure.Connection refused. connect failed in tcp_connect()
9) Event:E_DEBUG, length:68, at 262100 usecs after Tue Dec 4 23:28:09 2012
    [102] vms_vim_connect_extension(506): connection failed. returning -1
10) Event:E_DEBUG, length:193, at 262088 usecs after Tue Dec 4 23:28:09 2012
    [102] convert_soap_fault_to_err(1762): SOAP 1.1 fault: SOAP-ENV:Client [VMWARE-VIM] Operation could not be completed due t
o connection failure.Connection refused. connect failed in tcp_connect()

Enable jumbo frame on Nexus switch

I read following phrase in configuration guide of Nexus 5020
The Cisco Nexus 5000 Series switch is a Layer 2 device. This means it does not fragment frames. As a result,
the switch cannot have two ports in the same Layer 2 domain with different maximum transmission units
(MTUs). A per-physical Ethernet interface MTU is not supported. Instead, the MTU is set according to the
QoS classes. You modify the MTU by setting Class and Policy maps.
When you show the interface settings, a default MTU of 1500 is displayed for physical Ethernet interfaces
and a receive data field size of 2112 is displayed for Fibre Channel interfaces
Has anybody configured jumbo frame with above mentioned way ?

Yes, it looks something like this:
policy-map jumbo
class class-default
mtu 9216
policy-map class-default
class class-default
mtu 9216
system qos
service-policy class-default

Weird syslog format messages with Nexus 1000v

I'm trying out the Nexus 1000v, and have the VEM configured to write logs to my syslog server. The thing is, the messages are in a weird format that my log management tools cannot parse. Here is an example:
<189>: 2012 Oct 21 15:22:40 UTC: %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on unknown_session
I found the documentation rather amusing, where it states "The syslog client functionality is RFC-5424 compliant" - doesn't look like they've even read the RFC! This is closer to the format of the older (but more often found in the wild, RFC3164... though not compliant with that either :/
Anyway, I guess the main issue here is that the hostname of the 1000v is not being added to the logs (it is set in my config). Any ideas how I can fix this?
Thanks!

Hi,
Do you have vCenter install on Win2012 Server? The installation would not continue until you have vCenter installed.
Hardik

NAC Error Message in 4500 Switch

Hi There,
I have a 4507R core Switch running IOS version 12.2(31). I am trying to configure this switch for Clean Access; I have already configured the ACS server but when configuring the switch as a NAD and apply the "ip admission NAC" command on the interface level, I get the following error message:
% This config is not supported on this platform. Try configuring a new rule.
The NAC configuration I entered on the switch is as follows:
Switch(config)=ip access-list extended Interface_ACL
Switch(config-nacl)=permit udp any any eq 21862
Switch(config-nacl)=permit udp any any eq domain
Switch(config-nacl)=permit udp any any eq bootpc
Switch(config-nacl)=permit udp any any eq bootps
Switch(config-nacl)=permit tcp any host (antivirus ip address)
Switch(config)=ip admission name NAC eapoudp
Can somebody clarify to me the meaning of that error message and assist me whether my NAC configuration is alright?
Thanking in advance.
Regards,
Haitham

Hello All,
I just figured out the problem; you need first to configure the following commands before applying the ip admission command:
switchport mode access
switchport access vlan
Thanks to all.
Regards,
Haitham

PBR feature in cisco 3548 nexus switch

Hi All ,
Could you please tell me whether cisco 3548 switch will support PBR ? we do have license of Lan1k9 enterprise license switch. But we are not ableto use the PBR featutre. Any help on this..
Regards,
Vijay.

See table-5 in this link:
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/nx-os/licensing/guide/b_Cisco_NX-OS_Licensing_Guide/b_Cisco_NX-OS_Licensing_Guide_chapter_01.html#fntarg_13
Note 19:
The LAN_BASE_SERVICES_PKG license needs to be installed in order to use the LAN_ENTERPRISE_SERVICES_PKG license.
HTH

PoAP message on Nexus switch

Similar Messages

Maybe you are looking for