Connect does exist but you can't use it with a bridge domain.
The connect command is only used for two service instances. If you need to link three or more that traffic must be switched, so then just use a bridge-group.
Connect example Switch (config)# interface gigabitethernet0/2 Switch (config-if)# service instance 1 Ethernet Switch (config-if-srv)# encapsulation dot1q 10,20,30-50 Switch (config-if-srv)# exit Switch (config)# interface gigabitethernet0/3 Switch (config-if)# service instance 1 Ethernet Switch (config-if-srv)# encapsulation dot1q 10,20,30-50 Switch (config)#connect NAMEHERE GigabitEthernet0/2 1 GigabitEthernet0/3 1 On 9/26/2012 8:38 PM, Ivan wrote:
Hi, Does anyone know if it is possible to configure local connect on the ME3600X? The closest I have found is "hairpinning" http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/swevc.html#wp1051612 This uses bride domains and seems to have some limitations... Switch(config-if-srv)#bridge-domain ? <1-8000> Bridge-domain number Switch(config-if-srv)#bridge-domain 8000 QOS: Bridge-Domain greater than 4095 is not supported for output policies QoS: Detaching output service-policy TEST from efp 60 Something like on the 7600 ( " connect<name> GigabitEthernet3/3 55 GigabitEthernet3/3 66" would be nice. Ivan _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
