Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
When we upgraded APIC controller from 2.2.3 to 3.1 the process stopped after APIC 01 was finished. To proceed we had to download the .iso image to APIC 02 and 03 respectively and then restart the process. Anybody that have seen this? Why?
/Jorgen
Hi,
We are planning to upgrade a centrel Nexus 7k DC VPC installation.
Today:
Redundant SUP-1M1-32XP linecardsFab-1 fabric moules (3)
Two nodes in VPC configuration with NxOS 5.2
New:
Redundant SUP-2EF3-48XP linecardsFab-2 fabric modules (5)NxOS 7....
Hi, Have a new DC solution with Nexus 56128 switches running LAN + Native FC.Storage Arrays shall be connected to the Nexus switches via 8G FCCustomer has Dell blade with Qlogic SAN switches, where existing zoning is done. Today these are connected t...
Hi,We are about to start a project that shall secure an organisations wired network.This organisation has 40k clients and around 250k network attached devices (clients, printers, cams, medical equipment, environmental equipment ...)There are about 30...
Hi,
use a SVI on each side together with a common secondary address.
Example:
SVI 1: Primary IP 10.1.1 2, Secondary IP 10.1.1.1
SVI 2: Primary IP 10.1.1.3, Secondary IP 10.1.1.1
Hi,
For clarification:
I am not going to mix different modules in the same chassi. I upgrade one chassi at a time.
Step 1 - Bring down chassi A and change all modules in chassi A
Step 2 - Bring up chassi A and connect it to chassi B (that has old M1 ...
