EVC .. VPLS .. VS Type 4

Dears
I have few questions regarding EVC and its assiciation with VPLS and would like your assistance please regarding them
https://supportforums.cisco.com/thread/2246221
Many Thanks
Regards
Sherif Ismail

Hi Sandip
Many thanks for your detailed reply
1- The document is great and really helped
For QinQ method 2 (P.11-19), method 2 should be similar to figure 11-10 (P.11-28) however I believe there is a small mistake
For the direction EVC --> switchport
Packet received with C-VLAN 20 (encapsulation should be 20 and not 10) then bridge over brigde-domain 10 and at egress of switchport VLAN equals to that of bridge-domain (S-VLAN) is pushed
For the direction switchport --> EVC
C-VLAN Packets received on switchport trunk will have their outer vlan popped (vlan 20) and then bridged to bridge-domain 10. Packets will reach EFP port with only 1 VLAN (C-VLAN 20) and cause there is no rewrite tag operation
If my analysis is correct, then as mentioned encapsulation should be 20
|||
2- If I understood correctly, behavior seems to look as below
For non EVC IOS VC type 4, incoming VLAN tag is removed and dummy tag 0 is added. On remote side this dummy tag is removed and VLAN configured on interface is added
For EVC & IOS XR VC type 4, dummy tag is added on top of incoming tag so packet is sent with both tags. With pass-through no dummy tag is added
Thanks
Regards
Sherif Ismail

Similar Messages

  • VPLS TLS and EVCS support?

    I have been trying to read the VPLS section on the following page to what versions of VPLS are supported.
    http://www.cisco.com/en/US/products/hw/routers/ps368/products_module_configuration_guide_chapter09186a00801e5c06.html
    I have a few questions:
    1. What flavors of VPLS does Cisco support?
    2. For the config exmaple on that page, is it TLS of EVCS?
    3. Can I attach multiple vlan interfaces to a VFI?
    4. Related to last question, does the packet that enters the VPLS over the core maintain the VLAN header of is it stripped? I'll have more questions about this depedning on the answer I get.
    5. I am seeing conflicting reports in the forum and in the docs about which SUP card I need. What do I need to get my 6509 to work with VPLS?
    Thanks,
    Greg

    1. I apologize. I guess I should have been more clear. I understand which draft Cisco used, it was more around vlan based and port based implementations I've seen on other vendors.
    2. Sorry, I meant in the VPLS section. The section was a bit confusing saying where it kept mentioning the TLS and EVCS. But it never clearly showed which lines make it EVCS and which lines make it TLS. Are you saying that EVCS is actually just a reference to Martini?
    3. Thanks. I guess this means vlan headers are maintained across VPLS.
    4. I think I understand now. Mainly I was trying to see if Cisco's VPLS also did the same type4(vc-type vlan) and type5(vc-type ether) as they did with Martini. From what I iunderstand, Cisco's current VPLS is type4. Correct?
    5. So for VPLS, I need at least a SUP2 MSFC2 with OSM+. For Martini, if I have a SUP720-3BXL, what card can I use to support MPLS core interface? Will a standard GE card work?
    Thanks,
    Greg

  • VPLS, EVC

    Dear All,
    We have network connectivity as in attachment but we could not make it work with the config below could you please help to advise ? Please note that our vpls network is working properly and we suspect the problem with "rewrite".
    Regards, Pok.
    PE01 A#
    interface GigabitEthernet0/0/0
     description TO~MX-PNHCC-AS01~Gi0/10
     mtu 4470
     bandwidth 1000
     no ip address
     negotiation auto
     cdp enable
     service instance 30 ethernet
      encapsulation dot1q 30
      rewrite ingress tag push dot1q 100 symmetric
      bridge-domain 111
     service instance 40 ethernet
      encapsulation dot1q 40
       rewrite ingress tag push dot1q 100 symmetric
      bridge-domain 111
    PE02 A#
    interface GigabitEthernet0/0/1
     description To-MX-PNHKT-CS01-Gi0/1
     mtu 4470
     no ip address
     negotiation auto
     cdp enable
     service instance 30 ethernet
      encapsulation dot1q 100 second-dot1q 30
      rewrite ingress tag pop 1 symmetric
      bridge-domain 111
     service instance 40 ethernet
      encapsulation dot1q 100 second-dot1q 40
      rewrite ingress tag pop 1 symmetric
      bridge-domain 111

    I think you have confused things a bit. 
    So on PE1
    you will add another vlan tag of 100 when traffic ENTERS the interface (Ingress).
    This gets to PE2 (hopefully)
    the process works in reverse. So you would need 
    encapsulation dot1q 30
    rewrite ingress tag push dot1q 100 symmetric
    Traffic will enter the service instance and dot1q tag of 100 will be removed. 

  • Various VPLS Mode

    Hi,
    I would like to know various types or mode of VPLS.
    As per Cisco standerds its: Port mode and VLAN mode.
    Now I would like to know if I can use the PE interface connected to CE as a trunk interface and carry all customer VLAN via that port? Instread of creating multiple subninterfaces of the interface and put them on different instances or VPLS instances?
    Is there any good document, site or blog that shows various VPLS deployment mode along with VPLS redundancy scenarios?
    Thanks,
    Devang

    Hi Devang,
    not sure if you are refrring to vc-types instead.
    However you can use a trunk port for the PE to CE AC
    have a look at
    http://www.cisco.com/en/US/docs/routers/7600/install_config/ES40_config_guide/es40_chap6.html#wp1460517
    Or you can explore the EVC world (if you have the right hw) and have a more flexible approach.
    Riccardo

  • VPLS : VC UP but no data -- ASR9k & 7600 ES+

    Dears
    Would like your assistance please regarding below VPLS setup
    VPLS is between ASR9k & 7600 ES+ card. VC is up but CEs are not able to ping each others
    Lab Topology
    CE <> Te0/1/0/3.55 ASR9K < -- mpls --> 7600 Gi4/2 <> CE
    Any ideas ?
    Note
    ASR9k & 7600 are directly connected via same ES+ card
    ||||||||||||||||||||||||||||||||||||||||||||||||||
    ASR9k
    interface TenGigE0/1/0/3
    cdp
    interface TenGigE0/1/0/3.55 l2transport
    encapsulation dot1q 55 exact
    rewrite ingress tag pop 1 symmetric
    l2vpn
    pw-class PW-CLASS-TEST
      encapsulation mpls
      transport-mode ethernet
    bridge group vpls-test
      bridge-domain asr9k-7600
      interface TenGigE0/1/0/3.55
      vfi vlan-55
        neighbor 6.6.6.6 pw-id 55
        pw-class PW-CLASS-TEST
    7600
    ethernet evc test-vpls
    interface GigabitEthernet4/2
    no ip address
    speed 1000
    service instance 55 ethernet test-vpls
      encapsulation dot1q 55
      rewrite ingress tag pop 1 symmetric
      bridge-domain 55
    interface Vlan55
    no ip address
    xconnect vfi asr9k-7600
    end
    l2 vfi asr9k-7600 manual test-vpls
    vpn id 55
    neighbor 19.19.19.19 encapsulation mpls
    ||||||||||||
    RP/0/RSP0/CPU0:XR1#sh l2vpn bridge-domain
    Wed Oct 16 19:34:58.345 UTC
    Legend: pp = Partially Programmed.
    Bridge group: vpls-test, bridge-domain: asr9k-7600, id: 15, state: up, ShgId: 0, MSTi: 0
      Aging: 300 s, MAC limit: 4000, Action: none, Notification: syslog
      Filter MAC addresses: 0
      ACs: 1 (1 up), VFIs: 1, PWs: 1 (1 up), PBBs: 0 (0 up)
      List of ACs:
        Te0/1/0/3.55, state: up, Static MAC addresses: 0
      List of Access PWs:
      List of VFIs:
        VFI vlan-55 (up)
          Neighbor 6.6.6.6 pw-id 55, state: up, Static MAC addresses: 0
    RP/0/RSP0/CPU0:XR1#
    RP/0/RSP0/CPU0:XR1#sh l2vpn bridge-domain  detail
    Wed Oct 16 19:35:02.391 UTC
    Legend: pp = Partially Programmed.
    Bridge group: vpls-test, bridge-domain: asr9k-7600, id: 15, state: up, ShgId: 0, MSTi: 0
      Coupled state: disabled
      MAC learning: enabled
      MAC withdraw: enabled
        MAC withdraw for Access PW: enabled
        MAC withdraw sent on bridge port down: disabled
      Flooding:
        Broadcast & Multicast: enabled
        Unknown unicast: enabled
      MAC aging time: 300 s, Type: inactivity
      MAC limit: 4000, Action: none, Notification: syslog
      MAC limit reached: no
      MAC port down flush: enabled
      MAC Secure: disabled, Logging: disabled
      Split Horizon Group: none
      Dynamic ARP Inspection: disabled, Logging: disabled
      IP Source Guard: disabled, Logging: disabled
      DHCPv4 snooping: disabled
      IGMP Snooping profile: none
      Bridge MTU: 1500
      MIB cvplsConfigIndex: 16
      Filter MAC addresses:
      Create time: 16/10/2013 18:40:04 (00:54:57 ago)
      No status change since creation
      ACs: 1 (1 up), VFIs: 1, PWs: 1 (1 up), PBBs: 0 (0 up)
      List of ACs:
        AC: TenGigE0/1/0/3.55, state is up
          Type VLAN; Num Ranges: 1
          VLAN ranges: [55, 55]
          MTU 1500; XC ID 0x44002e; interworking none
          MAC learning: enabled
          Flooding:
            Broadcast & Multicast: enabled
            Unknown unicast: enabled
          MAC aging time: 300 s, Type: inactivity
          MAC limit: 4000, Action: none, Notification: syslog
          MAC limit reached: no
          MAC port down flush: enabled
          MAC Secure: disabled, Logging: disabled
          Split Horizon Group: none
          Dynamic ARP Inspection: disabled, Logging: disabled
          IP Source Guard: disabled, Logging: disabled
          DHCPv4 snooping: disabled
          IGMP Snooping profile: none
          Storm Control: disabled
          Static MAC addresses:
          Statistics:
            packets: received 0, sent 2
            bytes: received 0, sent 112
          Storm control drop counters:
            packets: broadcast 0, multicast 0, unknown unicast 0
            bytes: broadcast 0, multicast 0, unknown unicast 0
          Dynamic ARP inspection drop counters:
            packets: 0, bytes: 0
          IP source guard drop counters:
            packets: 0, bytes: 0
      List of Access PWs:
      List of VFIs:
        VFI vlan-55 (up)
          PW: neighbor 6.6.6.6, PW ID 55, state is up ( established )
            PW class PW-CLASS-TEST, XC ID 0xc000001d
            Encapsulation MPLS, protocol LDP
            Source address 19.19.19.19
            PW type Ethernet, control word disabled, interworking none
            PW backup disable delay 0 sec
            Sequencing not set
            PW Status TLV in use
              MPLS        Local                          Remote
              Label        16052                          63
              Group ID    0xf                            0x0
              Interface    vlan-55                        unknown
              MTU          1500                          1500
              Control word disabled                      disabled
              PW type      Ethernet                      Ethernet
              VCCV CV type 0x2                            0x12
                          (LSP ping verification)        (LSP ping verification)
              VCCV CC type 0x6                            0x6
                          (router alert label)          (router alert label)
                          (TTL expiry)                  (TTL expiry)
            Incoming Status (PW Status TLV):
              Status code: 0x0 (Up) in Notification message
            MIB cpwVcIndex: 3221225501
            Create time: 16/10/2013 18:51:28 (00:43:33 ago)
            Last time status changed: 16/10/2013 18:52:43 (00:42:18 ago)
            MAC withdraw message: send 0 receive 0
            Static MAC addresses:
            Statistics:
              packets: received 0, sent 0
              bytes: received 0, sent 0
          DHCPv4 snooping: disabled
          IGMP Snooping profile: none
          VFI Statistics:
            drops: illegal VLAN 0, illegal length 0
    RP/0/RSP0/CPU0:XR1#
    |||
    NPE-3#show mpls l2 binding
      Destination Address: 19.19.19.19,VC ID: 55
        Local Label:  63
            Cbit: 0,    VC Type: Ethernet,    GroupID: 0
            MTU: 1500,  Interface Desc: n/a
            VCCV: CC Type: RA [2], TTL [3]
                  CV Type: LSPV [2], BFD/Raw [5]
        Remote Label: 16052
            Cbit: 0,    VC Type: Ethernet,    GroupID: 15
            MTU: 1500,  Interface Desc: vlan-55
            VCCV: CC Type: RA [2], TTL [3]
                  CV Type: LSPV [2]
    NPE-3#
    NPE-3#show mpls l2 vc 55
    Local intf    Local circuit              Dest address    VC ID      Status
    VFI asr9k-7600  \
                  vfi                        19.19.19.19    55        UP
    NPE-3#
    NPE-3#show mpls l2 vc 55 detail
    Local interface: VFI asr9k-7600 vfi up
      Interworking type is Ethernet
      Destination address: 19.19.19.19, VC ID: 55, VC status: up
        Output interface: none, imposed label stack {}
        Preferred path: not configured
        Default path: active
        No adjacency
      Create time: 00:53:12, last status change time: 00:40:59
        Last label FSM state change time: 00:39:58
        Last peer autosense occurred at: 00:40:59
      Signaling protocol: LDP, peer 19.19.19.19:0 up
        Targeted Hello: 6.6.6.6(LDP Id) -> 19.19.19.19, LDP is UP
        Status TLV support (local/remote)  : enabled/supported
          LDP route watch                  : enabled
          Label/status state machine        : established, LruRru
          Last local dataplane  status rcvd: No fault
          Last BFD dataplane    status rcvd: Not sent
          Last BFD peer monitor  status rcvd: No fault
          Last local AC  circuit status rcvd: No fault
          Last local AC  circuit status sent: No fault
          Last local PW i/f circ status rcvd: No fault
          Last local LDP TLV    status sent: No fault
          Last remote LDP TLV    status rcvd: No fault
          Last remote LDP ADJ    status rcvd: No fault
        MPLS VC labels: local 63, remote 16052
        Group ID: local 0, remote 15
        MTU: local 1500, remote 1500
        Remote interface description: vlan-55
      Sequencing: receive disabled, send disabled
      Control Word: Off (configured: autosense)
      SSO Descriptor: 19.19.19.19/55, local label: 63
      Dataplane:
        SSM segment/switch IDs: 4200/110690 (used), PWID: 27
      VC statistics:
        transit packet totals: receive 0, send 0
        transit byte totals:  receive 0, send 0
        transit packet drops:  receive 0, seq error 0, send 0
    NPE-3#
    Many Thanks
    Regards
    Sherif Ismail

    Hi Xander
    First many thanks for your assistance
    Have recheked CEs config and they are straight forward. [trunk interface allowing all vlans]
    However I have added CE3/PE3 to topolgoy and results were somehow interesting
    CE1(ME3800) -- PE1 (ASR9K)  --- PE2 (7600) -- PE3 (7600) -- CE3 (ME3800)
                                                                    |
                                                            CE2(ME3800)
    Now both CE1/CE2 can ping CE3 but still no communication between CE1 & CE2
    Dont know what could be the difference between CE2 & CE3. Only thing that comes to my mind is that with CE2, PE2 is directly connected to PE1. Dont know if this could be a problem or not as in this case MPLS label should be pop but still there is VC label
    Another thing I removed "rewrite ingress tag pop 1 symmetric" from all PEs cause with this command CE3 (only) was receiving BPDU with different VLAN !      [dont know if this behavior is normal or not]
    interface GigabitEthernet4/2
    no ip address
    speed 1000
    service instance 55 ethernet
      encapsulation dot1q 55
      rewrite ingress tag pop 1 symmetric
      bridge-domain 55
    *Oct 24 21:57:14.158: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 2 on GigabitEthernet0/23 VLAN55.
    *Oct 24 21:57:14.158: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking GigabitEthernet0/23 on VLAN0055. Inconsistent local vlan.
    *Oct 24 21:57:15.158: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan55, changed state to down
    UPE-42#
    Once I remove it
    UPE-42# *Oct 24 21:59:23.638: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet0/23 on VLAN0055. Port consistency restored
    Now what do you think ?  :]
    Many Thanks
    Regards
    Sherif Ismail

  • Unable to retrieve data from XML Type

    Hi All,
    I have table which has Column of type XMLType
    XML Data is loaded in the table.
    But when iam trying to extract not able to retrieve the data
    Following is the select query i am using
    SELECT CL.XMLDATA.EXTRACT('/ServiceType/entityName/text()').getStringVal() "entityname" FROM CL_DATA_SERVICE_TEMPLATE CL;
    Any help / pointer will help me a lot... Thanks in advance
    Sample XML File:
    <?xml version="1.0" encoding="WINDOWS-1252"?>
    <ServiceType xmlns="http://www.bmiasia.com/tBos/service_1_0">
    <entityName>bmiasia.app.irb.servicetemplate12</entityName>
    <systemVersion>4</systemVersion>
    <displayName>
    <bundle />
    <key>AG-EVC</key>
    </displayName>
    <description>AG-EVC GROUP: AG-EVC</description>
    <category entityName="bmiasia.app.service.category.ServiceRootCategory.AG_-_EVC_Services">
    <operation>ADD</operation>
    </category>
    <entityMetaInfo name="bmiasia.app.irb.servicetemplate12.NC_PRODUCT_ID">
    <type entityName="1"></type>
    </entityMetaInfo>
    <entityMetaInfo name="bmiasia.app.irb.servicetemplate12.NC_GL_PRODUCT_CODE">
    <type entityName="2"></type>
    </entityMetaInfo>
    <entityMetaInfo name="bmiasia.app.irb.servicetemplate12.NC_GL_PROFIT_CENTRE">
    <type entityName="3"></type>
    </entityMetaInfo>
    <entityMetaInfo name="bmiasia.app.irb.servicetemplate12.NC_SERVICE_CODE">
    <type entityName="4"></type>
    </entityMetaInfo>
    <entityMetaInfo name="bmiasia.app.irb.servicetemplate12.RSP_EU_CUST_REF">
    <type entityName="5"></type>
    </entityMetaInfo>
    <entityMetaInfo name="irbPkClass">
    <type entityName="com.convergys.geneva.j2ee.product.ProductPK"></type>
    </entityMetaInfo>
    <entityMetaInfo name="irbId">
    <type entityName="12"></type>
    </entityMetaInfo>
    <extensionProperty name="hasAddress" value="true"></extensionProperty>
    <parent>
    <itemkey>AllServiceTemplate</itemkey>
    <name>AllServiceTemplate</name>
    <targetEntity entityName="bmiasia.app.service.template.AllServiceTemplate"></targetEntity>
    <number>0</number>
    </parent>
    <group>NORMAL</group>
    <siu>
    <itemkey>L2_OPTION</itemkey>
    <operation>ADD</operation>
    <name>L2_OPTION</name>
    <required>true</required>
    <source>INTERNAL</source>
    <displayName>
    <key>L2 Option</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>L3_OPTION</itemkey>
    <operation>ADD</operation>
    <name>L3_OPTION</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>L3 Option</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>QPEVPL_SERVICE_ID</itemkey>
    <operation>ADD</operation>
    <name>QPEVPL_SERVICE_ID</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>QP EVLP Service ID</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>QPEVPL_LAG_ID</itemkey>
    <operation>ADD</operation>
    <name>QPEVPL_LAG_ID</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>QP EVLP LAG ID</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>CO_NAME</itemkey>
    <operation>ADD</operation>
    <name>CO_NAME</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Aggregation Layer / Co Layer</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>INSTALL_SALUTAION</itemkey>
    <operation>ADD</operation>
    <name>INSTALL_SALUTAION</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Installation Salutation</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>INSTALL_LASTNAME</itemkey>
    <operation>ADD</operation>
    <name>INSTALL_LASTNAME</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Installlation Last Name</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>INSTALL_FIRSTNAME</itemkey>
    <operation>ADD</operation>
    <name>INSTALL_FIRSTNAME</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Installation First Name</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>INSTALL_TELEPHONE</itemkey>
    <operation>ADD</operation>
    <name>INSTALL_TELEPHONE</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Installation Telephone</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>INSTALL_MOBILE</itemkey>
    <operation>ADD</operation>
    <name>INSTALL_MOBILE</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Installation Mobile</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>INSTALL_EMAIL</itemkey>
    <operation>ADD</operation>
    <name>INSTALL_EMAIL</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Installlation Email</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>INSTALL_NOTIFICATION</itemkey>
    <operation>ADD</operation>
    <name>INSTALL_NOTIFICATION</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Installation Notification</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>TECHNICAL_SALUTAION</itemkey>
    <operation>ADD</operation>
    <name>TECHNICAL_SALUTAION</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Operational / Technical Salutation</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>TECHNICAL_LASTNAME</itemkey>
    <operation>ADD</operation>
    <name>TECHNICAL_LASTNAME</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Operational / Technical Last Name</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>TECHNICAL_FIRSTNAME</itemkey>
    <operation>ADD</operation>
    <name>TECHNICAL_FIRSTNAME</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Operational / Technical First Name</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>TECHNICAL_TELEPHONE</itemkey>
    <operation>ADD</operation>
    <name>TECHNICAL_TELEPHONE</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Operational / Technical Telephone</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>TECHNICAL_MOBILE</itemkey>
    <operation>ADD</operation>
    <name>TECHNICAL_MOBILE</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Operational / Technical Mobile</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>TECHNICAL_EMAIL</itemkey>
    <operation>ADD</operation>
    <name>TECHNICAL_EMAIL</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Operational / Technical Email</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>TECHNICAL_NOTIFICATION</itemkey>
    <operation>ADD</operation>
    <name>TECHNICAL_NOTIFICATION</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Operational / Technical Notification</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>SERVICE_ACTIVATION_PERIOD</itemkey>
    <operation>ADD</operation>
    <name>SERVICE_ACTIVATION_PERIOD</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Service Activation Period</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>REJECT_CODE</itemkey>
    <operation>ADD</operation>
    <name>REJECT_CODE</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Rejection Reason</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>APPLICATION_ACCEPTED</itemkey>
    <operation>ADD</operation>
    <name>APPLICATION_ACCEPTED</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Application Accepted</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.BooleanCheckSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>APPLICATION_REJECTED</itemkey>
    <operation>ADD</operation>
    <name>APPLICATION_REJECTED</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Application Rejected</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.BooleanCheckSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>APPROVAL_CODE</itemkey>
    <operation>ADD</operation>
    <name>APPROVAL_CODE</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Approval Code</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>PROCESSED_BY</itemkey>
    <operation>ADD</operation>
    <name>PROCESSED_BY</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Processed By</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>ACTUAL_RFS_DATE</itemkey>
    <operation>ADD</operation>
    <name>ACTUAL_RFS_DATE</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Actual RFS Date</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.DateSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>DISCLAIMER</itemkey>
    <operation>ADD</operation>
    <name>DISCLAIMER</name>
    <required>false</required>
    <source>INTERNAL</source>
    <displayName>
    <key>Disclaimer</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>NC_PRODUCT_ID</itemkey>
    <operation>ADD</operation>
    <name>NC_PRODUCT_ID</name>
    <required>false</required>
    <source>EXTERNAL</source>
    <displayName>
    <key>NC Product ID</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>NC_GL_PRODUCT_CODE</itemkey>
    <operation>ADD</operation>
    <name>NC_GL_PRODUCT_CODE</name>
    <required>false</required>
    <source>EXTERNAL</source>
    <displayName>
    <key>NC GL Product Code</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>NC_GL_PROFIT_CENTRE</itemkey>
    <operation>ADD</operation>
    <name>NC_GL_PROFIT_CENTRE</name>
    <required>false</required>
    <source>EXTERNAL</source>
    <displayName>
    <key>NC GL Profit Centre</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>NC_SERVICE_CODE</itemkey>
    <operation>ADD</operation>
    <name>NC_SERVICE_CODE</name>
    <required>false</required>
    <source>EXTERNAL</source>
    <displayName>
    <key>EUC ID</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.common.StringSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAttribute"></mapping>
    <scope>PRODUCT</scope>
    </siu>
    <siu>
    <itemkey>bmiasia.app.irb.servicetemplate54</itemkey>
    <operation>ADD</operation>
    <name>bmiasia.app.irb.servicetemplate54</name>
    <required>false</required>
    <source>INTERNAL</source>
    <equalsProvider>bmiasia.app.service.spi.AddSvcSIUEqualsProvider</equalsProvider>
    <displayName>
    <key>CIR Per 250Mbps CoS A</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.AdditionalServiceSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAdditionalService"></mapping>
    <scope>SERVICE</scope>
    <outSvcAttr>true</outSvcAttr>
    </siu>
    <siu>
    <itemkey>bmiasia.app.irb.servicetemplate55</itemkey>
    <operation>ADD</operation>
    <name>bmiasia.app.irb.servicetemplate55</name>
    <required>false</required>
    <source>INTERNAL</source>
    <equalsProvider>bmiasia.app.service.spi.AddSvcSIUEqualsProvider</equalsProvider>
    <displayName>
    <key>CIR Per 250Mbps CoS B</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.AdditionalServiceSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAdditionalService"></mapping>
    <scope>SERVICE</scope>
    <outSvcAttr>true</outSvcAttr>
    </siu>
    <siu>
    <itemkey>bmiasia.app.irb.servicetemplate56</itemkey>
    <operation>ADD</operation>
    <name>bmiasia.app.irb.servicetemplate56</name>
    <required>false</required>
    <source>INTERNAL</source>
    <equalsProvider>bmiasia.app.service.spi.AddSvcSIUEqualsProvider</equalsProvider>
    <displayName>
    <key>CIR Per 250Mbps CoS C</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.AdditionalServiceSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAdditionalService"></mapping>
    <scope>SERVICE</scope>
    <outSvcAttr>true</outSvcAttr>
    </siu>
    <siu>
    <itemkey>bmiasia.app.irb.servicetemplate57</itemkey>
    <operation>ADD</operation>
    <name>bmiasia.app.irb.servicetemplate57</name>
    <required>false</required>
    <source>INTERNAL</source>
    <equalsProvider>bmiasia.app.service.spi.AddSvcSIUEqualsProvider</equalsProvider>
    <displayName>
    <key>CIR Per 250Mbps CoS D</key>
    </displayName>
    <type entityName="bmiasia.app.siulib.siu.AdditionalServiceSIU"></type>
    <mapping entityName="bmiasia.app.service.oo.ServiceAndAdditionalService"></mapping>
    <scope>SERVICE</scope>
    <outSvcAttr>true</outSvcAttr>
    </siu>
    <defaultWorkflowInfo>
    <workflow entityName="bmiasia.app.irb.servicetemplate12_Workflow"></workflow>
    <cancelFlow entityName="bmiasia.app.irb.servicetemplate12_CancelFlow"></cancelFlow>
    </defaultWorkflowInfo>
    <source>EXTERNAL</source>
    <additionalServices entityName="bmiasia.app.irb.servicetemplate54">
    <operation>ADD</operation>
    <name>CIR Per 250Mbps CoS A</name>
    </additionalServices>
    <additionalServices entityName="bmiasia.app.irb.servicetemplate55">
    <operation>ADD</operation>
    <name>CIR Per 250Mbps CoS B</name>
    </additionalServices>
    <additionalServices entityName="bmiasia.app.irb.servicetemplate56">
    <operation>ADD</operation>
    <name>CIR Per 250Mbps CoS C</name>
    </additionalServices>
    <additionalServices entityName="bmiasia.app.irb.servicetemplate57">
    <operation>ADD</operation>
    <name>CIR Per 250Mbps CoS D</name>
    </additionalServices>
    <defaultWorkflowDefinition>
    <installSoEntityName>bmiasia.app.template.serviceorder.Installservicetemplate12SO</installSoEntityName>
    <changeSoEntityName>bmiasia.app.template.serviceorder.Modifyservicetemplate12SO</changeSoEntityName>
    <removeSoEntityName>bmiasia.app.template.serviceorder.Removeservicetemplate12SO</removeSoEntityName>
    <workflow>
    <entityName>bmiasia.app.irb.servicetemplate12_Workflow</entityName>
    </workflow>
    <cancelFlow>
    <entityName>bmiasia.app.irb.servicetemplate12_CancelFlow</entityName>
    </cancelFlow>
    </defaultWorkflowDefinition>
    </ServiceType>

    Hi !!
    Now when iam extracting the data for the above xml, using the below query
    SELECT extractvalue(VALUE(p),'/itemkey/*') Name, extractvalue(VALUE(p),'/required/*') Required FROM CL_DATA_SERVICE_TEMPLATE w, TABLE(XMLSEQUENCE(EXTRACT(xmldata,'/ServiceType/siu','xmlns="http://www.bmiasia.com/tBos/service_1_0"'))) p
    I am expecting the output to be something like below
    Name | Required
    L2_OPTION | true
    L3_OPTION | false
    but iam getting the required number of rows but all blank
    Lets take it as O/P should be 20 Rows, then iam getting 20 Rows.... But all are blank
    What is wrong in the query ?
    Can some one point it out

  • VPLS doesn't work on Catalyst 6500

    Hello everybody
    I'd like to setup VPLS between 3 points. Our switches are 6504E with Sup720-3BXL
      and the the following modules and IOS:
    6504# show module
    Mod Ports Card Type                              Model              Serial No. 
      1    2  Supervisor Engine 720 (Active)         WS-SUP720-3BXL     SAL134322F9
      3   24  CEF720 24 port 1000mb SFP              WS-X6724-SFP       SAL1219PUZU
      4   48  48-port 100FX SFP Ethernet Module      WS-X6148-FE-SFP    SAL1216N2QD
    Mod MAC addresses                       Hw    Fw           Sw           Status 
      1  001a.a22d.90c4 to 001a.a22d.90c7   5.9   8.5(3)       15.1(2)SY1   Ok     
      3  0021.5593.b6c8 to 0021.5593.b6df   3.1   12.2(18r)S1  15.1(2)SY1  Ok     
      4  001f.6cae.3340 to 001f.6cae.336f   3.3   8.4(1)       15.1(2)SY1   Ok     
    Mod  Sub-Module                  Model              Serial       Hw     Status 
      1  Policy Feature Card 3       WS-F6K-PFC3BXL     SAL134325LA  1.11  Ok     
      1  MSFC3 Daughterboard         WS-SUP720          SAL13421LZN  4.0    Ok     
      3  Centralized Forwarding Card WS-F6700-CFC       SAL1218PC9H  4.0 Ok     
    my problem is that when i configure VPLS according to CISCO-Documents, the VFI and L2 VCs comes up,
    but i can't ping between end points located in Customer-Switches.
    Is any problem with Hardware-Configuration, IOS or platform support ?
    I have just studied the following link about this, but i'm not sure about that. (at least i can't believe that ! )
    http://afnog.org/pipermail/afnog/2013-February/001006.html
    Any comments will be appreciated. thanks
    Arshin

    Hi there,
    Could you provide the community with a little more information to help narrow troubleshooting? What operating system are we using?
    You can say thanks by clicking the Kudos Star in my post. If my post resolves your problem, please mark it as Accepted Solution so others can benefit too.

  • How to verify VPLS mac-address forwarding

    I think VPLS know how to forward by mac-address. but how to verify it ?
    for example I show mac-address vlan 100. But I can not find a command to verify How mac-address is forwarding ?
    at 6509:
    PA_C76_1>sh mpls l2transport vc
    Local intf Local circuit Dest address VC ID Status
    VFI PA-LA-test VFI 203.160.227.88 100 UP
    VFI PA-LA-test VFI 203.160.227.95 100 UP
    PA_C76_1>show mac-address-table vlan 100
    Legend: * - primary entry
    age - seconds since last seen
    n/a - not available
    vlan mac address type learn age ports
    ------+----------------+--------+-----+----------+--------------------------
    * 100 000b.45b6.bc40 dynamic Yes 95 Router
    * 100 0012.d946.59c1 dynamic Yes 10 Gi4/1

    Hi,
    VPLS provides the medium to for a E-LAN, and in Cisco implementations, the MAC learning is not actually done by a VPLS instance.
    This can be best explained by an example.
    PE(SW)-A ---- PE(SW)-B
    PE(SW)-C
    Now these three PE nodes under VPLS, are only provided the medium to connect to each other using P2P PW forming a full mesh.
    For simplicity you can assume they are three switches connected in the above manner using copper. So this copper connecitivity is provided by VPLS.
    And at the end of the day the end nodes learn mac addresses using the conventional method of flooding and learning. So you wont find any VPLS specific commands to see what mac address is the VPLS instance flooding. As its only providing a medium for connectivty. And the flooding is done by the end nodes. as they treat the VPLS VC as one of the outgoing port.
    HTH-Cheers,
    Swaroop

  • WARNING: Type 'SByte' is not available in the public API. Onyx development?

    Hello i'm getting the warning WARNING: Type 'SByte' is not available in the public API.
    and various other warnings.The problem is that i don't see any code.
    Any thoughts?BTW is onyx still under development?
    ps:I know that nobody is going to reply so i wonder why i keep asking.

    The vSphere client uses some hidden API's. If you perform an action in the vSphere client that uses a hidden API, Onyx will report the "WARNING: Type 'xxx' is not available in the public API." message. This unfortunately limits what you can do with PowerCLI. Some know hidden API's are for tags, cluster EVC mode and for Storage Profiles.
    I don't know if Onyx is still under development. Maybe some from VMware can answer this question?

  • Sony VPL - CS5 Projector Component input

    Hello. I have a Sony VPL - CS5 Projector, and a Sony BDP-BX37 Blu Ray Disc Player.
    I want to use these two items together.
    The projector is an older model, and does not have an HDMI input, although the manual does state that the VGA input can also be used as a component input.
    I tried making an adaptor wired as follows....
    Pin 1=Pr+
    Pin 2=Y+
    Pin 3=Pb+
    Pin 6=Pr-
    Pin 7=Y-
    Pin 8=Pb-
    The projector manual described the above pinning as....
    Pin 1=R
    Pin 2=G
    Pin 3=B
    Pin 6=R-
    Pin 7=G-
    Pin 8=B-
    While I do get a picture, i only get green.
    Obviously I have done something wrong.
    I have double checked the integrity of my connections using a circuit tester, and even though all connectors are fine, the projector only recognized the input from Pin 2/7.
    Additionally, when I manually change the input setting from "Input A/Computer" to "Input A/Component", the projector does not recognize any signal at all.
    All that being said, my question to you is how do I properly connect the 3 component output connections (Pr, Pb, Y) from my Blu Ray player to this projector.
    All I need is to be told which pins on the VGA connector correspond to the positive and negative connections Pb, Pr and Y of the Blu Ray player.
    Thanks in advance for your help with this, and have a great day.
    ....Tony M

    Hello Tony,
    Welcome to the User Discussion Forums.
    Unfortunately we cannot release the pin out or wiring diagrams via the forums , If you require the service manual that includes all pin outs and schematics of the BDP-BX37 you would need to visit our
    [url=https://iamc.sel.sony.com/idm/forms/pages/ascLoginMMN.jsp?TYPE=33554433&REALMOID=06-90ae0017-0fff-4c7e-add0-53dbdc5f5833&GUID=&SMAUTHREASON=0&METHOD=GET&SMAGENTNAME=-SM-Q6Ra9hpD%2f%2bCj41T9KSl0chiq3qLamKiryQsLwNZIDNGx1BFl7e5D7SkmodTJyjyc&TARGET=-SM-https%3a%2f%2fdbiz.sel.sony.com%2fsecure%2fasc%2fweb%2findex.do:3swk4xhc]Sony ASC Portal Log In page[/url:3swk4xhc]
    The only suggestion we can offer over the forums is to use an HDMI to Component (YPbPr) converter. We cannot guarantee results , nor support the converter box, however this would likely be your best option to attempt to connect to the Projector for output.

  • VPLS on Same Line Card

    Hi dear all
    Can the ES+ line card be Edge-facing and Core-facing at the same time on RSP-7609-S like the below diagram ?
    i know that there is restriction on IOS XR, but i can't find any thing on IOS.
    i want to know that the below case support the VPLS or not?
    we want to use MPLS/VPN and VPLS at same time.
    i would be appreciated if give me the reference for that.
    Thank you

    Hi Amir,
    yes ES+ can be both core and customer (edge) facing card at the same time (even if the 2 links are on the same LC); actually there are some cases where ES+ MUST be both core and customer facing such as H-VPLS with MPLS access.
    In general for all VPLS flavours you need a ES+ card (or any other card performing label imposition such as SIP-400, SIP-600, ES20, OSM) facing the core. Then depending the type of access you want to configure you have a choice of customer facing LC. i.e: any PFC based LC for basic VPLS up to ES+ (or the other mentioned above) for H-VPLS with MPLS access.
    You find this (inderectly documented) on this page:
    http://www.cisco.com/en/US/docs/routers/7600/install_config/ES40_config_guide/es40_chap6.html#wp1463854
    regards,
    Riccardo

  • Data Center Interconnect using MPLS/VPLS

    We are deploying a backup data center and need to extend couple of Vlans over the backup data center.These two DC's which are interconnected by a fibre link which we manage and terminates on the ODC2MAN and ODCXMAN.We run  MPLS on these devices ODC2MAN and ODCXMAN(Cisco 6880) as PE routers. I configured  OSPF between these devices and advertised their loopbacks.
    I need configuration assistance on my PE (odcxman and odc2man) to run the VFI and the VPLS instances.The vlans on the ODCXAGG need to extend to the ODC2AGG. 
     Also, I am looking for the  configuration assistance such that each core devices should have 3 eigrp neighbors. 
    For example:
    ODC2COR1 should have Eigrp neighbors with ODCXCOR1, ODCXCOR2 and ODC2COR2 and my  VPLS Cloud should be emulated as a transparent bridge to my core devices such that it appears that ODC2COR1 is directly connected to ODCXCOR1 and ODCXCOR2 and have cdp neighbor relation. I have attached the diagram.Please let me know your inputs.

    Hello.
    If you are running Active/Backup DC scenario, I would suggest to make network design and configuration exactly the same. This includes platforms, interconnectivity types and etc.
    Do you know what is the latency on the fiber between these two DCs?
    Another question: why do you run 6880 in VSS, do you really need this?
    Q about the diagram: are you going to utilize 4 fibers for DC interconnection?
    PS: did you think about OTV+LISP instead of MPLS?

  • Mpls,vpls and ES20G module for 7600

    hi all,
    do i need a ES20G module on my 7600 in order to perform VPLS,6VPE mpls and so on...
    is this module just a 'speeding' module for these fonctionnalities ?
    (it is very expensive and the license too)
    Can i implement these features without it ??
    Does someone use vpls on 7600 without that module ?
    Thanks for answer

    Yes you can run VPLS without ES-20 using any WAN OSM or SIP-600 faing the core.
    Although there would be cost difference in each module including ES-20G, but these modules have been designed with different objectives and requirements in mind. As each module provides you with either a certain media type density(ES-20G) or OSM , or the flexibility of media type usage etc (SIP-600).
    So you can weigh the pros and cons with each module including the cost marked to the budget and take a call.
    HTH-Cheers,
    Swaroop

  • Disabling split horizon for H-VPLS on 7609

    Hi,
    We installed a new 7609 in our lab for doing H-VPLS interop. The sw Version is IOS (tm) s72033_rp Software (s72033_rp-PSV-M), Version 12.2(18)SXD7.
    I do not see the "no-split-horizon" option when trying to configure the remote spoke PE.
    l2 vfi PE3-VPLS-A manual
    vpn id 200
    neighbor 20.0.0.1 encapsulation mpls <no-split-horizon>
    Is there a version problem or some config issue ?
    Thanks
    AT

    The hw info is as follows :-
    Mod Ports Card Type Model Serial No.
    1 2 2+4 port GE-WAN OSM-2+4GE-WAN+ JAB0847061N
    5 2 Supervisor Engine 720 (Active) WS-SUP720-BASE SAL0919113H
    Mod Sub-Module Model Serial Hw Status
    5 Policy Feature Card 3 WS-F6K-PFC3BXL SAL09253GNF 1.6 Ok
    5 MSFC3 Daughterboard WS-SUP720 SAL09190TCD 2.5 Ok

  • [solved]VPLS can not activate

    Hello guys,
    I meet a pretty strange problem. I use ME36600X to test the vpls. And i cant activate the vfi.It said "Maximum number of VFIs 0 have been configured."
    And the other ME3600x have no problem at all.
    Someone know where is the problem?
    The two ME3600x have the exactlly same license and IOS version.
    thanks!
    3600-1(config)#l2 vfi test autodiscovery
    Maximum number of VFIs 0 have been configured.
    =========================
    Cisco IOS Software, ME360x Software (ME360x-UNIVERSALK9-M), Version 15.2(2)S1, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Tue 22-May-12 21:21 by prod_rel_team
    ROM: Bootstrap program is WHALES boot loader
    BOOTLDR: ME360x Boot Loader (ME360X-HBOOT-M), Version 12.2 [sourdutt-loader_release_ledfix 100]
    3k1.me.rd uptime is 1 hour, 48 minutes
    System returned to ROM by power-on
    System restarted at 16:05:39 UTC Thu Aug 23 2012
    System image file is "flash:/me360x-universalk9-mz.152-2.S1/me360x-universalk9-mz.152-2.S1.bin"
    Last reload reason: Unknown reason
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    License Level: AdvancedMetroIPAccess
    License Type: Permanent
    Next reload license Level: AdvancedMetroIPAccess
    cisco ME-3600X-24FS-M (PowerPC8572) processor (revision A0) with 1015808K/32760K bytes of memory.
    Processor board ID FOC1615V1AY
    Last reset from power-on
    2 Virtual Ethernet interfaces
    25 Gigabit Ethernet interfaces
    2 Ten Gigabit Ethernet interfaces
    The password-recovery mechanism is enabled.
    1536K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address       : F4:EA:67:B2:C1:80
    Motherboard assembly number     :
    Motherboard serial number       :
    Model revision number           : A0
    Motherboard revision number     : B0
    Model number                    : ME-3600X-24FS-M
    System serial number            :
    Top Assembly Part Number        : 800-32951-01
    Top Assembly Revision Number    : B0
    Version ID                      : V01
    CLEI Code Number                :
    Configuration register is 0xF
    ==================================================================================

    Cisco Bug CSCua05375, just change the sdm config to "default"

Maybe you are looking for