CategoryNetworking

Nexus 5500: Changing Unified Ports on expansion module without reload

When you need to only the change the unified ports inside an expansion slot of a Nexus 5500, you do not have to reload the entire switch to activate the unified port changes. You can simply restart only the module like this:

nx5548up-a# config t
nx5548up-a(config)# slot 2
nx5548up-a(config-slot)# port 1-16 type fc
nx5548up-a(config-slot)# end
nx5548up-a# copy run start
nx5548up-a# poweroff module 2
nx5548up-a# no poweroff module 2

Read more

UCS Explained in video

Brad Hedlund‘s blog is one of my favorite sources of excellent UCS (and other general) material. I just found the exceptional UCS videos, which deserved a re-share.


Part 1 – The Physical Architecture of UCS

In this video we take a look at the physical network architecture of Cisco UCS and incorporate the new capability of connecting both blade and rack mount servers to UCS Manager.


Part 2 – Infrastructure Virtualization & Logical Architecture

Here we look at how Cisco UCS virtualizes every significant component of the physical architecture; switches, cables, adapters, and servers. Then we look at how … Read more

IOS Recovery of 3750 switch

I had a corrupted IOS image on a 3750E switch today and feared for a xmodem transfer to eat up my day, until I found that you can copy from TFTP. It’s very well hidden, but still possible. Here’s how:

When the switch has ‘booted’ without a proper IOS, you’ll be in the ‘switch: ‘ command line. In the following example, I will assume that the TFTP server has IP 192.168.0.10 and the switch will use 192.168.0.1.

Connect your TFTP server to the ethernet management port, then follow this sequence:

switch: set IP_ADDR 192.168.0.1/255.255.255.0
switch: set DEFAULT_ROUTER 192.168.0.10
switch: copy
Read more

Enabling IPv6 on a Cisco ME3400

For some reason a Cisco ME3400 doesn’t have both IPv4 and IPv6 routing enabled. Still wondering why, but this is how you enable it:

 

conf t
sdm prefer dual-ipv4-and-ipv6 routing
exit
wr mem
reload
Read more

%CRYPTO-4-PKT_REPLAY_ERR: decrypt: replay check failed connection id=xxx

If your replay window size has not been set to a number that is high enough for the number of packets received, you will receive a system message such as the following:

*Nov 17 19:27:32.279: %CRYPTO-4-PKT_REPLAY_ERR: decrypt: replay check failed connection id=xxx

To prevent this error, you can do following:

rtr(config)# crypto ipsec security-association replay window-size 1024

Read more

© 2024 Lostdomain

Theme by Anders NorénUp ↑