I have Nexus 7K installations in 2 locations. Both of them have multiple VDCs. In default VDC there are continous tacacs error message though tacacs is not configured. The requests are from various public IPs where thsi VDC is not exposed to Internet at all. What would be t he cause of it?
%AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication failed for user root from 195.2.219.2 2012 Dec 11 16:25:28 IDC-FBDTB-AMR2-CN7K-01 %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication failed for user nagios from 67.78.206.226 - sshd[25797] 2012 Dec 11 16:25:34 IDC-FBDTB-AMR2-CN7K-01 %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication failed for user nagios from 67.78.206.226 - sshd[25799]
I need to upgrade my core switches at one of our locations (two 7009s with dual sups) from 6.0.1 to 6.1.2. After looking through the release notes it appears that this will be a disruptive upgrade?how long should I expect for the disruption? Are we talking a 7009 boot cycle (10 - 15 minutes) or something longer?How many disruptions can I expect? I suspect 1 per chassis during the failover to the standby but I'd like to validate.Is there any compelling reason to upgrade the EPDL? From what I can see, again from the release notes, this is only necessary with F2 cards if I were to upgrade to Sup2s . I'm in a healthcare environment and this upgrade will be affecting one of our major campuses so the more info I can get to the managers the more accepting they will be for the disruptions.
I need to figure out the max power consumption of 7009. The issue is, at this point i am not sure what modules will be used, so just to give an estimate, how we calculate the max power consumption of nexus 7009 ?
We are migrating from Catalyst 6509 IOS platforms to Nexus 7009. There's the normal differences in commands which is well doucumented. We do have some quite large files containing ACLs varying from 10's of lines to several 1000's of lines. Our normal upload would be done using tftp and then issuing the command 'conf net' on the the 6509. This is no longer the way to do this on NX-OS. I've tried copy ftp: running-config which works fine for small files but for big ones it takes a long time, in some cases I've see it takes 20-30 minutes. The initilal tftp uplaod to the 7009 seems OK but the copy into the running-config is the bit that takes time and initially I thought I'd killed the 7009!! It did finally come back to the prompt. Are the 7009's simply not designed for large ACLs? I did try the configure session (Session Manager) but I couldn't see a way of uploading a file. I tried creating a new session and then exiting it, copying in a file of the same format and then commiting it but it didn't seem to acknowledge the file (checksum?).
I wanted to know that in nexus 7009, can i use mix of F2/M1/M2 series line cards ? will they work with each other ? Lets say i have F2 line card and M2 line card, will servers attached to them will communicate with each other ?
We have Nexus 7009 switch and want to configure the span session
We are using F2 and M2 card both are in seperate differeent VDC.And out server is connected to M2 card on eth 4/6 and want to monitor the traffic from vlan 161Which is made on F2 card.
We are looking to deploy two Nexus 7009 cores at our two datacenters. They are approximately 2 miles apart. We are hoping to have 10G Dark Fiber between the buildings and therefore dedicate a pair for FCOE between the cores using 10G Long Range SFP's. I read that the Nexus 5000 series had a limit of ~3 km for FCOE. Does the same hold true for the 7000 series? I thought I read somehwere that the buffers were larger on the 7000 series and therefore would be able to do ~30 km.
I wanted to know if any has the Nexus 7009 chassis installed into a 600 wide rack with the sides fitted and if they are experiencing heat issues?
My client will be replacing their aging 6509 chassis with 7009 devices, but the physicals dont tally with the install guidelines for the 7009 series chassis. The current install of the 6509s does not tally with the recommended install guidelines for those either, but they have not expereienced any heat issues...
The 7009 will be fitted with 2xSUP2E, 3x48portSFP-F2E cards and 2x10GSFP-M2 cards with 2x6K PSUs. I am genuinely concerned they may cook these devices, but space restrictions look like vetoing the upgrade to 800 wide racks. Likewise moving to 7010 chassis may prove tricky due to existing other installs within the racks limiting vertical space.
We've gotten two Nexus 7009's in and I'm starting to configure them when I found I couldn't add VDCs. I found there was no license installed but the only licenses I found that came with them are "Cisco DCNM for LAN Enterprise Lic for one Nexus 7000 Chassis". So my question is this - do I need to configure a DCNM server to get the license pushed to these two 7009s or should there be another PAK for each chassis that I can register and get my enterprise services?
we've been using IOS for a long time, but are relatively new to NX-OS. We've got a central syslog server that all our devices log to. No matter what we do, we can't get our Nexus switches to log there. Here's my current attempt:
Nexus 7009, NX-OS 6.0(1)
# sh logging server Logging server: enabled {redacted} server severity: debugging server facility: local7 server VRF: default
[code].....
The default VRF is working. I see log entries in the logfile, but nothing arrives at the syslog server. It's not a config issue on the server, because tcpdump shows that no packets arrive from the IP for loopback 0.
Is there any challenge to upgrade core switch 6500 series from Nexus 7009 which runs NxOS, because i have 3750X series switches connected at distribution and access layer in my network topology??
Is there any challenge if we place NxOS in core and IOS in distribution and Access layer??? how we are able to match sh run config in existing 6500 switch to Nexus 7009 NXOS?
I've taken 2 4507's fresh out of the box running CAT4500E-ENTSERVICESK9-MZ.122-53.SG2.BIN which was upgraded from CAT4500E-IPBASEK9-MZ.122-53.SG2.BIN
I'm getting constant %C4K_S2W-4-WRITECALENDARERR: Calendar write operation Failed errors on the console. I was also getting them on the original IOS version.
Anything I've seen say's to ignore them but their very frequent filling up the logs.
There's very little return on google and no bugs to report on Cisco?
Have a small stack of two 3750 routers. Get the following error message every few secounds:
%STACKMGR-4-STACK_LINK_CHANGE: Stack Port 1 Switch 1 has changed to state DOWN %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 1 Switch 1 has changed to state UP
Now I replaced the stacking cables but no joy. It was ok for an hr or so but then the error messages popped up again. Also random links on this stack back to access layer user switches have been going up and down randomly. So I have decided to take the next step and upgrade the IOS.
Although when I try and copy a new IOS I get the following error:
%Error writing flash:/c3750-ipservicesk9-mz.122-55.SE6.bin (No space left on device)
Seems this image is 130MB while the image that is currently on it is 74MB and free space is 54MB. How do I get the image onto the router? If I delete the current image from flash will that cause the router to stop functioning?
Also I noticed there seems to be more than one flash directory. See below:
copy tftp: ? flash1: Copy to flash1: file system flash2: Copy to flash2: file system flash: Copy to flash: file system null: Copy to null: file system nvram: Copy to nvram: file system running-config Update (merge with) current system configuration startup-config Copy to startup configuration system: Copy to system: file system vb: Copy to vb: file system
The current router image seems to be in flash1 and flash 2 also. Could I delete the image from flash1. Upload it there and then boot the router from flash1?
my MSFC2 sent this strange log message. %DATACORRUPTION-SP-1-DATAINCONSISTENCY: copy error, The error message decoder tool says: "NOT FOUND". The level is "alert".
We are running a small network business and as funs of ciscos we own a some of the 4948s.We are facing an issue with couple of them as we get the below error message
C4K_CHASSIS-3-INSUFFICIENTPOWERSUPPLIESDETECTED:Insufficient power supplies present for specified configuration
First thought to replace the power supply didn't actually work as we did that with no result.Power consumption is not an issue as well because all other 4948s work fine with 1 power supply (forgot to mention is 1 power supply in all of them).
I recently upgraded my network to have two 3750x core, one interface on the Cisco is connecting to a Net gear switch via a fiber converter. I am keep getting the vlan flapping error message in my log as below.
003396: Sep 17 01:46:16.328: %SW_MATM-4-MACFLAP_NOTIF: Host 5c0e.8ba7.0a5c in vlan 2 is flapping between port Gi2/0/15 and port Gi2/0/13 003397: Sep 17 01:46:19.843: %SW_MATM-4-MACFLAP_NOTIF: Host 5c0e.8ba7.0a5c in vlan 2 is flapping between port Gi2/0/15 and port Gi2/0/13 003400: Sep 17 01:49:58.769: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/17, changed state to down [Code] .....
After my research i think this is a looping issue but I'm unsure how to address it.
I am receiving this error after connecting a copper adapter on a GBIC blade in a 6509. Here are the results from the show Interface. I am waiting to confirm the device on the other side settings but as far as I see I get UP and Up for protocol and line respectively.
GigabitEthernet2/11 is up, line protocol is up (connected) Hardware is C6k 1000Mb 802.3, address is 0009.11e4.f3ce (bia 0009.11e4.f3ce) Description: RCPBSDEV MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set
I encountered problem while trying to copy file from Nexus 5548 to my ftp server (proteus - 192.168.12.220 - the Nexus switch is able to resolve name proteus correctly to 192.168.12.220). See below the working and not working scenarios. I have serached through Cisco Bug Database but unable to find any related bug associated to this problem. This Nexus is running the following NX-OS version.
n5000-uk9-kickstart.5.1.3.N1.1a.bin n5000-uk9.5.1.3.N1.1a.bin Working (without specifying the username and full path)
I have a nexus 7009 that used to work connecting via SSH. However now I cannot connect to it via ssh. It appears the SSH is connects but doing a show users from the console shows nothing connected other than the console connection.
I'm facing a problem regarding loss of ping packets when i do ping test from nexus3k to another nexus3k connected directly.however there is no error counters on the interfaces on both of devices.the ping failutre is occurring only whenever i do ping test with a large number of ping packets.I don't see the ping loss symptom with default ping test (default ping test is 5 packets).
H/W : N3K-C3548P-10G S/W : 5.0(3)A1(1) nexus3k# ping 1.1.1.2 PING 1.1.1.2 (1.1.1.2): 56 data bytes 64 bytes from 1.1.1.2: icmp_seq=0 ttl=254 time=2.732 ms 64 bytes from 1.1.1.2: icmp_seq=0 ttl=254 time=2.732 ms
We are getting some error logs on Nexus VDC,as follows:2012 Nov 23 08:49:11 N7K_B-Network_Center_B %$ VDC-3 %$ last message repeated 6 times 2012 Nov 23 08:50:21 N7K_B-Network_Center_B %$ VDC-3 %$ last message repeated 7 times 2012 Nov 23 08:49:11 N7K_B-Network_Center_B %$ VDC-3 %$ last message repeated 6 times2012 Nov 23 08:50:21 N7K_B-Network_Center_B %$ VDC-3 %$ last message repeated 7 times.
We inserted GLC-T modules and on Nexus 5548 they are showing SFP validation Failed , as per Cisco doc GLC-T is support . Since we have 28 such modules and all after inserting showing same error. please see the below details. I also try configuring speed and inserting modules but no result ..let me know whether my GLC-T module is supported on Nexus 5548
INMUMFDS1SWCORE01# show module Mod Ports Module-Type Model Status --- ----- -------------------------------- ---------------------- ------------ 1 32 O2 32X10GE/Modular Supervisor N5K-C5548P-SUP active * 2 16 O2 16X10GE Ethernet Module N55-M16P ok 3 0 O2 Daughter Card with L3 ASIC N55-D160L3 ok
I have 2 datacenters running same equipement (two Nexu 5596 with FEX).I just took a look at the log just to see if everything is ok and I saw that I have the same error message (a lot of times) at both location :
%SYSMGR-FEX100-5-HEARTBEAT_LOSS: Service "satctrl" heartbeat loss 2 ,max 7,I though it was a problem with my peerklink-keepalive connection but I see the word FEX ....so i'm not sure...
Note that at both locations, my Nexus are connected back to back through the management port using transceivers. So it's a copper cable from the first nexus, going into a transceiver, going to another transceiver in fiber and then back to copper to the other nexus.
We have purchased two new Nexus 3548 switches. According to documenation the Nexus 3K does support vPC. When trying to enable the feature I get this:
nexus(config)# feature vpc Error: vPC feature is not supported nexus(config)#
We are running software version version 5.0(3)A1(1) and it looks like the latest version is 5.0(3)A1(2) so that's not much of a difference.Am I missing something here?
We have Nexus7009 at client network but due to limitation of Nexus switches that they can not be directly integrate Nexus with RSA so client has purchased cisco ACS for the AAA. We are able to do the authentication and authorization via ACS.However clients wants to further integrate the ACS with RSA so that authentication should happen via RSA and authorization should happen ACS. Is that possible ? if yes, how can i configure the ACS ?
We are getting some error logs on Nexus switch 7K.
Loggs: ---------- 2012 Oct 30 22:36:07 SWITCH %CMPPROXY-STANDBY-2-LOG_CMP_UP: Connectivity Management processor(on module 6) is now UP 2012 Oct 30 22:36:40 SWITCH %SYSMGR-2-GSYNC_SNAPSHOT_SRVFAILED: Service "ipqosmgr" on active supervisor failed to sto re its snapshot (error-id 0x40480005). 2012 Oct 30 22:36:40 SWITCH %SYSMGR-2-STANDBY_BOOT_FAILED: Standby supervisor failed to boot up. 2012 Oct 30 22:36:42 SWITCH %PLATFORM-2-MOD_REMOVE: Module 6 removed (Serial number JAF1550ATBR) 2012 Oct 30 22:42:08 SWITCH %BOOTVAR-5-NEIGHBOR_UPDATE_AUTOCOPY: auto-copy supported by neighbor supervisor, starting