Category Archives: Network

1500 MTU NSX-T Ortamında BAŞınıza Nasıl Dert AÇAbilir kİ ?!

Evet, daha önceki makalelerimde belirttiğim, ama böylede çalışıyor dediğim MTU konusunda baltayı taşa nasıl vurmuş olduğumu göstermek istedim.

Güzel güzel ping atabilirkene 1600 – 1500 sadece 100 birimlik bir fark fregmantasyonda nasıl bu kadar derin etki yapabilirdi ki ?

Bunu okuyan networkçü arkadaşlarımın aklından neler geçiyor acaba, hepsinde bin tane MTU problemi hikayesi vardır !

yum update sizlere ömür …

Gördüğünüz gibi “yum update” sırasında network bağlantı hatları alıyorsunuz, metadata dosyalarının index ve checksum dosyasını tutan repomd.xml’i bile indiremiyorum !!

Şimdi gerekli MTU değerini düzeltelim bakalı neler oluyor 😀

Hersey istediğimiz gibi …

NSX-T Edge Node kendi üzerinde enkapsülasyon yaptığı için bağlı olduğu vSwitch’de ilgili VSS veya VDS’de ve üzerinde koştuğu ESXi host’un bağlı olduğu switch port’larda MTU 9000 olarak set edilmeli ki bu tip durumlarla karşılaşılmasın.

VM

Openstack Networking Router , sadece cli !

Islemlere baslamadan once ilgili komutlari calistiracaginiz sunucuda veya client’da ilgili Openstack RC (environment variables) dosyasini ayarlayin ve calistirin. Daha fazla bilgi icin bakiniz Openstack Networking VXLAN , sadece cli!

Amacimiz elimizdeki VXLAN networklerini internete ve/veya birbirleri arasinda eristirebilmek. Openstack’de bu islem icin Network Node‘lar kullaniliyor. Network Node’lari ile Controller Node’lari ayni yerde kosabildikleri gibi birbirlerinden izole sekildede calisabilirler. DVR (Distributed Virtual Router) olmadan once tum trafigin Network Node’lar uzerinden gecmesi gerekiyor idi fakat DVR’dan sonra Computer Node’larda devreye girdi ve trafik artik dagitik bir sekilde islenmeye basladi fakat burada trafigi SNAT ve DNAT olarak ayirmakta fayda var, SNAT trafigi halen Network Node uzerinden, DNAT trafigi ise Compute Node uzerinden ilerlemekte.

Openstack networking router konusurken ayni zamanda linux networking namespaces hakkinda bilgimiz ve ip netns cli komutlarinin kullanimi bizim icin onemli. Linux Networking Namespace bizim tcp/ip stack’inin ayni isletim sistemi uzerinde clone’lanmasi , bu clone’lari domain olarak nitelendirsek , her domain icersinde overlap networkler gibi tamamen birbirinden bagimsiz , loopback interface’ler , ethernet interface’ler , iptables tablolari ve routing tablolari icermekte , ip komutunun netns parametreside bu farkli domainlerdeki/namespace’lerdeki tcp/ip stack’ini yonetmek icin kullandigimiz cli komutu.

Router diyince artik ML2 scope’undan cikmis oluyoruz , yeni scope’umuz L3. Konfigrasyonlarimiz Neutron Server (neutron.conf) ve L3_Agent(l3_agent.ini) uzerinde olacak.

  • Oncelikle /opt/stack/service/neutron-20160722T142043Z/etc/neutron.conf bakalim
    • Dikkat edilmesi gereken konu l3_router plugin’in set edilmis olmasi
    • [DEFAULT]
      service_plugins = neutron.services.l3_router.l3_router_plugin.L3RouterPlugin
    • Eger service_plugin tanimli degil ise Horizon GUI’de my.sa goremeyebilirsiniz
  • Bir sonraki konfigrasyon dosyasi sudo vi /opt/stack/service/neutron-20160722T142043Z/etc/l3_agent.ini
    • Burada iki onemli parametre var biri interface_driver digeri ise external_network_bridge ek olarak agent_mode‘da bizim icin onemli.
    • interface_driver kullandiginiz mechanism_driver ne ise o set edilmis olmali ornegin linux bridge veya OpenvSwitch(OVS)
    • external_network_bridge onemli cunku sisteme disariya dogru cikisin hangi interface’den yapilacagini belirtiyor
    • agent_mode ile DVR kullanip kullanmayacaginizi belirtiyor
  • Cli’da Router yaratmak icin
    • Oncelikle bir halihazirda elimizde Router var mi bakalim ?
      • stack@helion-cp1-c0-m1-mgmt:~$ neutron router-list
    • Simdi yaratalim bir tane, asagidaki ornekte demo projesi icin bu islem yapilmakta
      • stack@helion-cp1-c0-m1-mgmt:~$ neutron router-create Router1_demoprj –tenant-id 68ca3d8aa2294bc1bc606acbb8b9405a
    • Eger silmek isterseniz router-delete paramteresini kullanabilirsiniz.
    • Bir sonraki adima gecmeden once yarattigimiz router’in id‘sini not edelim neutron router-list komutu ile –> d4fe02b8-0cc0-4662-8573-b3b3f783baaf
  • Yukarda belirttigimiz gibi Router hem farkli network’leri birbiri ile konusturmakta hemde internet’e dogru cikislari saglamakta.
    • Once network’ler arasi konusmayi gorelim. Bir onceki Openstack Networking VXLAN , sadece cli! da sadece Demo-WebServers-Network1 (10.10.1.0/24) networku icin instance yaratmistik, bir tanede Demo-DBServers-Network1(10.10.2.0/24) icin yaratalim. Bu kez port yaratmayacagiz , instance yaratilirken otomatik olarak yaratilacak.
      • Asagidaki komutu calistirmadan once ortam degiskeni olan  OS_PROJECT_NAME ‘i guncelelyin
      • stack@helion-cp1-c0-m1-mgmt:~$ nova boot –flavor m1.tiny –image cirros-0.3.3-x86_64 DBServer1 –nic net-id=bb8dd87f-466e-4082-b69b-c6436bb12a18
      • Elimizde iki adet instance var biri WebServer1 10.10.1.6 digeri ise DBServer1 10.10.2.4
      • Ek olarak daha sonra kullanacagimiz ilgili subnet’lerin id’lerini not edelim neutron subnet-list komutu ile
        • dbsubnet –> fcf2a7da-9cda-45f9-9c9b-51750ca6d1bf
        • web-subnet –> fdb33ffc-43d5-415a-a090-fc8ccb37684d
      • Baslamadan once durumu resmeder isek, iki network var , her ikisine birer instance bagli.
        DUNYA/Internet mevcut , birde biraz once yarattigimiz router’imiz . Bir sonraki adimda router’i DB ve WEB subnet’lerine baglayacagiz
        screen-shot-2016-10-17-at-11-43-57
      • stack@helion-cp1-c0-m1-mgmt:~$ neutron router-interface-add d4fe02b8-0cc0-4662-8573-b3b3f783baaf fcf2a7da-9cda-45f9-9c9b-51750ca6d1bf
      • stack@helion-cp1-c0-m1-mgmt:~$ neutron router-interface-add d4fe02b8-0cc0-4662-8573-b3b3f783baaf fdb33ffc-43d5-415a-a090-fc8ccb37684d
      • Yarattiginiz interface/port’lari silmek icin herzaman router-interface-delete komutunu kullanabilirsiniz.
      • Yeni resim asagidaki gibi oldu ,eger Security Group bazinda bir sikinti yok ise DB ile Web sunuculari birbirleri ile konusabilecekler
        screen-shot-2016-10-17-at-12-01-53
      • Ayni goruntuyu cli’danda alabiliriz
        • stack@helion-cp1-c0-m1-mgmt:~$ neutron router-port-list d4fe02b8-0cc0-4662-8573-b3b3f783baaf
    • Neutron Router sadece neutron networkler arasinda degil ayni zamanda instance’larin internet erisimleri icinde kullanilmakta ki buna Openstack’de external network olarak adlandiriliyor. Genelde bu network daha onceden yaratilmistir , eger hangi network’un external network oldugunu bilmiyorsaniz oncelikle neutron net-list yapip neutron net-show komutu ile router:external parametresi True olan network external network olacaktir.
    • Yukardaki eforu harcamaktansa sadece benim floating ip pool’um var mi acaba diyede bakabiliriz , buda bize ilgili external networkleri direkt verecektir.
    • stack@helion-cp1-c0-m1-mgmt:~$ nova floating-ip-pool-list
      • Simdi yukarda yaptigimiz gibi benzer bir islem yapacagiz , sadece bu kez komut biraz degisecek ama yine bizim router_id‘sine , external_network_id‘sine ihtiyac olacak . Ilgili komutu calistirdigimizda external network’den bir ip adresi alacagiz ve bu ip adresi bizim instance’larimiz icin SNAT konfigrasyonu tanimlanmis olacak fakat bunun disinda internet’den instance’larimiza dogru hicbir erisim acilmayacak
      • Router_id –> d4fe02b8-0cc0-4662-8573-b3b3f783baaf
      • External_Network_id –> efb5448d-7593-46f7-90ad-bd33206c2c7b
      • stack@helion-cp1-c0-m1-mgmt:~$ neutron router-gateway-set d4fe02b8-0cc0-4662-8573-b3b3f783baaf efb5448d-7593-46f7-90ad-bd33206c2c7b
      • Yaptiginiz konfigrasyonu geri almak icin her zaman neutron router-gateway-clear parametresini kullanabilirsiniz.
      • Iste , yeni network baglanti semamiz , time to ping google.comscreen-shot-2016-10-17-at-14-47-51
    • Bu islemlerden sonra sira eger disaridan ilgili instance’a erisilmek istenir ise ne olacak konusu var. Burada floating ip denilen bir kavram isin icine giriyor.
      • Floating IP adresi direkt instance‘a atanabildigi gibi bir proje icin yaratilip instance’a atanmaya hazir halde bulundurulabilir.
      • Once sistem uzerinde halihazirda floating ip var mi bakalim
        • stack@helion-cp1-c0-m1-mgmt:~$ neutron floatingip-list
      • Bir tane yaratalim , ext-net bizim enternal network’un adi
        • stack@helion-cp1-c0-m1-mgmt:~$ neutron floatingip-create ext-net
      • Silmek icin floating ip id’sine ihtiyac var , floatingip-list diyerek elde edebilirsiniz
        • stack@helion-cp1-c0-m1-mgmt:~$ neutron floatingip-delete 89ce7905-0fb5-445c-b8b6-f8f5ff45a166
      • Bundan sonra ilgili floating ip adresini ilgili instance’a atamaya geldi sira. Bunun icin ilgili instance’in hangi port’una karsilik gelen id bilgisini kullanacagiz , diyelimki bizim web server’a floating ip atayacagiz. Ilgili sunucu ip adresi 10.10.1.6 idi, once bu ip adresinin atandigi neutron port id_sini bulalim
        • stack@helion-cp1-c0-m1-mgmt:~$ neutron port-list | grep 10.10.1.6
        • –> 9759d23d-7863-497d-88c3-02067af12714
      • Atayacagimiz floating ip adresinin id’sini bulalim.
        • stack@helion-cp1-c0-m1-mgmt:~$ neutron floatingip-list
        • –> 54096c72-64f2-4133-984c-2061d4ba2b5a
      • Birbirlerine baglayalim
        • stack@helion-cp1-c0-m1-mgmt:~$ neutron floatingip-associate 54096c72-64f2-4133-984c-2061d4ba2b5a 9759d23d-7863-497d-88c3-02067af12714
        • Daha sonra eger security group’lardan ilgili izinler mevcut ise ilgili servis icin ilgili erisimler acilmis olacak.
      • Floating ip baglantisini kaldirmak icin neutron floatingip-disassociate

Kolay gelsin

VM

Openstack Networking VXLAN , sadece cli !

Islemlere baslamadan once ilgili komutlari calistiracaginiz sunucuda veya client’da ilgili Openstack RC (environment variables) dosyasini ayarlayin ve calistirin. Asagida bir ornek mevcut , bunun disinda Horizon’a ilgili kimlik bilgileri ile login olup Project –> Compute –> Access & Security tab’indan indirebilirsiniz.

Cli uzerinden islem yapmak icin Openstack-client kurulu olmali , eger kurulu degil ise kullandiginiz ilgili link’den gerekli paketleri kurabilirsiniz.

Ek olarak asagida calistiracaginiz tum komutlarin parametre bilgilerini vermeden once –debug yazarak calistirdiginizda (ornegin nova –debug list , openstack –debug project list) Openstack REST API‘de kesfetmeniz mumkun.

VXLAN icin on bilgiye ihtiyaciniz var ise bu makaleyi inceleyebilirsiniz , VMware/NSX olmus , OpenvSwitch (OVS), Hyper-V/NVGRE olmus cok onemli degil, prensipte birbirlerine yakin calisiyorlar.

Benim icin ;  Read the rest of this entry

Esitliklerle Openstack Networking – Neutron

Instance = VM = sanal makine

OVS = Open vSwitch = VMware vSS gibi

OVS = Tunneling + QoS + Monitoring (Netflow) + Yonetim + Otomizasyon (Openflow ve OVSDB sayesinde)

OpenFlow = SDN Controller ile OpenFlow switch arasindaki iletisim protokol’u

OpenFlow = Network paketinin izleyecegi yolu belirler ve yaratir

OVSDB = OpenFlow gibi oda bir protokol “OVSDB Protocol” = Yonetim ve Konfigrasyondan sorumlu =  OpenFlow a gore daha uzun metrajli islemleri icin mesela tunel , bridge , port , datapath islemleri yaratma/silme/guncelleme = https://tools.ietf.org/html/draft-pfaff-ovsdb-proto-00

Virtual Switch = OVS = L2 Agent = VM’lerin sanal vNIC leri buraya baglaniyor = vSwitch

Router =  L3 Agent = Virtual Router = Fiziksel router’in sanal hali

Floating IP = VM haberdar olmadigi fakat disardan iceriye erismek icin kullanilan IP adresi

Tenant = Musteri/Organizasyon

Tenant Network = Musteri Network’u = 192.168.0.0/24 = Mesela Web Tier, Database Tier gibi

Flat = untagged = herkez ayni networkde

Local = isolated = VM’in kostugu makine uzerinde networking = disari cikis yok

Tenant Network = Flat + Local + VLAN

GRE/VXLAN = Overlay Networks = Tum tenantlar 192.168.0.0/24 kullaniyorlar , tekrar tekrar tekrar = iletisim noktadan noktaya ve tunelleme kullaniliyor

Provider Network = VLAN ve Flat icin kullaniliyor

Flat Provider Network = Instance/VM leri direkt external networklere baglamak icin = Ornegin Openstack l3-agent degilde halihazirdaki fortinet + netscaller gibi cihazlari kullanmak istiyorsaniz

L3 High Availability = VRRP = Virtual Router / Floating IP leri koruma = Her bir musteri/organizasyon Virtual Router’i farkli bir Network Node uzerinde bulunur/dagitilir = Aktif/Pasif virtual router’lar

Network Node = Routing + DHCP + Metadata

Neutron = OpenStack Networking

Compute = HP = Sanal makinelere CPU/RAM

OVS-Agent = Network ve Compute Node’lar uzerinde calisan bir ajan = L2 Agent = OVS Plugin uzerinden kurulacak tunel ve flow bilgisini alir ve OVS’i programlar

External Network = Internet

Security Group = Firewall Kurallari = Compute Instance uzerinde = SG

Set edilmez ise Default Security kurali uygulanir = Iceri giris yok + Disari cikis any

SG LBaaS VIP , virtual router interface ve instance’a uygulanir

LinuxBridge + OVS + NSX + NEC + Ryu destekler SG (Biraz Master Yoda tarzi dusuk )

OVS = Open vSwitch = Bridging Replace = GRE / VXLAN tunelleme destekler

ML2 = Networking Plugin = Core Plugin

ML2 Onemli = Cunku olmasaydi tum saglayicilar tum servisleri IPAM , DB Access , Virtual Network ID bastan yaratmalari gerekecekti

ML2 Network Type = local + GRE + VLAN + VXLAN + Flat

ML2 Mechanics = OVS , Linuxbridge , Arista , Cisco

Neutron Service Plugins = LBaaS+FWaaS+L3 Agent

Nova Networking = OOOOOOOO Nooooooooooo (kullanima kalkti o/belki vardir hala)

Neden Neutron = Yeni ozellikler LBaaS/FWaaS + ML2 + 16 Milyon Network + Overlapping + network namespaces

Network Namespace = Izolasyon = Farkli network instance’lari = Her bir namespace icin farkli iptables/routing ve ethernet arabirimleri

veth pairs = Iki farkli Namespace’i birbirine baglar

L2Population = No BUM trafik 🙂

BUM = Broadcast + Unicast + Multicast

L3 Agent = virtual layer 3 router = L2 Networklere gw servisi = iptables/NAT/Routing

External IP Range = L3 Agent uzerinde otomatik konfigre ediliyor = IP adresleri virtual layer 3 router’lara assign ediliyor

Neutron DHCP Agent = Tenant networklere DHCP servisi verir = dnsmasq

ovsdb-server = Open vSwitch database server = Konfigrasyon ve durum veritabani = JSON RPC Request/Response = /etc/openvswitch/conf.db

durum = L2 learning table + L3 Forward table + ACL + QoS Policy + Netflow/IPFLEX/sFLOW

ovsdb-tool = Open vSwitch database yonetimi = DB yaratma , sorgulama 🙂

ovs-vswitchd = Lokal sunucu uzerindeki OVS switch lerini yonetir ve kontrol eder = Aciliste tum konfigrasyonu db’den okur ve acar = L2 Switching MAC Learning = VLAN = Port Mirroring

ovs-vswitchd = Flow Table

datapath = Verinin akis yolu

hash lookup table = OVS Kernel Module Flow Cache

Fast Path = OVS Kernel uzerinden

Slow Path = OVS vswitchd user space uzerinden

DPDK = Intel userspace’de Fast Path’den hizli islem yapiyor = OVS Kernel replace for Fast Path

Netlink = ovs-vswitchd ile kernel arasindaki iletisim protokolu burada TCP degil Netlink konusuluyor = Unix domain socket benzeri = kernel <-> userspace arasi baglanti

Package Classifier = Paket islenirken hangi OpenFlow kuralinin uygulanacagini belirler

brt-int = Instance vNIC’ler bu bridge a bagli = vswitch

br-tun = Tuneller uzerinden kosan tenant ve dis baglanti trafigi buradan akiyor

br-ex = Dis baglanti icin kullanilan bridge  = Floating IP ler burada = Network Node uzerinde

qvo = openvswitch tarafindaki veth cifti

qvb = bridge tarafindaki veth cifti

qbr = bridge

qr = l3-agent tarafindan yonetilen port , router tarafinda

qg = l3-agent tarafindan yonetilen port, gw tarafi

patch port = uplink port, birden fazla bridge birbirine patch port ile baglanip tek bir bridge olusturuyor

 

Muhtemelen kacirdigim cok sey vardir , onlarda zamanla eklenecektir buraya.

VM

 

 

About FC SAN – Collection

After made some modification in our SAN network i need to describe all

First  about the design(Architectural) point of view very clear explanation from brocade. Actually my design is between mesh and core-edge

About the limitations need to read each FOS version scalability guidelines , this is for version 7.x  (FOS is Fabric OS , Firmware or Operating System of brocade switch) its important because how many switch(domain id) supported per fabric, how many access gateway per fabric, how many node per fabric, number of zone

if you dont know what is Domin, Domain ID, E Port, N Port pls read IBM Redbooks (Chapter 2 and for Domain ID page 405 Principal Switch Selection)

About Brocade Access Gateway read this (1.1.1 Basic Concept, 1.1.2 Port Mapping, 1.2 NPIV_ID Virtualization, 1.3 Benefits, 1.3.4 Cost Reduction , 1.5 Limitations)

Most important question mark in my mind was multiple connection between Brocade Access Gateway to Fabric SWITCH for availability , read section 2.4.1 in same document , i tested and F port to N port mapping are switched and communication is continue without any issue at the fail-over time

About Brocade Access Gateway port mapping use same document or fallow related link

For ag commend reference

For change FC switch to Access Gateway execute commands bellow

First you have to disable switch (this is also needed if you update the licenses on switch too)

Jango-Fett:admin> switchdisable

Disable auth policy

Jango-Fett:admin> authutil –policy -sw off    Warning: Activating the authentication policy requires either DH-CHAP secrets or PKI certificates depending on the protocol selected. Otherwise, ISLs will be segmented during next E-port bring-up. ARE YOU SURE  (yes, y, no, n): [no] y
Auth Policy is set to OFF

Use such commend if you want to sure that you really disabled

Jango-Fett:admin> authutil –show
AUTH TYPE     HASH TYPE     GROUP TYPE ————————————–
fcap,dhchap     sha1,md5     0,1,2,3,4 Switch Authentication Policy: OFF Device Authentication Policy: OFF
Then switch to access gateway mode, switch configs will be deleted and rebooted

Jango-Fett:admin> ag –modeenable
WARNING: Access Gateway mode changes the standard behavior of the switch. Please check Access Gateway Administrator’s Guide before proceeding. Enabling agmode will remove all the configuration data on the switch including zoning configuration, FAWWN configuration and security database. Please backup your configuration using configupload. This operation will reboot the switch.
Do you want to continue? (yes, y, no, n): [no] y
Access Gateway mode was enabled successfully Switch is being rebooted…

Additionally need to know about licensing  because from community i can see many question about ISL , people says ISL need license but actually ISL Trunking need optional license

 

Multiple ISL connection between two fiber switchs without ISL Trunk

Before i posted some different articles for connect multiple switch together, now i will show you the how multiple ISL connection you can do without ISL Trunk
Problem is from Brocade community pages i can not find out right answer or i don’t know answers why not enough helpful for such big company community page 😦

Short explanation , because of FC network is do not have any Ethernet based Spanning Tree kind of issue , you can do easily multiple connection between two switches. My purpose is not load balance or any port saturation , just only have an issue about my E port , for to do this i have to switch the E port or ISL port.

I plugged the second connection between two switches without any interruption and FC switches take care about routing and traffic like below. P0 and P2 are two E ports. This is Dynamic Load Sharing. You can see it with execute “dlsshow” command which show that dls set or not or you can set it with “dlsset” command to enable it. I guess its come default because our switches 1-4 years old and they have it.

A note for you , I’m not completely sure but when i unplug on of E port , i saw some short latency increase on storage site.

Screen Shot 2013-09-10 at 1.09.25 PM

Also a good comments you have to take care about to see the topology and paths

Use “urouteshow” , “topologyshow”

Also when i search something finally i found perfect pdf file which everybody should read it

http://books.sysadmins.su/oldlib/SAN/FCBasics.pdf

Regards
VM

Multicast Ping , Oracle 11g RAC installation Multicast Test and more

 

Perfect multicast testing utility , its omping , install it with yum like ‘yum install omping’

Use the command like bellow, don’t forget after execute this you have to execute same command other site

[root@kahin02-11g ~]# omping kahin02-11g-priv kahin01-11g-priv -vv

 

Utility detected ip address of local server/client,set buffers and waiting for initialization of remote peer

addrfunc.c:438 getaddrinfo for “kahin02-11g-priv” port 4321 ip_ver 0
cli.c:651 new address “kahin02-11g-priv” added to list (position 0)
addrfunc.c:438 getaddrinfo for “kahin01-11g-priv” port 4321 ip_ver 0
cli.c:651 new address “kahin01-11g-priv” added to list (position 1)
cli.c:779 Every address support ipv4
addrfunc.c:555 Found local addr ipv4, addr: 10.79.79.2 as device bond1
addrfunc.c:438 getaddrinfo for “232.43.211.234” port 4321 ip_ver 4
sockfunc.c:571 Send buffer (unicast socket) allocated 262144 bytes
sockfunc.c:577 Receive buffer (unicast socket) allocated 4194304 bytes
sockfunc.c:571 Send buffer (multicast socket) allocated 262144 bytes
sockfunc.c:577 Receive buffer (multicast socket) allocated 4194304 bytes
kahin01-11g-priv : waiting for response msg
msgsend.c:113 Sending init msg to 10.79.79.1
kahin01-11g-priv : waiting for response msg
msgsend.c:113 Sending init msg to 10.79.79.1

And we got a response from other site and swtich multicasting 😀

omping.c:511 Received unicast message from 10.79.79.1 type I (0x49), len 45
msgsend.c:178 Sending response msg to 10.79.79.1
omping.c:511 Received unicast message from 10.79.79.1 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.1
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
kahin01-11g-priv : waiting for response msg
msgsend.c:113 Sending init msg to 10.79.79.1
omping.c:511 Received unicast message from 10.79.79.1 type S (0x53), len 64
kahin01-11g-priv : joined (S,G) = (*, 232.43.211.234), pinging
msgsend.c:145 Sending query msg to 10.79.79.1
omping.c:511 Received unicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : unicast, seq=1, size=69 bytes, dist=0, time=0.354ms
omping.c:511 Received multicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : multicast, seq=1, size=69 bytes, dist=0, time=0.363ms
omping.c:511 Received unicast message from 10.79.79.1 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.1
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.1
omping.c:511 Received unicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : unicast, seq=2, size=69 bytes, dist=0, time=0.345ms
omping.c:511 Received multicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : multicast, seq=2, size=69 bytes, dist=0, time=0.354ms
omping.c:511 Received unicast message from 10.79.79.1 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.1
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.1
omping.c:511 Received unicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : unicast, seq=3, size=69 bytes, dist=0, time=0.318ms
omping.c:511 Received multicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : multicast, seq=3, size=69 bytes, dist=0, time=0.326ms
omping.c:511 Received unicast message from 10.79.79.1 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.1
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.1
omping.c:511 Received unicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : unicast, seq=4, size=69 bytes, dist=0, time=0.357ms
omping.c:511 Received multicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : multicast, seq=4, size=69 bytes, dist=0, time=0.365ms
omping.c:511 Received unicast message from 10.79.79.1 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.1
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.1
omping.c:511 Received unicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : unicast, seq=5, size=69 bytes, dist=0, time=0.355ms
omping.c:511 Received multicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : multicast, seq=5, size=69 bytes, dist=0, time=0.364ms
omping.c:511 Received unicast message from 10.79.79.1 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.1
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.1
omping.c:511 Received unicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : unicast, seq=6, size=69 bytes, dist=0, time=0.362ms
omping.c:511 Received multicast message from 10.79.79.1 type A (0x41), len 69
kahin01-11g-priv : multicast, seq=6, size=69 bytes, dist=0, time=114.891ms
omping.c:511 Received unicast message from 10.79.79.1 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.1
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.1
omping.c:511 Received unicast message from 10.79.79.1 type S (0x53), len 42
omping.c:964 Server doesn’t send us multicast group
omping.c:967 Client was in query state. Put to initial state
kahin01-11g-priv : waiting for response msg
msgsend.c:113 Sending init msg to 10.79.79.1
omping.c:511 Received unicast message from 10.79.79.1 type S (0x53), len 34
omping.c:964 Server doesn’t send us multicast group
omping.c:977 Client was not in query state. Put it to stop state
kahin01-11g-priv : server told us to stop

kahin01-11g-priv : unicast, xmt/rcv/%loss = 6/6/0%, min/avg/max/std-dev = 0.318/0.348/0.362/0.016
kahin01-11g-priv : multicast, xmt/rcv/%loss = 6/6/0%, min/avg/max/std-dev = 0.326/19.444/114.891/46.759
omping.c:187 Moving all clients to stop state and server to finishing state
omping.c:197 Waiting for 3000 ms to inform other nodes about instance exit

 

Below you can see that other server , of course this establishment time you have to execute same command here

 

[root@kahin01-11g ~]# omping kahin02-11g-priv kahin01-11g-priv -vv

addrfunc.c:438 getaddrinfo for “kahin02-11g-priv” port 4321 ip_ver 0
cli.c:651 new address “kahin02-11g-priv” added to list (position 0)
addrfunc.c:438 getaddrinfo for “kahin01-11g-priv” port 4321 ip_ver 0
cli.c:651 new address “kahin01-11g-priv” added to list (position 1)
cli.c:779 Every address support ipv4
addrfunc.c:555 Found local addr ipv4, addr: 10.79.79.1 as device bond1
addrfunc.c:438 getaddrinfo for “232.43.211.234” port 4321 ip_ver 4
sockfunc.c:571 Send buffer (unicast socket) allocated 262144 bytes
sockfunc.c:577 Receive buffer (unicast socket) allocated 4194304 bytes
sockfunc.c:571 Send buffer (multicast socket) allocated 262144 bytes
sockfunc.c:577 Receive buffer (multicast socket) allocated 4194304 bytes
kahin02-11g-priv : waiting for response msg
msgsend.c:113 Sending init msg to 10.79.79.2
omping.c:511 Received unicast message from 10.79.79.2 type S (0x53), len 64
kahin02-11g-priv : joined (S,G) = (*, 232.43.211.234), pinging
msgsend.c:145 Sending query msg to 10.79.79.2
omping.c:511 Received unicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : unicast, seq=1, size=69 bytes, dist=0, time=0.322ms
omping.c:511 Received multicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : multicast, seq=1, size=69 bytes, dist=0, time=0.348ms
omping.c:511 Received unicast message from 10.79.79.2 type I (0x49), len 45
msgsend.c:178 Sending response msg to 10.79.79.2
omping.c:511 Received unicast message from 10.79.79.2 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.2
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.2
omping.c:511 Received unicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : unicast, seq=2, size=69 bytes, dist=0, time=0.352ms
omping.c:511 Received multicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : multicast, seq=2, size=69 bytes, dist=0, time=0.361ms
omping.c:511 Received unicast message from 10.79.79.2 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.2
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.2
omping.c:511 Received unicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : unicast, seq=3, size=69 bytes, dist=0, time=0.366ms
omping.c:511 Received multicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : multicast, seq=3, size=69 bytes, dist=0, time=0.375ms
omping.c:511 Received unicast message from 10.79.79.2 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.2
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.2
omping.c:511 Received unicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : unicast, seq=4, size=69 bytes, dist=0, time=0.368ms
omping.c:511 Received multicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : multicast, seq=4, size=69 bytes, dist=0, time=0.377ms
omping.c:511 Received unicast message from 10.79.79.2 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.2
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.2
omping.c:511 Received unicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : unicast, seq=5, size=69 bytes, dist=0, time=0.335ms
omping.c:511 Received multicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : multicast, seq=5, size=69 bytes, dist=0, time=0.343ms
omping.c:511 Received unicast message from 10.79.79.2 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.2
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.2
omping.c:511 Received unicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : unicast, seq=6, size=69 bytes, dist=0, time=0.338ms
omping.c:511 Received multicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : multicast, seq=6, size=69 bytes, dist=0, time=0.347ms
omping.c:511 Received unicast message from 10.79.79.2 type Q (0x51), len 84
msgsend.c:67 Sending unicast answer msg to 10.79.79.2
msgsend.c:82 Sending multicast answer msg to 232.43.211.234
msgsend.c:145 Sending query msg to 10.79.79.2
omping.c:511 Received unicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : unicast, seq=7, size=69 bytes, dist=0, time=0.304ms
omping.c:511 Received multicast message from 10.79.79.2 type A (0x41), len 69
kahin02-11g-priv : multicast, seq=7, size=69 bytes, dist=0, time=0.313ms
^C
kahin02-11g-priv : unicast, xmt/rcv/%loss = 7/7/0%, min/avg/max/std-dev = 0.304/0.341/0.368/0.023
kahin02-11g-priv : multicast, xmt/rcv/%loss = 7/7/0%, min/avg/max/std-dev = 0.313/0.352/0.377/0.022
omping.c:187 Moving all clients to stop state and server to finishing state
omping.c:197 Waiting for 3000 ms to inform other nodes about instance exit
omping.c:511 Received unicast message from 10.79.79.2 type Q (0x51), len 84
omping.c:855 Server is not in answer state
msgsend.c:178 Sending response msg to 10.79.79.2
omping.c:511 Received unicast message from 10.79.79.2 type I (0x49), len 45
omping.c:785 We are in finishing state. Sending request to stop.
msgsend.c:178 Sending response msg to 10.79.79.2

 

VM

FC Brocades / IBM Branded Brocades / EMC Branded Brocades ISL Connection

i accept that you are adding new fc switch to fabric, this document do not related with merge something

Be sure no configuration on new switch, if it has then clear it

Savage_Opress:FID128:admin> cfgshow

Defined configuration:

no configuration defined

Effective configuration:

no configuration in effect

You do not have to deal with DomainID, default every switch have DomainID 1 and when you join the new switch to new existing fabric need to be restart because need to be election if without reboot you connect two fc switch via ISL link, you will get incompatible …

Savage_Opress:FID128:admin> islshow

1:  0->    (incompatible)

Try to reboot new switch you will see that it will join to new fabric like below (to reboot fc switch type “reboot” to go )

Savage_Opress:FID128:admin> islshow  1:  0->  4 10:00:00:05:33:55:ef:af   2 Chewbacca       sp:  8.000G bw:  8.000G

Chewbacca:admin> islshow
1: 0-> 3 10:00:00:05:1e:d6:5c:19 1 R2D2 sp: 8.000G bw: 8.000G
2: 4-> 0 10:00:00:05:33:ab:b9:95 3 Savage_Opress sp: 8.000G bw: 8.000G

Now this configuration is cascade base installation , Chewbacca connected to R2D2 , Savage connected to Chewbacca , if you want you can connect Savage to R2D2 for ring topology

Also maybe you have a question on your mind, domain name is not important on this configuration.

VM

FC Brocades / IBM Branded Brocades / EMC Branded Brocades FOS Upgrade

Go …

Download related FOS and out it on any FTP server or you can use SCP too ! File Name section you can see that i indicated folder no any file just folder where all files inside. IBM redirect to special website of Brocade to download, on EMC powerlink you can download it too !

if you ask me what is the big issue of purchase branded fc switch , answer is very easy EMC say aaaa this is IBM branded ask they, IBM yes this is EMC one problem should be there 😀 very funny isn’t it because they are selling same product

Pls do not ask me something about firmwares because most hard thing is this

Savage_Opress:FID128:admin> firmwaredownload
Server Name or IP Address: xxx.yyy.ttt.zzz
User Name: iso
File Name: /FOS/v7.0.1
Network Protocol(1-auto-select, 2-FTP, 3-SCP, 4-SFTP) [1]: 2
Password:
Server IP: 212.58.13.11, Protocol IPv4
Checking system settings for firmwaredownload…
System settings check passed.

You can run firmwaredownloadstatus to get the status
of this command.

This command will cause a warm/non-disruptive boot but will
require that existing telnet, secure telnet or SSH sessions
be restarted.
Do you want to continue (Y/N) [Y]:
Firmware is being downloaded to the switch. This step may take up to 30 minutes.
Preparing for firmwaredownload…
Start to install packages…
dir ##################################################
ldconfig ##################################################
glibc ##################################################

You can see that linux running on it, lovely. Hey Windows lovers waiting someday fc switches run on Windows maybe on 2199 when its more powerful or more fit or whatever  🙂 .. Go …

All packages have been downloaded successfully.
Firmware has been downloaded to the secondary partition of the switch.
HA Rebooting …

Now, reconnect switch and execute

Darth_Maul:FID128:admin> version
Kernel: 2.6.14.2
Fabric OS: v7.0.1
Made on: Thu Dec 15 00:10:22 2011
Flash: Mon Jul 2 18:56:16 2012
BootProm: 1.0.9

perfect !

FC Brocades / IBM Branded Brocades / EMC Branded Brocades First Time Installation

quick as possible

Connect console cable (sorry i don’t like EZSetup) 9600,n,8,1 Flow is none

Default user is admin and password is password 🙂

Pls do not forget i don’t know which terminal you will use like  Putty / SecureCRT or bla bla don’t backspace something such terminals can understand different sometimes and you can not logon or something will be wrong

Brocade will ask you 4 users pass which are root,factory,admin,user

then, continue hope ip address are ready to go , pls type like below

ipaddrset

Darth_Maul:FID128:admin> ipaddrset
Ethernet IP Address [192.168.21.9]:
Ethernet Subnetmask [255.255.255.0]:
Gateway IP Address [192.168.21.1]:
DHCP [Off]:

Not: Type your one, i already did it

Connent GUI like http://ip.address.of.yourdevice

Click Switch Admin –> 

  • Change the name of switch
  • Set DNS Address
  • Set Domian Name
Apply it !

Click Licenses –>

it should be empty or just only default/embedded ones should be

Now my switch is IBM one and i need to go web site http://www-912.ibm.com/LicenseRequestClient/
Not: Other vendors should have their own one, ask to they 

On terminal type like below to get License ID

Darth_Maul:FID128:admin> licenseidshow
10:00:00:05:33:d2:81:1d

Type your email address and all transaction key step by step with license ID to get Activation keys

Back to GUI again , on license section and enter license keys , then grey sections of switch become more beautiful to you 😀

After add license execute such commands

Darth_Maul:FID128:admin> switchdisable
Darth_Maul:FID128:admin> switchenable

Now its beautiful ..

VM