ip-stories.com

  •  

    September 2010
    M T W T F S S
    « Aug    
     12345
    6789101112
    13141516171819
    20212223242526
    27282930  
  • Web Stat Counter

    • Search This Blog :

    • Add url
    • Add Me on FB

      Rahman Isnaini's Facebook profile
    • Hurricane Electric IPv6 Cert

      IPv6 Certification Badge for risnaini
    • comments

    • Visitors Referred From :

    • Geo Stats

    • Categories

    Archive for the 'Cisco' Category


    [Cisco] Cisco BGP OIDs Version 4

    Posted by admin on 6th August 2010

    OID VIEW Web Information

    ciscoBgp4MIB 1.3.6.1.4.1.9.9.187
    ciscoBgp4NotifyPrefix ciscoBgp4NotifyPrefix 1.3.6.1.4.1.9.9.187.0
    cbgpFsmStateChange cbgpFsmStateChange 1.3.6.1.4.1.9.9.187.0.1
    cbgpBackwardTransition cbgpBackwardTransition 1.3.6.1.4.1.9.9.187.0.2
    cbgpPrefixThresholdExceeded cbgpPrefixThresholdExceeded 1.3.6.1.4.1.9.9.187.0.3
    cbgpPrefixThresholdClear cbgpPrefixThresholdClear 1.3.6.1.4.1.9.9.187.0.4
    ciscoBgp4MIBObjects ciscoBgp4MIBObjects 1.3.6.1.4.1.9.9.187.1
    cbgpRoute cbgpRoute 1.3.6.1.4.1.9.9.187.1.1
    cbgpRouteTable cbgpRouteTable 1.3.6.1.4.1.9.9.187.1.1.1
    cbgpRouteEntry cbgpRouteEntry 1.3.6.1.4.1.9.9.187.1.1.1.1
    cbgpRouteAfi cbgpRouteAfi 1.3.6.1.4.1.9.9.187.1.1.1.1.1
    cbgpRouteMedPresent cbgpRouteMedPresent 1.3.6.1.4.1.9.9.187.1.1.1.1.10
    cbgpRouteMultiExitDisc cbgpRouteMultiExitDisc 1.3.6.1.4.1.9.9.187.1.1.1.1.11
    cbgpRouteLocalPrefPresent cbgpRouteLocalPrefPresent 1.3.6.1.4.1.9.9.187.1.1.1.1.12
    cbgpRouteLocalPref cbgpRouteLocalPref 1.3.6.1.4.1.9.9.187.1.1.1.1.13
    cbgpRouteAtomicAggregate cbgpRouteAtomicAggregate 1.3.6.1.4.1.9.9.187.1.1.1.1.14
    cbgpRouteAggregatorAS cbgpRouteAggregatorAS 1.3.6.1.4.1.9.9.187.1.1.1.1.15
    cbgpRouteAggregatorAddrType cbgpRouteAggregatorAddrType 1.3.6.1.4.1.9.9.187.1.1.1.1.16
    cbgpRouteAggregatorAddr cbgpRouteAggregatorAddr 1.3.6.1.4.1.9.9.187.1.1.1.1.17
    cbgpRouteBest cbgpRouteBest 1.3.6.1.4.1.9.9.187.1.1.1.1.18
    cbgpRouteUnknownAttr cbgpRouteUnknownAttr 1.3.6.1.4.1.9.9.187.1.1.1.1.19
    cbgpRouteSafi cbgpRouteSafi 1.3.6.1.4.1.9.9.187.1.1.1.1.2
    cbgpRoutePeerType cbgpRoutePeerType 1.3.6.1.4.1.9.9.187.1.1.1.1.3
    cbgpRoutePeer cbgpRoutePeer 1.3.6.1.4.1.9.9.187.1.1.1.1.4
    cbgpRouteAddrPrefix cbgpRouteAddrPrefix 1.3.6.1.4.1.9.9.187.1.1.1.1.5
    cbgpRouteAddrPrefixLen cbgpRouteAddrPrefixLen 1.3.6.1.4.1.9.9.187.1.1.1.1.6
    cbgpRouteOrigin cbgpRouteOrigin 1.3.6.1.4.1.9.9.187.1.1.1.1.7
    cbgpRouteASPathSegment cbgpRouteASPathSegment 1.3.6.1.4.1.9.9.187.1.1.1.1.8
    cbgpRouteNextHop cbgpRouteNextHop 1.3.6.1.4.1.9.9.187.1.1.1.1.9
    cbgpPeer cbgpPeer 1.3.6.1.4.1.9.9.187.1.2
    cbgpPeerTable cbgpPeerTable 1.3.6.1.4.1.9.9.187.1.2.1
    cbgpPeerEntry cbgpPeerEntry 1.3.6.1.4.1.9.9.187.1.2.1.1
    cbgpPeerPrefixAccepted cbgpPeerPrefixAccepted 1.3.6.1.4.1.9.9.187.1.2.1.1.1
    cbgpPeerPrefixDenied cbgpPeerPrefixDenied 1.3.6.1.4.1.9.9.187.1.2.1.1.2
    cbgpPeerPrefixLimit cbgpPeerPrefixLimit 1.3.6.1.4.1.9.9.187.1.2.1.1.3
    cbgpPeerPrefixAdvertised cbgpPeerPrefixAdvertised 1.3.6.1.4.1.9.9.187.1.2.1.1.4
    cbgpPeerPrefixSuppressed cbgpPeerPrefixSuppressed 1.3.6.1.4.1.9.9.187.1.2.1.1.5
    cbgpPeerPrefixWithdrawn cbgpPeerPrefixWithdrawn 1.3.6.1.4.1.9.9.187.1.2.1.1.6
    cbgpPeerLastErrorTxt cbgpPeerLastErrorTxt 1.3.6.1.4.1.9.9.187.1.2.1.1.7
    cbgpPeerPrevState cbgpPeerPrevState 1.3.6.1.4.1.9.9.187.1.2.1.1.8
    cbgpPeerCapsTable cbgpPeerCapsTable 1.3.6.1.4.1.9.9.187.1.2.2
    cbgpPeerCapsEntry cbgpPeerCapsEntry 1.3.6.1.4.1.9.9.187.1.2.2.1
    cbgpPeerCapCode cbgpPeerCapCode 1.3.6.1.4.1.9.9.187.1.2.2.1.1
    cbgpPeerCapIndex cbgpPeerCapIndex 1.3.6.1.4.1.9.9.187.1.2.2.1.2
    cbgpPeerCapValue cbgpPeerCapValue 1.3.6.1.4.1.9.9.187.1.2.2.1.3
    cbgpPeerAddrFamilyTable cbgpPeerAddrFamilyTable 1.3.6.1.4.1.9.9.187.1.2.3
    cbgpPeerAddrFamilyEntry cbgpPeerAddrFamilyEntry 1.3.6.1.4.1.9.9.187.1.2.3.1
    cbgpPeerAddrFamilyAfi cbgpPeerAddrFamilyAfi 1.3.6.1.4.1.9.9.187.1.2.3.1.1
    cbgpPeerAddrFamilySafi cbgpPeerAddrFamilySafi 1.3.6.1.4.1.9.9.187.1.2.3.1.2
    cbgpPeerAddrFamilyName cbgpPeerAddrFamilyName 1.3.6.1.4.1.9.9.187.1.2.3.1.3
    cbgpPeerAddrFamilyPrefixTable cbgpPeerAddrFamilyPrefixTable 1.3.6.1.4.1.9.9.187.1.2.4
    cbgpPeerAddrFamilyPrefixEntry cbgpPeerAddrFamilyPrefixEntry 1.3.6.1.4.1.9.9.187.1.2.4.1
    cbgpPeerAcceptedPrefixes cbgpPeerAcceptedPrefixes 1.3.6.1.4.1.9.9.187.1.2.4.1.1
    cbgpPeerDeniedPrefixes cbgpPeerDeniedPrefixes 1.3.6.1.4.1.9.9.187.1.2.4.1.2
    cbgpPeerPrefixAdminLimit cbgpPeerPrefixAdminLimit 1.3.6.1.4.1.9.9.187.1.2.4.1.3
    cbgpPeerPrefixThreshold cbgpPeerPrefixThreshold 1.3.6.1.4.1.9.9.187.1.2.4.1.4
    cbgpPeerPrefixClearThreshold cbgpPeerPrefixClearThreshold 1.3.6.1.4.1.9.9.187.1.2.4.1.5
    cbgpPeerAdvertisedPrefixes cbgpPeerAdvertisedPrefixes 1.3.6.1.4.1.9.9.187.1.2.4.1.6
    cbgpPeerSuppressedPrefixes cbgpPeerSuppressedPrefixes 1.3.6.1.4.1.9.9.187.1.2.4.1.7
    cbgpPeerWithdrawnPrefixes cbgpPeerWithdrawnPrefixes 1.3.6.1.4.1.9.9.187.1.2.4.1.8
    ciscoBgp4NotificationPrefix ciscoBgp4NotificationPrefix 1.3.6.1.4.1.9.9.187.2
    ciscoBgp4MIBConformance ciscoBgp4MIBConformance 1.3.6.1.4.1.9.9.187.3
    ciscoBgp4MIBCompliances ciscoBgp4MIBCompliances 1.3.6.1.4.1.9.9.187.3.1
    ciscoBgp4MIBCompliance ciscoBgp4MIBCompliance 1.3.6.1.4.1.9.9.187.3.1.1
    ciscoBgp4MIBComplianceRev1 ciscoBgp4MIBComplianceRev1 1.3.6.1.4.1.9.9.187.3.1.2
    ciscoBgp4MIBComplianceRev2 ciscoBgp4MIBComplianceRev2 1.3.6.1.4.1.9.9.187.3.1.3
    ciscoBgp4MIBGroups ciscoBgp4MIBGroups 1.3.6.1.4.1.9.9.187.3.2
    ciscoBgp4RouteGroup ciscoBgp4RouteGroup 1.3.6.1.4.1.9.9.187.3.2.1
    ciscoBgp4PeerGroup ciscoBgp4PeerGroup 1.3.6.1.4.1.9.9.187.3.2.2
    ciscoBgp4NotificationsGroup ciscoBgp4NotificationsGroup 1.3.6.1.4.1.9.9.187.3.2.3
    ciscoBgp4PeerGroup1 ciscoBgp4PeerGroup1 1.3.6.1.4.1.9.9.187.3.2.4
    ciscoBgp4NotificationsGroup1 ciscoBgp4NotificationsGroup1 1.3.6.1.4.1.9.9.187.3.2.5

    Posted in BGP, Cisco, MRTG, snmp | No Comments »

    [MRTG] How To Monitor Number of BGP Prefixes from BGP Peer on Cisco Router(s) using MRTG

    Posted by admin on 29th July 2010

    This is my CFG File.

    The complete OID is 1.3.6.1.4.1.9.9.187.1.2.4.1.1.192.168.150.164.1.1
    The OID of Accepted BGP Routes : 1.3.6.1.4.1.9.9.187.1.2.4.1.1
    The OID of Max BGP Routes : 1.3.6.1.4.1.9.9.187.1.2.4.1.3
    [well this not really important as this just to make the mrtg capturing to work, since mrtg MRTG needs to graph two variables/OIDs].
    The IP Address of the BGP Peer being monitored : 192.168.150.164
    The version of IP & Routing Type : 1.1 > IPv4 & Unicast.

    mrtg# vi /export/cfg/bgp-prefix.cfg

    WorkDir: /var/data-mrtg/bgp
    LogFormat: rrdtool
    PathAdd: /usr/local/bin/
    LibAdd: /usr/local/lib/perl5/5.8.8
    Interval: 5
    Refresh: 300
    Forks: 4

    Options[_]: gauge, nopercent, integer
    Unscaled[_]: ymwd
    YLegend[_]: Number of Prefix
    ShortLegend[_]:
    LegendI[_]:   Received Prefixes
    LegendO[_]:   Withdrawn Prefixes
    Legend1[_]: Number of Accepted Prefixes
    Legend2[_]: Withdrawn

    ### as999
    Target[bgp-as999]: 1.3.6.1.4.1.9.9.187.1.2.4.1.1.192.168.150.164.1.1&1.3.6.1.4.1.9.9.187.1.2.4.1.3.192.168.150.164.1.1:public@192.168.150.129
    MaxBytes[bgp-as999]: 1250
    Title[bgp-as999]: BGP Prefixes AS999
    PageTop[bgp-as999]:

    BGP Prefixes AS999

    System: Cisco Gateway
    Equipment: Cisco 3750
    Maintainer: NOC Jakarta

    =================== Options Information ======================
    More information on : MRTG Website

    gauge

    Treat the values gathered from target as ‘current status’ measurements
    and not as ever incrementing counters.
    This would be useful to monitor things like disk space, BGP Prefixes,
    processor load, temperature, and the like …

    integer

    Print summary lines below graph as integers without commas, if you missed this on your option… MRTG would print / plot the value with additional x.000 for example 50 prefixes > 50.000 prefixes.
    nopercent

    Don’t print usage percentages.

    ==================== Router IOS Version =======================

    3750-GW#sh ver
    Cisco IOS Software, 3700 Software (C3725-ADVIPSERVICESK9-M), Version 12.4(3), RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2005 by Cisco Systems, Inc.
    Compiled Fri 22-Jul-05 02:27 by hqluong

    ROM: System Bootstrap, Version 12.2(8r)T2, RELEASE SOFTWARE (fc1)

    3750-GW uptime is 20 weeks, 19 hours, 34 minutes
    System returned to ROM by power-on
    System restarted at 11:04:16 UTC Wed Mar 10 2010
    System image file is “flash:c3725-advipservicesk9-mz.124-3.bin”

    It’s 12.4-3 Version….

    a. rahman isnaini r.sutan

    Posted in Cisco, MRTG, Script | No Comments »

    [Switch] HP Procurve SFP Port Interoperability Problem

    Posted by admin on 26th July 2010

    Connecting HP Procurve with other Switches on Gigabit Port using SFP Module is not an easy one at the first time. Since HP Procurve only work with it’s proprietary SFP Modules.

    I have been trying to use another SFP Modules from different vendors.
    Cisco Switch works with them, but not HP Procurve Switch.
    What we saw on the port as the fact is :

    a. SFP Module plugged in to Cisco SFP Slot : Interface & protocol both are UP (connected)
    b. SFP Module pluggen in to Procurve Slot : no signal / led at all.
    c. HP Procurve SFP Proprietary Module plugged in to Procurve SFP slot, everything is fine :)
    You can now have 1 Gbps Trunk inter different switch vendors.

    My conclusion is that HP Procurve only works with it’s proprietary sfp modules.

    a. rahman isnaini r.sutan

    Posted in Cisco, switch | No Comments »

    [Software] GNS 3 Tips & Tricks

    Posted by admin on 22nd July 2010

    Earning your higher level certifications, practices & hands on are a must.
    And practicing with virtual lab is more/really efficient rather than purchasing hardware.
    GNS 3 [Graphical Network Simulator] is one of the best virtual lab software.

    All you need is just this software and the Cisco IOS Image.
    The memory of the virtual Cisco engine is adjustable to it’s maximum.

    Some Issues (and tips/tricks) at the first time you worked with…

    1. Console not respond immediately after start.
    This text should appear first “Connected to Dynamips VM “MPLSCORE” (ID 4, type c3600) - Console port”
    This sample for Cisco 3640 IOS Image.
    Tips :
    - Wait for a while after the Router Started [it needs to boot the IOS]
    - If still the console not working, try to check your IOS Image location

    2. Error when connecting between Routers with Serial, Ethernet, FastEthernet etc
    Tips/Tricks :
    - Don’t go to console at the first time after starting the router
    - Do right click on your router and configure / add / remove your interfaces
    - If that done, try to connect your routers each other as you need.
    - if that done, try to start all device.
    - Go for console now !.

    3. Cannot Save the start-up config & Once you opened a saved *.net on file tab it always goes to default configuration
    and the config-register is 0×2142.
    Tips/Tricks
    -  After all configuration you have considered to be saved done,
    stop all device by using “Stop Every Devices”  red button .
    - Click file and go to new project.
    - Type your *.net file name [example: lab.net] and check on save nvram also export configuration…
    - Close GNS 3 and try to open your *.net file.
    - Your configuration is now stay as before :)

    a. rahman isnaini r. sutan
    thanks to Gracia Wahab

    Posted in Cisco, software | No Comments »

    [Cisco] Load Balancing & Aggregated Fast Ethernet Ports / TRUNK between Cisco Catalyst 3750 using Port-Channel

    Posted by admin on 15th July 2010

    Without Stack Cable that can accommodate 32 Gbps and no more Gig Ports available.
    Cisco Catalyst 3750 Fast Ethernet Ports can be aggregated to be a trunk and to have n x 100 Mbps capacity.
    “n” is the number of Fast Ethernet, the technology is called Port-Channel.

    If you have existing trunk with Fast Ethernet, here the trick to migrate [configuration applied to both switches] :

    A. Port Channel
    1. Config Port-Channel “x”
    x is what ever number :)
    2. Set Port-Channel to be trunk
    3. Set Port-Channel trunk type

    B. FastEthernet
    1. Config Fast Ethernet as Trunk also Trunk Type.
    2. Config Fast Ethernet to be included in channel-group 1
    Channel-Group 1 associate with Port-Channel 1
    3. Don’t forget the mode channel-group is on [avoiding looping traffic ?]

    If All done both switches,
    C. Migration
    1. Plug the Cross Cable in between ports
    2. Immediately unplug the existing trunk [may be on fast1/0/48 for e.g]
    Both action should be done at the same time, unless the switch stop to work :) nope sure this is a looping symptom or not.
    3. Check the link in between by ping, trace, show interface etc.
    4. If all running good, set you existing trunk to be included on channel-group x also do not forget the trunk encapsulation type.
    5. You’ll now have 3 x 100 Mbps :)
    6. Your traffic is not load shared……

    D. Load Balancing
    1. Config “port-channel load-balance dst-ip” [my choice]
    2. Check the traffic load on trunk ports, it should be shared now.

    Issue : still not balanced dan shared 100% the same volume on each of trunk interface.

    ====================================
    port-channel load-balance dst-ip

    interface Port-channel1
    switchport trunk encapsulation dot1q
    switchport mode trunk

    interface FastEthernet1/0/1
    switchport trunk encapsulation dot1q
    switchport mode trunk
    speed 100
    duplex full
    channel-group 1 mode on
    !
    interface FastEthernet1/0/2
    switchport trunk encapsulation dot1q
    switchport mode trunk
    speed 100
    duplex full
    channel-group 1 mode on
    =====================================

    a. rahman isnaini r.sutan

    Posted in Cisco | No Comments »

    [Trunk] One Switch for Multiple Vlan Trunking

    Posted by admin on 18th May 2010

    Budget Constrain is always improving IT Brains to Turn….
    With only One Shared Switch [Cisco Catalyst] you can have Multiple Trunks from Multiple Routers.

    How it is done ?.
    Let say you have two Routers that needed to be trunked to a Cisco Catalyst.
    No matter what type / brand of your router is, as long as it’s support trunking / sub interface… this multiple vlan trunking should work & of course cisco catalyst needs to support dot1.q trunk protocol [2950T which I'm using].

    This sample, I have used Mikrotik & Zebra OS [Quagga].
    The steps are :

    1. Configure One Port to be Mikrotik Vlan Trunk [Gi 0/1]
    2. Configure One Port to be Zebra OS Vlan Trunk [Gi 0/2]

    Vlans

    1. Define Range of Vlan for Mikrotik [e.g : 0 - 99]
    2. Define Range of Vlan for Zebra/Quagga [e.g : 100 - 199]

    Ports

    1. Define Ports will be used for Mikrotik Vlans [F0/0 - f0/7]
    2. Define Ports will be used for Quagga Vlans [F0/17 - F0/24]

    How to Connect between two Routers Vlan ?.
    Don’t ! :) Unless You Will have a Huge Looping Traffic.
    The purpose of doing this is just for shared a switch with multiple trunks from multiple routers.

    There you go…
    You should be able to ping and reach other.

    a. rahman isnaini r.sutan

    Posted in CentOS, Cisco, Mikrotik, quagga, trunk | No Comments »

    [Cisco] Dialing DSL PPOE Connection from Cisco Router

    Posted by admin on 5th April 2010

    A simple configuration for Dialing DSL Connection using PPOE & CHAP Authentication.
    Please set your username & password accordingly as your provider given.

    ==========================================
    ip subnet-zero
    !
    !
    !
    vpdn enable
    vpdn logging
    vpdn logging local
    !
    vpdn-group 1
    request-dialin
    protocol pppoe
    Read the rest of this entry »

    Posted in Cisco, Dial Up | 1 Comment »

    [Cisco] NBAR for Blocking Blog “http://komiknabimuhammad.blogspot.com ONLY

    Posted by admin on 20th November 2009

    Refer to Above Formal Letter from the Ministry of Communication & Information…. regarding to block “KOMIKNABIMUHAMMAD.BLOGSPOT.COM” not BLOGSPOT.COM or BLOGGER.COM.
    Therefor To have ONLY and ONLY this specific blog being blocked [http://komiknabimuhammad.blogspot.com], without blocking entire of blogspot.com, blogger.com and their following subdomains,
    Here the Cisco NBAR solution to be implemented :

    Cisco NBAR to Block Regular Expression [Regexp]

    All you have to do is adding more regular expressions:

    class-map match-any BLOCK-URL
    match protocol http url “*komiknabimuhammad*”
    match protocol http url “*komikmuhammad*”
    match protocol http url “*komik*muhammad*”
    match protocol http url “*Azl.jpg*”
    match protocol http host “*faithfreedom*”
    match protocol http url “*AlAzl2.jpg*”
    match protocol http url “*AlAzl3.jpg*”

    This will block all web site that having/containing information regarding words:

    - Komik Muhammad
    - KomikMuhammad
    - KomikNabiMuhammad

    But not :

    - Komik Nabi
    - Komik
    - Nabi
    - Muhammad.

    rgs
    a. rahman isnaini r.sutan
    Thanks Cisco System

    Posted in Cisco, Web, security, technologies | 1 Comment »

    [Failover] Layer2 [STP] vs Layer3 [OSPF] Redundancy Concept ?

    Posted by admin on 4th February 2009

    Metro Ethernet is a fastest growing internet fundamental backbone technology over Metropolitan Areas to reach even End Customers.
    This crucial, high capacity & reliable backbone should be built over a ring to at least to have a fully redundancy purpose.
    The technology has been offered so far by Vendors :

    - Cisco System
    Use REP [Resilient Ethernet Protocol] with 50 ms failover protection.
    Use RSTP [Rapid Spanning Tree Protocol] with 2 seconds failover protection
    Use STP [Spanning Tree Protocol with over than 40 seconds failover protection

    - Nortel Network & Adtran
    Use R [Rapid] & RPR [Resilient Packet Ring] with 50 ms failover protection.

    - Extreme Network
    Use EAPS [Ethernet Automatic Protection Switching] with 50 ms failover protection.

    And so on..
    If you are facing to choose : Layer 2 Redundancy with STP only supported in your switch compared to Layer 3 Redundancy Routing Protocol using OSPF, I suggest to implement OSPF.
    As OSPF will recover the link much faster compared to old fashioned STP.

    a. rahman isnaini r.sutan

    Posted in Cisco, Failover | No Comments »

    [Cisco] Replicate / Mirror All Traffic in Cisco Catalyst Port

    Posted by admin on 28th January 2009

    Last week, EVA [Email Vulnerability Assessment] appliance installed in my network.
    This Real Mail product function as Reporting Engine for Effectiveness of an Antivirus & AntiSpam Server.
    Works by replicating/mirroring all mail traffic towards in & out to/from Antivirus & AntiSpam Server.
    So, this is a very safe way to do the monitoring job without cutting off production mail flow.
    It’s just received the copy of traffic.

    We have been working with this mirroring process couple times ago that replicates all traffic to one port.
    And captured by Source Fire Engine which will be used as log source, destination & protocol to generate a security purpose record.

    Replicating / Mirroring Process done by Cisco Catalyst.
    Impact is your catalyst resources should raise up in usage.
    Here the config how to replicate your traffic :

    a. Catalyst with IOS
    conf t#
    (conf)#int f0/1
    (conf-if)#port monitor f0/5

    Note : Port f0/1 & f0/5 is in the same VLAN.
    Port f0/1 attached to Monitoring-Engine / Sniffer
    Port f0/5 attached to real Engine
    You can add more port to monitor as long as in one VLAN.

    Or

    monitor session 5 source interface Fa0/5
    monitor session 5 destination interface Fa0/1

    b. Catalyst with CatOS
    after enable..
    set span 6/5 6/1
    set span 6/9 6/1
    set span 6/5,6/9 6/1

    Note : Port 6/1 attached to Monitoring-Engine / Sniffer
    Port 6/5 & 6/9 attached to Real Engine

    This mirroring/replicating process can be applied for monitor traffic :

    - from switch to switch
    - from switch to router
    - trunk switch

    a. rahman isnaini r.sutan

    Posted in Cisco | 2 Comments »